On Wed, Jul 10, 2013 at 9:18 AM, Dirk Thomas wrote: > Great, with that info I was able to identify the source of the problem. > I filled a ticket: > https://github.com/ros-infrastructure/jenkins_scripts/issues/45 > Expect it to be fixed soonish. > Nice! Looking forward to it. I'll updated you on new bugs as I find them! ;-) Marcus > > - Dirk > > > On 09.07.2013 16:46, Marcus Liebhardt wrote: > > On Wed, Jul 10, 2013 at 8:42 AM, Dirk Thomas dthomas@osrfoundation.org>> wrote: > > > > Marcus, I asked for the repository name. > > > > > > Sorry, misunderstood. The repo is turtlebot_create. > > https://github.com/turtlebot/turtlebot_create > > https://github.com/turtlebot-release/turtlebot_create-release > > > > Marcus > > > > > > - Dirk > > > > > > On 09.07.2013 16:38, Marcus Liebhardt wrote: > > > On Wed, Jul 10, 2013 at 1:24 AM, Dirk Thomas < > dthomas@osrfoundation.org dthomas@osrfoundation.org >> wrote: > > > > > > I might have missed it in the previous emails but for which > repository have you triggered the "latest" pre-release? > > > > > > > > > I triggered it from the release repo _not_ the source repo. > > > > > > Marcus > > > > > > > > > - Dirk > > > > > > > > > On 09.07.2013 03:19, Marcus Liebhardt wrote: > > > > Hey Dirk, > > > > > > > > On Tue, Jul 9, 2013 at 4:41 PM, Dirk Thomas < > dthomas@osrfoundation.org dthomas@osrfoundation.org > > > > >>> > wrote: > > > > > > > > Hi Marcus, > > > > > > > > could you please mention what exactly you selected on > the pre-release website and which packages you wanted to test? > > > > > > > > > > > > After doing what I described I can only select "latest" > for the pre-release. There are no other options. > > > > > > > > > > > > - Dirk > > > > > > > > > > > > On 09.07.2013 00:30, Tully Foote wrote: > > > > > > > > > > > > > > > > > > > > On Tue, Jul 9, 2013 at 12:00 AM, Marcus Liebhardt > marcus.liebhardt@yujinrobot.com> > > marcus.liebhardt@yujinrobot.com>>> > > > marcus.liebhardt@ >__yujinrobot.com < > http://yujinrobot.com> > > > > marcus.liebhardt@yujinrobot.com> marcus.liebhardt@yujinrobot.com>>>>> wrote: > > > > > > > > Hey Tully! > > > > ` > > > > Thanks for the hint. Unfortunately, I don't > think this solves my problem. > > > > > > > > I am able to trigger the pre-release, but it > currently fails with the first task of building, which is building the > metapackage. It tries to get the metapackage's > > dependencies (the > > > other > > > > packages > > > > in the repo) via apt-get, which of course is > not possible. Is that a setup issue on my side or is some logic > missing/broken in the pre-release script? > > > > > > > > > > > > We'll have to double check the prerelease logic. > It was written before metapackages were written. That sounds like a bug. > > > > > > > > > > > > Regarding the pre-release instructions, I > believe we need to add the other steps to prepare a pre-release as well. > > > > For example, I did: > > > > * Created a pull request for > rosdistro/hydro/release.yaml to add repo/package information, but without a > version number > > > > * Configured the release repo using > git-bloom-config > > > > * Started with bloom-release, but stopped > before creating a pull request for rosdistro/hydro/release.yaml. This was > need to get the required tags pushed to my release repo > > > > > > > > I am not sure, if the above is the > correct/recommended way to prepare a pre-release. For example, after using > the new highly automated tools, such as git-bloom-config and > > > bloom-release, > > > > it feels > > > > awkward to do similar things manually and > also to interrupt a process halfway through. > > > > > > > > > > > > This allows you to do a versioned prerelease, what > you should be able to do is ask for latest it may require you to have an > entry in the source index with the same name to do the > > latest > > > version. > > > > > > > > > > > > Yes, as I wrote above, I am able to select latest. > > > > > > > > Cheers, > > > > Marcus > > > > > > > > > > > > Tully > > > > > > > > > > > > Marcus > > > > > > > > > > > > > > > > > > > > On Tue, Jul 9, 2013 at 3:18 PM, Tully Foote < > tfoote@osrfoundation.org tfoote@osrfoundation.org > > > > >> > > > . > .>__org tfoote@osrfoundation.org > > tfoote@osrfoundation.org>>>>> wrote: > > > > > > > > Hi Markus, > > > > > > > > If you add it to the index without a > version and wait ~ 15-30 minutes for the distro caching to run you will be > able to run a prerelease of unreleased stuff. (It may be > > slightly > > > > longer if the > > > > farm is heavily loaded. The job is here: > http://jenkins.willowgarage. > __com:8080/job/_rosdistro-build-__cache/buildTimeTrend > > > > < > http://jenkins.willowgarage.com:8080/job/_rosdistro-build-cache/buildTimeTrend > >) > > > > > > > > If you could add this to the docs that > would be great. > > > > > > > > Tully > > > > > > > > > > > > On Mon, Jul 8, 2013 at 9:38 PM, Marcus > Liebhardt marcus.liebhardt@yujinrobot.com > > marcus.liebhardt@yujinrobot.com>>> > > > marcus.liebhardt@ >__yujinrobot.com < > http://yujinrobot.com> > > > > marcus.liebhardt@yujinrobot.com> marcus.liebhardt@yujinrobot.com>>>>> wrote: > > > > > > > > Hello fellow releasers! > > > > > > > > Wanting to bring in my first bloom > release as smooth as possible, I tried to do a pre-release before releasing > my package for the first time. However, after several > > failed > > > attempts I > > > > finally gave up and did a normal > release. > > > > > > > > We wrote down some instructions > about how to do this in Groovy, but they seem to be outdated by now. > Furthermore, the instructions about doing a first time release > > don't > > > mention the > > > > option of pre-releasing. Hence I > wonder, if such instructions for the new release pipeline exist? If not, > could we write them down? > > > > > > > > Best regards, > > > > Marcus > > > > > > > > -- > > > > Marcus Liebhardt > > > > Control Engineer > > > > Yujin Robot > > > > 주소: 대한민국 서울시 금천구 가산동 345-30 남성프라자 > #601, 153-023. > > > > Address: Door #601, Namsung-Plaza, > 345-30 Gasan-dong, Guemcheon-gu, Seoul, 153-023, Republic of Korea > > > > Website: http://www.yujinrobot.com < > http://www.yujinrobot.com/> > > > > Email: marcus.liebhardt@yujinrobot.__com > marcus.liebhardt@yujinrobot.com> > >> marcus.liebhardt@> > > > >__ > yujinrobot.com marcus.liebhardt@yujinrobot.com > > marcus.liebhardt@yujinrobot.com >>>> > > > > Phone: +82-70-46577073 > > > > > > > > > > _________________________________________________ > > > > Ros-release mailing list > > > > Ros-release@code.ros.org > > > > Ros-release@code.ros.org>>> Ros-release@code.ros>. > .>__org > > > Ros-release@code.ros.org> Ros-release@code.ros.org>>>> > > > > > > > > https://code.ros.org/mailman/__listinfo/ros-release < > https://code.ros.org/mailman/listinfo/ros-release> > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > Marcus Liebhardt > > > > Control Engineer > > > > Yujin Robot > > > > 주소: 대한민국 서울시 금천구 가산동 345-30 남성프라자 #601, > 153-023. > > > > Address: Door #601, Namsung-Plaza, 345-30 > Gasan-dong, Guemcheon-gu, Seoul, 153-023, Republic of Korea > > > > Website: http://www.yujinrobot.com < > http://www.yujinrobot.com/> > > > > Email: marcus.liebhardt@yujinrobot.__com > marcus.liebhardt@yujinrobot.com> > >> marcus.liebhardt@> > > > >__ > yujinrobot.com marcus.liebhardt@yujinrobot.com > > marcus.liebhardt@yujinrobot.com >>>> > > > > Phone: +82-70-46577073 > > > > > > > > > > > > > > > > > > > > > > > > _________________________________________________ > > > > Ros-release mailing list > > > > Ros-release@code.ros.org > > > > Ros-release@code.ros.org>>> > > > > https://code.ros.org/mailman/__listinfo/ros-release < > https://code.ros.org/mailman/listinfo/ros-release> > > > > > > > > > > > > _________________________________________________ > > > > Ros-release mailing list > > > > Ros-release@code.ros.org > > > > Ros-release@code.ros.org>>> > > > > https://code.ros.org/mailman/__listinfo/ros-release < > https://code.ros.org/mailman/listinfo/ros-release> > > > > > > > > > > > > > > > > > > > > -- > > > > Marcus Liebhardt > > > > Control Engineer > > > > Yujin Robot > > > > 주소: 대한민국 서울시 금천구 가산동 345-30 남성프라자 #601, 153-023. > > > > Address: Door #601, Namsung-Plaza, 345-30 Gasan-dong, > Guemcheon-gu, Seoul, 153-023, Republic of Korea > > > > Website: http://www.yujinrobot.com < > http://www.yujinrobot.com/> > > > > Email: marcus.liebhardt@yujinrobot.com marcus.liebhardt@yujinrobot.com> marcus.liebhardt@yujinrobot.com>> > > marcus.liebhardt@yujinrobot.com> marcus.liebhardt@yujinrobot.com>>> > > > > Phone: +82-70-46577073 > > > > > > _______________________________________________ > > > Ros-release mailing list > > > Ros-release@code.ros.org > > > > > https://code.ros.org/mailman/listinfo/ros-release > > > > > > > > > > > > > > > -- > > > Marcus Liebhardt > > > Control Engineer > > > Yujin Robot > > > 주소: 대한민국 서울시 금천구 가산동 345-30 남성프라자 #601, 153-023. > > > Address: Door #601, Namsung-Plaza, 345-30 Gasan-dong, > Guemcheon-gu, Seoul, 153-023, Republic of Korea > > > Website: http://www.yujinrobot.com > > > Email: marcus.liebhardt@yujinrobot.com marcus.liebhardt@yujinrobot.com> marcus.liebhardt@yujinrobot.com>> > > > Phone: +82-70-46577073 > > > > > > > > > > -- > > Marcus Liebhardt > > Control Engineer > > Yujin Robot > > 주소: 대한민국 서울시 금천구 가산동 345-30 남성프라자 #601, 153-023. > > Address: Door #601, Namsung-Plaza, 345-30 Gasan-dong, Guemcheon-gu, > Seoul, 153-023, Republic of Korea > > Website: http://www.yujinrobot.com > > Email: marcus.liebhardt@yujinrobot.com marcus.liebhardt@yujinrobot.com> > > Phone: +82-70-46577073 > > _______________________________________________ > Ros-release mailing list > Ros-release@code.ros.org > https://code.ros.org/mailman/listinfo/ros-release > -- Marcus Liebhardt Control Engineer Yujin Robot 주소: 대한민국 서울시 금천구 가산동 345-30 남성프라자 #601, 153-023. Address: Door #601, Namsung-Plaza, 345-30 Gasan-dong, Guemcheon-gu, Seoul, 153-023, Republic of Korea Website: http://www.yujinrobot.com Email: marcus.liebhardt@yujinrobot.com Phone: +82-70-46577073