<div dir="ltr"><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jul 29, 2014 at 11:51 AM, <span dir="ltr"><<a href="mailto:dfleming@austin.rr.com" target="_blank">dfleming@austin.rr.com</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">Also, if we move that content to the api-site/api-ref-guides directory, the guides would point directly to the WADLs in api-site/api-ref directory, so they pick up current content rather than pointing to what's merged into master by way of URL.<br>
<div class="im"><br></div></blockquote><div><br></div><div>Hi all, </div><div>Diane had a great idea over breakfast about how to mitigate these issues, and I've put together a pair of patches that put the solution in place to see what others think. </div>
<div><br></div><div>The idea is to stop embedding WADL references in the Dev References and instead link to the HTML output. Any relevant info for a particular call moves into the WADL itself.</div><div><br></div><div>I think this solves many of the issues I listed previously, so please review this approach and let us know what you think on the review (or here on the mailing list thread).</div>
<div><br></div><div>These examples are for Compute API v2, I'd do the same for Identity API docs and others with embedded WADL in the Dev Ref.</div><div>
<p class=""><a href="https://review.openstack.org/111436">https://review.openstack.org/111436</a></p><p class=""><a href="https://review.openstack.org/#/c/111435/">https://review.openstack.org/#/c/111435/</a><br></p></div>
<div>Thanks,</div><div>Anne</div><div><br></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">
<div class="im">
<br>
---- dfleming <<a href="mailto:dfleming@austin.rr.com">dfleming@austin.rr.com</a>> wrote:<br>
> Perhaps we could move the development guides out of their own repositories and put them all in the api - site repo and build everything there. That way, we know immediately whether the build breaks. We could put them in api-site/api - ref - guides directory. <br>
<br>
<br>
Sent from my Verizon Wireless 4G LTE smartphone<br>
<br>
<br>
-------- Original message --------<br>
</div><div class="im">From: Jorge Williams <<a href="mailto:jorge.williams@rackspace.com">jorge.williams@rackspace.com</a>><br>
Date:07/28/2014 4:24 PM (GMT-06:00)<br>
</div><div class=""><div class="h5">To: Andreas Jaeger <<a href="mailto:aj@suse.com">aj@suse.com</a>><br>
Cc: <a href="mailto:openstack-docs@lists.openstack.org">openstack-docs@lists.openstack.org</a><br>
Subject: Re: [Openstack-docs] identity-api: Building broken<br>
<br>
Maybe we need to rethink our model. Rather than reaching directly to a HTTP URI in github, we can instead list the WADL as a dependency in maven. Should be possible, we can tar up the api-ref project, have a deployment that stores it somewhere — maybe maven central…then when we build our docs we download and extract the correct version and tie everything together.<br>
<br>
-jOrGe W.<br>
<br>
<br>
<br>
<br>
On Jul 28, 2014, at 3:01 PM, Andreas Jaeger <<a href="mailto:aj@suse.com">aj@suse.com</a>> wrote:<br>
<br>
> On 07/28/2014 09:49 PM, Christian Berendt wrote:<br>
>> On 07/28/2014 09:46 PM, Anne Gentle wrote:<br>
>>> We already do test and gate on something building, but the problem was<br>
>>> with two repos, so I think is that he "race condition" problem we see in<br>
>>> other cross-repo dependencies?<br>
>><br>
>> I mean the cross-repo dependencies. Is it not possible to build checks<br>
>> to check if identity-api still builds when changing something in api-site?<br>
><br>
> Since we're not providing a "binary" that can be used in the environment<br>
> but instead download directly from the other git repository, I do not<br>
> see how to implement this.<br>
><br>
> Also, how are we getting in a change that renames a file in one<br>
> repository and the change for that in the other one together?<br>
><br>
> So, as much as I would like to see such gating done for these few repos,<br>
> I have no clever idea. If you have one, please write up a blueprint,<br>
><br>
> Andreas<br>
> --<br>
> Andreas Jaeger aj@{<a href="http://suse.com" target="_blank">suse.com</a>,<a href="http://opensuse.org" target="_blank">opensuse.org</a>} Twitter/Identica: jaegerandi<br>
> SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany<br>
> GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg)<br>
> GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126<br>
><br>
> _______________________________________________<br>
> Openstack-docs mailing list<br>
> <a href="mailto:Openstack-docs@lists.openstack.org">Openstack-docs@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
<br>
<br>
_______________________________________________<br>
Openstack-docs mailing list<br>
<a href="mailto:Openstack-docs@lists.openstack.org">Openstack-docs@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
<br>
<br>
<br>
_______________________________________________<br>
Openstack-docs mailing list<br>
<a href="mailto:Openstack-docs@lists.openstack.org">Openstack-docs@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
</div></div></blockquote></div><br></div></div>