openstack-doc-core team mailing list archive

[Anne Gentle <anne@xxxxxxxxxxxxx>]

Hi all -
Just to follow up on Joe Savak's issue, it turns out he updated the
image files but they aren't linked in any content. I've reopened
https://bugs.launchpad.net/openstack-manuals/+bug/911892 and marked
High.
Anne

On Fri, Jun 22, 2012 at 9:18 AM, Anne Gentle <anne@xxxxxxxxxxxxx> wrote:
> I looked into another job that didn't seem to merge correctly,
> https://review.openstack.org/8834 last night. It contained only
> images, but the changed images aren't appearing according to Joe
> Savak.
>
> What I do when these types of oddities happen is first look on Jenkins
> to see if anything sticks out. The "gate-openstack-manuals-merge" job
> is pretty unsmart if I remember correctly, so I usually have to go to
> the job that builds the book I'm looking at and look at the Console
> output. What sometimes happens is the build "succeeds" but the FTP
> file copy fails or some such.
>
> What I do next is go to IRC in #openstack-infra and ask for help
> troubleshooting a job. They're very helpful.
>
> I have a hunch that the FTP configuration changed recently so I'll ask
> in #openstack-infra for help.
>
> I'm also trying to figure out why Lorin's externals diagrams aren't
> showing up. Would love another pair of eyes on that.
> http://docs.openstack.org/essex/openstack-compute/install/yum/content/externals.html
> Possibly the .svg reference should change to .png?
>
> I have admin rights to the doc jobs on Jenkins, I think it makes sense
> to ask the CI team if we can have another doc team member get those
> rights as well to troubleshoot the jobs - Tom, are you willing to help
> out in that way?
>
> Thanks,
> Anne
>
> On Fri, Jun 22, 2012 at 1:00 AM, Tom Fifield <fifieldt@xxxxxxxxxxxxxx> wrote:
>> Hi,
>>
>> 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/
>>
>> 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/
>>
>> 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