<div dir="ltr">Hey Tully!<div><br></div><div>Thanks for the hint. Unfortunately, I don't think this solves my problem.</div><div><br></div><div>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?</div>
<div><br></div><div>Regarding the pre-release instructions, I believe we need to add the other steps to prepare a pre-release as well.<br></div><div>For example, I did:</div><div>* Created a pull request for rosdistro/hydro/release.yaml<font color="#333333" face="Helvetica, arial, freesans, clean, sans-serif"><span style="line-height:20px"> to add </span></font>repo/package information, but without a version number</div>
<div>* Configured the release repo using git-bloom-config</div><div>* 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</div>
<div><br></div><div>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.</div>
<div><br></div><div>Marcus</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jul 9, 2013 at 3:18 PM, Tully Foote <span dir="ltr"><<a href="mailto:tfoote@osrfoundation.org" target="_blank">tfoote@osrfoundation.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Markus, <div><br></div><div>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: <a href="http://jenkins.willowgarage.com:8080/job/_rosdistro-build-cache/buildTimeTrend" target="_blank">http://jenkins.willowgarage.com:8080/job/_rosdistro-build-cache/buildTimeTrend</a>) </div>
<div><br></div><div>If you could add this to the docs that would be great. </div><div><br></div><div>Tully</div></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div class="h5">On Mon, Jul 8, 2013 at 9:38 PM, Marcus Liebhardt <span dir="ltr"><<a href="mailto:marcus.liebhardt@yujinrobot.com" target="_blank">marcus.liebhardt@yujinrobot.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr">Hello fellow releasers!<div><br></div><div>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.</div>
<div><br></div><div>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?</div>
<div><br></div><div>Best regards,</div><div>Marcus</div><span><font color="#888888"><div><div><br></div>-- <br><font size="1">Marcus Liebhardt <br>Control Engineer<br>Yujin Robot<font size="1"><br></font></font><font size="1"><span lang="ko">주소</span></font><font size="1">: </font><font size="1"><span lang="ko-Hang">대한민국 </span></font><font size="1">서울시 금천구 가산동 345-30 남성프라자 #601, 153-023.<br>
</font><font size="1">Address: Door </font><font size="1">#601, Namsung-Plaza, 345-30 Gasan-dong, Guemcheon-gu, Seoul, 153-023, Republic of Korea<br>Website: <a href="http://www.yujinrobot.com/" target="_blank">http://www.yujinrobot.com</a><br>
Email: <a href="mailto:marcus.liebhardt@yujinrobot.com" target="_blank">marcus.liebhardt@yujinrobot.com</a><br>Phone: <a href="tel:%2B82-70-46577073" value="+827046577073" target="_blank">+82-70-46577073</a></font>
</div></font></span></div>
<br></div></div>_______________________________________________<br>
Ros-release mailing list<br>
<a href="mailto:Ros-release@code.ros.org" target="_blank">Ros-release@code.ros.org</a><br>
<a href="https://code.ros.org/mailman/listinfo/ros-release" target="_blank">https://code.ros.org/mailman/listinfo/ros-release</a><br>
<br></blockquote></div><br></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><font size="1">Marcus Liebhardt <br>Control Engineer<br>Yujin Robot<font size="1"><br></font></font><font size="1"><span lang="ko">주소</span></font><font size="1">: </font><font size="1"><span lang="ko-Hang">대한민국 </span></font><font size="1">서울시 금천구 가산동 345-30 남성프라자 #601, 153-023.<br>
</font><font size="1">Address: Door </font><font size="1">#601, Namsung-Plaza, 345-30 Gasan-dong, Guemcheon-gu, Seoul, 153-023, Republic of Korea<br>Website: <a href="http://www.yujinrobot.com/" style="color:rgb(0,0,0)" target="_blank">http://www.yujinrobot.com</a><br>
Email: <a href="mailto:marcus.liebhardt@yujinrobot.com" style="color:rgb(0,0,0)" target="_blank">marcus.liebhardt@yujinrobot.com</a><br>Phone: +82-70-46577073</font>
</div>