<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Aug 24, 2013 at 7:59 PM, Tom Fifield <span dir="ltr"><<a href="mailto:tom@openstack.org" target="_blank">tom@openstack.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Cheers for the look-in :) I agree we should be looking at the general case ... sorry for the short-sighted bug report!<br>
<br>
Thought about the idea of putting things in openstack-infra/config too, but discarded it. Essentially, I think we can do this without putting additional review load on openstack-infra. Having a bare-bones configuration in openstack-infra/config that points to scripts in docs-controlled repositories would enable us to be much more responsive to updates, and means we don't need to bother infra :)<br>
<br>
The last few patches I put through to config are took 1-3 weeks to get through. Importantly, this is completely fine - our patches are definitely low priority compared to others, and being typically less skilled at the ways of jenkins-job-builder we do want the time spent on thorough review from the overworked infracores.<br>
<br></blockquote><div><br></div><div>I ask for eyeballs in #openstack-infra if I have a review delay. They also have a separate Jenkins job review team so for these types of job additions I think your experience is atypical.</div>
<div><br></div><div>I've put this patch in: <a href="https://review.openstack.org/#/c/43734/">https://review.openstack.org/#/c/43734/</a> as a fix. Basically the zuul layout file is running in openstack-manuals and should run for operations-guide. What I'm unsure of, though, is whether the same pom.xml is used for non-english output. David or Daisy can you review?</div>
<div><br></div><div>Thanks,</div><div>Anne</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
However, this doesn't seem like a tenable situation for the tools, given the amount of churn we're going through right now (consider eg validate.py!). I think it would seriously slow things down for something that could potentially be done another way.<br>
<br>
<br>
Regards,<br>
<br>
Tom<div class=""><div class="h5"><br>
<br>
On 25/08/13 01:17, Anne Gentle wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Is there an option to store the tool in openstack-infra/config and<br>
point it at different repos? They're already running scripts to send<br>
Horizon strings to transifex. This makes me think so:<br>
<a href="https://review.openstack.org/#/c/32824/3/modules/openstack_project/files/jenkins_job_builder/config/translation-jobs.yaml" target="_blank">https://review.openstack.org/#<u></u>/c/32824/3/modules/openstack_<u></u>project/files/jenkins_job_<u></u>builder/config/translation-<u></u>jobs.yaml</a><br>
<br>
Plus <a href="https://review.openstack.org/#/c/34700/3/modules/jenkins/files/slave_scripts/propose_translation_update_manuals.sh" target="_blank">https://review.openstack.org/#<u></u>/c/34700/3/modules/jenkins/<u></u>files/slave_scripts/propose_<u></u>translation_update_manuals.sh</a><br>
points to a repo and a folder.<br>
<br>
It's from one the original patches Daisy sent through to start<br>
translations. Clark or Jeremy, do you know if a change in the config<br>
project would do what's needed -- slice docs from any repo?<br>
<br>
It's important to figure out because the next priority to me would be<br>
the API quick start in the openstack/api-site repo, then the install<br>
guides, so we have at least 3 repos with docs to translate. We could<br>
put all the high-priority-to-translate docs in one repo but that seems<br>
too rigid. Let's find a way.<br>
<br>
Thanks,<br>
Anne<br>
<br>
<br>
On Aug 23, 2013, at 7:23 PM, Tom Fifield <<a href="mailto:tom@openstack.org" target="_blank">tom@openstack.org</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Hi all,<br>
<br>
Just throwing this bug out there for your comment to select a way forward:<br>
<br>
<a href="https://bugs.launchpad.net/openstack-manuals/+bug/1216153" target="_blank">https://bugs.launchpad.net/<u></u>openstack-manuals/+bug/1216153</a><br>
<br>
<br>
The build job for the Japanese version of the Operations Guide was<br>
merged at: <a href="https://review.openstack.org/#/c/39846/" target="_blank">https://review.openstack.org/#<u></u>/c/39846/</a><br>
<br>
However, from the first run of the job (logs:<br>
<a href="https://jenkins01.openstack.org/job/openstack-operations-guide-ja/1/console" target="_blank">https://jenkins01.openstack.<u></u>org/job/openstack-operations-<u></u>guide-ja/1/console</a>)<br>
it becomes clear that it fails due to the split repositories.<br>
<br>
2013-08-23 23:42:49.457 | cp: cannot stat<br>
`./doc/src/docbkx/openstack-<u></u>ops': No such file or directory<br>
<br>
To fix this, we either need to:<br>
<br>
1) Check out the openstack-ops repo into manuals for build time<br>
<br>
2) Copy the tools into the openstack-ops repo and perform the painful<br>
ongoing task of keep them synchronised<br>
<br>
3) move openstack-ops back into the openstack-manuals repo<br>
<br>
<br>
<br>
Regards,<br>
<br>
<br>
Tom<br>
<br>
______________________________<u></u>_________________<br>
Openstack-docs mailing list<br>
<a href="mailto:Openstack-docs@lists.openstack.org" target="_blank">Openstack-docs@lists.<u></u>openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-docs</a><br>
</blockquote></blockquote>
<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Anne Gentle<br><a href="mailto:annegentle@justwriteclick.com" target="_blank">annegentle@justwriteclick.com</a>
</div></div>