openstack-doc-core team mailing list archive

[Tom Fifield <fifieldt@xxxxxxxxxxxxxx>]

Interestingly, the old version is still up, but at a different page:

http://docs.openstack.org/trunk/openstack-compute/admin/content/configuring-compute-rate-limiting.html

which is where my confusion comes from.

Do previously-built HTML pages stick around on the web server or something, perhaps?

Working on the cherrypick now.

Regards,

Tom
________________________________________
From: annegentle@xxxxxxxxxxxxxxxxxx [annegentle@xxxxxxxxxxxxxxxxxx] on behalf of Anne Gentle [anne@xxxxxxxxxxxxx]
Sent: Saturday, 23 June 2012 12:44 AM
To: Tom Fifield
Cc: openstack-doc-core@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Openstack-doc-core] Merged, but not built?

Hi again -

Running through the 7541, I definitely think it just needs to be cherry-picked.

> Recently, I've had a couple of changes which appear to have been merged
> successfully, but don't appear on docs.openstack.org.
> eg trunk
> https://review.openstack.org/#/c/7541/

This one definitely appears in
http://docs.openstack.org/trunk/openstack-compute/admin/content/configuring-compute-API.html.
So my guess is that it hasn't been cherry-picked to stable/essex.

>
> Jenkins: Change has been successfully merged into the git repository - so I
> guess
> https://jenkins.openstack.org/view/Openstack-manuals/job/gate-openstack-manuals-merge/
> works OK
>
> Jenkins:
> https://jenkins.openstack.org/job/gate-openstack-manuals-merge/406/console
> looks like it succeeded
>
>
> eg stable/diablo
> https://review.openstack.org/#/c/8634/

And this one definitely appears in
http://docs.openstack.org/diablo/openstack-compute/install/content/identity-define-services-endpoints.html

so it is getting built as expected.

Whew.

Does this one need to go to essex as well? Cherrypicking from diablo
to essex will probably end badly for this small a change. :)

Thanks Tom for your diligence.

Anne


> Jenkins:
> https://jenkins.openstack.org/job/gate-openstack-manuals-merge/495/console
> looks like it succeeded
>
> Jenkins: Change has been successfully merged into the git repository, so I
> guess
> https://jenkins.openstack.org/view/Openstack-manuals/job/gate-openstack-manuals-merge/
> works OK
>
>
> So, based on this I assume that another one of the Jenkins jobs to do with
> making the manuals end up on docs.openstack.org went wrong.
> * Does that make sense?
> * If so, are we checking for those kind of things?
> * What is the best thing to do in these cases?
>
>
> Regards,
>
> Tom
>
> --
> Mailing list: https://launchpad.net/~openstack-doc-core
> Post to     : openstack-doc-core@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack-doc-core
> More help   : https://help.launchpad.net/ListHelp