On 2 October 2013 03:37, Dirk Thomas wrote: > On 01.10.2013 00:28, Daniel Stonier wrote: > >> >> >> >> On 1 October 2013 04:55, Jack O'Quin > jack.oquin@gmail.com>> wrote: >> >> >> On Mon, Sep 30, 2013 at 2:42 PM, Tully Foote < >> tfoote@osrfoundation.org >> >> wrote: >> >> >> >> >> >> On Mon, Sep 30, 2013 at 9:16 AM, Isaac Isao Saito < >> 130s@lateeye.net > wrote: >> >> Now I also see some pre-releases pass w/o failures. Thanks >> Tully! >> >> Let me ask one follow-up question regarding what Jack said; >> >> On Fri, Sep 27, 2013 at 10:04 AM, Jack O'Quin < >> jack.oquin@gmail.com > wrote: >> > I like to run the "devel" pre-release on the source repo >> before using bloom-release. >> >> Is there a ways to run the pre-release test on ROS' jenkins >> against >> source repo (I know local pre-release is possible as in the >> wiki#1)? >> >> #1 http://wiki.ros.org/bloom/**Tutorials/PrereleaseTest#** >> Locally >> >> >> That link uses the release repo. The devel test can come before all >> that. >> >> 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 >> against the release repo tags. >> >> >> 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. >> >> 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. >> >> Daniel. >> > > > As mentioned by Tully and Jack in the last emails: the devel tests use the > source repos defined in https://github.com/ros/** > rosdistro/blob/master/hydro/**source.yaml > . > > I have also update the wiki page which describes the prereleases and devel > jobs: > http://wiki.ros.org/**regression_tests > > - Dirk > > 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: - It's downloading a rosinstall file generated with the source repo url and version key branch. - Not all entries in source.yaml have a version key. - I expect this means it downloads the default branch for the repository. - This is probably the cause of the confusion we've had trying to work out what pre-releases are actually building. - Why do some have a version key and some don't? How is it automatically added? Tully's comment 'using key matching against release.yaml' threw me in the previous email. I'm not sure what that is imparting. Cheers, Daniel. I'll interpret that as saying what I had guessed - it's using the branches listed in > > >> >> Right. So, just go to: >> >> http://prerelease.ros.org/**create_job/hydro >> >> and select the "devel" option. >> >> Your package must be defined in rosdistro/hydro/source.yaml for that >> option to be available. >> >> >-- >> >> joq >> >> ______________________________**_________________ >> ros-release mailing list >> ros-release@lists.ros.org >> > >> >> http://lists.ros.org/mailman/**listinfo/ros-release >> >> >> >> >> -- >> Phone : +82-10-5400-3296 (010-5400-3296) >> Home: http://snorriheim.dnsdojo.com/ >> Yujin R&D: http://rnd.yujinrobot.com/ >> >> >> >> ______________________________**_________________ >> ros-release mailing list >> ros-release@lists.ros.org >> http://lists.ros.org/mailman/**listinfo/ros-release >> >> > ______________________________**_________________ > ros-release mailing list > ros-release@lists.ros.org > http://lists.ros.org/mailman/**listinfo/ros-release > -- Phone : +82-10-5400-3296 (010-5400-3296) Home: http://snorriheim.dnsdojo.com/ Yujin R&D: http://rnd.yujinrobot.com/