<div dir="ltr"><div><br></div>It would be incredibly useful to be able to specify a pre-release version on the <a href="http://prerelease.ros.org/create_job/hydro" target="_blank">web page</a> as you make a test. Default value could be supplied from <a href="https://github.com/ros/rosdistro/blob/master/hydro" target="_blank">source.yaml</a>. Right now I have to pull request if I want to test a different branch. Is it necessary to have a man in the middle for the process of specifying a version for a prerelease test?<div>
<div><div class="gmail_extra"><br></div><div class="gmail_extra">Daniel.</div><div class="gmail_extra"><br><div class="gmail_quote">On 2 October 2013 11:50, Daniel Stonier <span dir="ltr"><<a href="mailto:d.stonier@gmail.com" target="_blank">d.stonier@gmail.com</a>></span> wrote:</div>
<div class="gmail_quote"><br></div><div class="gmail_quote"><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">
<div><div>On 2 October 2013 10:44, Dirk Thomas <span dir="ltr"><<a href="mailto:dthomas@osrfoundation.org" target="_blank">dthomas@osrfoundation.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 01.10.2013 18:31, Daniel Stonier wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
<br>
<br>
<br>
On 2 October 2013 03:37, Dirk Thomas <<a href="mailto:dthomas@osrfoundation.org" target="_blank">dthomas@osrfoundation.org</a> <mailto:<a href="mailto:dthomas@osrfoundation.org" target="_blank">dthomas@osrfoundation.<u></u>org</a>>> wrote:<br>
<br>
On 01.10.2013 00:28, Daniel Stonier wrote:<br>
<br>
<br>
<br>
<br></div>
On 1 October 2013 04:55, Jack O'Quin <<a href="mailto:jack.oquin@gmail.com" target="_blank">jack.oquin@gmail.com</a> <mailto:<a href="mailto:jack.oquin@gmail.com" target="_blank">jack.oquin@gmail.com</a>> <mailto:<a href="mailto:jack.oquin@gmail.com" target="_blank">jack.oquin@gmail.com</a> <mailto:<a href="mailto:jack.oquin@gmail.com" target="_blank">jack.oquin@gmail.com</a>>><u></u>> wrote:<br>
<br>
<br>
On Mon, Sep 30, 2013 at 2:42 PM, Tully Foote <<a href="mailto:tfoote@osrfoundation.org" target="_blank">tfoote@osrfoundation.org</a> <mailto:<a href="mailto:tfoote@osrfoundation.org" target="_blank">tfoote@osrfoundation.<u></u>org</a>> <mailto:<a href="mailto:tfoote@osrfoundation." target="_blank">tfoote@osrfoundation.</a>_<u></u>_org <mailto:<a href="mailto:tfoote@osrfoundation.org" target="_blank">tfoote@osrfoundation.<u></u>org</a>>>> wrote:<div>
<br>
<br>
<br>
<br>
<br>
<br>
On Mon, Sep 30, 2013 at 9:16 AM, Isaac Isao Saito <<a href="mailto:130s@lateeye.net" target="_blank">130s@lateeye.net</a> <mailto:<a href="mailto:130s@lateeye.net" target="_blank">130s@lateeye.net</a>> <mailto:<a href="mailto:130s@lateeye.net" target="_blank">130s@lateeye.net</a> <mailto:<a href="mailto:130s@lateeye.net" target="_blank">130s@lateeye.net</a>>>> wrote:<br>
<br>
Now I also see some pre-releases pass w/o failures. Thanks Tully!<br>
<br>
Let me ask one follow-up question regarding what Jack said;<br>
<br></div><div>
On Fri, Sep 27, 2013 at 10:04 AM, Jack O'Quin <<a href="mailto:jack.oquin@gmail.com" target="_blank">jack.oquin@gmail.com</a> <mailto:<a href="mailto:jack.oquin@gmail.com" target="_blank">jack.oquin@gmail.com</a>> <mailto:<a href="mailto:jack.oquin@gmail.com" target="_blank">jack.oquin@gmail.com</a> <mailto:<a href="mailto:jack.oquin@gmail.com" target="_blank">jack.oquin@gmail.com</a>>><u></u>> wrote:<br>
> I like to run the "devel" pre-release on the source repo before using bloom-release.<br>
<br>
Is there a ways to run the pre-release test on ROS' jenkins against<br>
source repo (I know local pre-release is possible as in the wiki#1)?<br>
<br></div>
#1 <a href="http://wiki.ros.org/bloom/__Tutorials/PrereleaseTest#__Locally" target="_blank">http://wiki.ros.org/bloom/__<u></u>Tutorials/PrereleaseTest#__<u></u>Locally</a> <<a href="http://wiki.ros.org/bloom/Tutorials/PrereleaseTest#Locally" target="_blank">http://wiki.ros.org/bloom/<u></u>Tutorials/PrereleaseTest#<u></u>Locally</a>><div>
<br>
<br>
<br>
That link uses the release repo. The devel test can come before all that.<br>
<br>
That's what a devel prerelease is. The devel test is against the source as defined in source.yaml using key matching against release.yaml. The latest and version numbered prereleases go<br>
against the release repo tags.<br>
<br>
<br>
We've been struggling with this for a bit now. Could sit down and spend a couple of hours testing the process, but would be far easier to pick some brains here.<br>
<br>
Is the devel test is against the tag identified by the version key in release.yaml? If that is true, the workflow for pre-releases would still seem awkward to me.<br>
<br>
Daniel.<br>
<br>
<br>
<br></div>
As mentioned by Tully and Jack in the last emails: the devel tests use the source repos defined in <a href="https://github.com/ros/__rosdistro/blob/master/hydro/__source.yaml" target="_blank">https://github.com/ros/__<u></u>rosdistro/blob/master/hydro/__<u></u>source.yaml</a><br>
<<a href="https://github.com/ros/rosdistro/blob/master/hydro/source.yaml" target="_blank">https://github.com/ros/<u></u>rosdistro/blob/master/hydro/<u></u>source.yaml</a>>.<div><br>
<br>
I have also update the wiki page which describes the prereleases and devel jobs:<br></div>
<a href="http://wiki.ros.org/__regression_tests" target="_blank">http://wiki.ros.org/__<u></u>regression_tests</a> <<a href="http://wiki.ros.org/regression_tests" target="_blank">http://wiki.ros.org/<u></u>regression_tests</a>><div>
<br>
<br>
- Dirk<br>
<br>
Ok, feeling like quite a dunderhead here. So decided to do some testing and here's what I can conclude about the devel prerelease along with some questions:<br>
</div></blockquote>
<br>
You should not need to conclude about what prereleases do.<br>
If the description (<a href="http://wiki.ros.org/regression_tests" target="_blank">http://wiki.ros.org/<u></u>regression_tests</a>) is not sufficient please provide feedback what needs clarfication then we can update the wiki page.<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
* It's downloading a rosinstall file generated with the source repo url and version key branch.<br>
* Not all entries in source.yaml <<a href="https://github.com/ros/rosdistro/blob/master/hydro/source.yaml" target="_blank">https://github.com/ros/<u></u>rosdistro/blob/master/hydro/<u></u>source.yaml</a>> have a version key.<br>
o I expect this means it downloads the default branch for the repository.<br>
</blockquote>
<br>
That is correct.<br>
I added that clarification to the wiki page: <a href="http://wiki.ros.org/regression_tests?action=diff" target="_blank">http://wiki.ros.org/<u></u>regression_tests?action=diff</a><br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
o This is probably the cause of the confusion we've had trying to work out what pre-releases are actually building.<br>
* Why do some have a version key and some don't? How is it automatically added?<br>
</blockquote>
<br>
Nothing happens automatically for that.<br>
Whatever a maintainer puts into that file will be used: a branch name, a tag name or nothing which implies the default branch.<div><br></div></blockquote><div><br></div></div></div><div>Ok, crystal now. I was wondering if source.yaml shouldn't be touched (I can't remember doing any pull requests to source.yaml, just to release.yaml, so something must be auto-generating the initial footprint there).</div>
<div><br></div><div>Thanks - I'll pass on the collective wisdom to our group.</div><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Tully's comment 'using key matching against release.yaml' threw me in the previous email. I'm not sure what that is imparting.<br>
</blockquote>
<br></div>
Tully referes to the fact that there is no relation between a release.yaml and source.yaml file.<br>
When selecting a repo the prerelease website just assumes that the repository name is the same in both both.<br>
That should be the case but is not strictly enforced anywhere.<span><font color="#888888"><br>
<br>
- Dirk</font></span><div><div><br>
<br>
______________________________<u></u>_________________<br>
ros-release mailing list<br>
<a href="mailto:ros-release@lists.ros.org" target="_blank">ros-release@lists.ros.org</a><br>
<a href="http://lists.ros.org/mailman/listinfo/ros-release" target="_blank">http://lists.ros.org/mailman/<u></u>listinfo/ros-release</a><br>
</div></div></blockquote></div></div><br><br clear="all"><div><div><br></div>-- <br>Phone : +82-10-5400-3296 (010-5400-3296)<br>Home: <a href="http://snorriheim.dnsdojo.com/" target="_blank">http://snorriheim.dnsdojo.com/</a><br>
<div>
Yujin R&D: <a href="http://rnd.yujinrobot.com/" target="_blank">http://rnd.yujinrobot.com/<br></a><br></div>
</div></div></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Phone : +82-10-5400-3296 (010-5400-3296)<br>Home: <a href="http://snorriheim.dnsdojo.com/" target="_blank">http://snorriheim.dnsdojo.com/</a><br><div>Yujin R&D: <a href="http://rnd.yujinrobot.com/" target="_blank">http://rnd.yujinrobot.com/<br>
</a><br></div>
</div></div></div></div>