<div dir="ltr">Hi Mike, <div><br></div><div>We've played with testing it. And we plan to make it available. What you see on the ros_comm is our proof of concept that it works. However to deploy it required a lot of manual work with admin access which we have not had time to develop into deployment scripts that we can make available to the community. We do hope to do that in the future such that everyone can have pull-request CI available on any package were running devel jobs. </div><div><br></div><div>Tully</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Sep 9, 2014 at 10:04 AM, Mike Purvis <span dir="ltr"><<a href="mailto:mpurvis@clearpathrobotics.com" target="_blank">mpurvis@clearpathrobotics.com</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">The community buildfarm does have a pull request builder plugin. Does that only work on certain orgs? Can others have it enabled?</div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On 9 September 2014 12:57, Dave Coleman <span dir="ltr"><<a href="mailto:davetcoleman@gmail.com" target="_blank">davetcoleman@gmail.com</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">So the options I see:<div><ul><li>Stop using Travis - can Jenkins do the same thing? Other CIs?</li><li>Release debians of ROS for Precise - very difficult/def. not worth the time</li><li>Somehow entice Travis developers (donations with money I don't have)<br></li><li>Build our own continuous integration servers - also difficult</li></ul></div></div><div class="gmail_extra"><br clear="all"><div><div dir="ltr"><div><span style="color:rgb(51,51,51);font-family:arial,sans-serif;background-color:rgb(255,255,255)"><font>dave</font></span></div><div><font color="#333333"><a href="tel:325.261.3283" value="+13252613283" target="_blank">325.261.3283</a></font><span style="font-size:small;color:rgb(51,51,51)"> c</span></div></div></div>
<br><div class="gmail_quote"><span>On Mon, Sep 8, 2014 at 3:43 PM, Dave Coleman <span dir="ltr"><<a href="mailto:davetcoleman@gmail.com" target="_blank">davetcoleman@gmail.com</a>></span> wrote:<br></span><div><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span style="color:rgb(38,38,38);font-family:arial,sans-serif;font-size:13px;line-height:16px">I'm not sure if this is the best mailing list for this question, but has </span><span style="color:rgb(38,38,38);font-family:arial,sans-serif;font-size:13px;line-height:16px">anyone found a work around to use Travis CI with ROS Indigo? Travis only runs Ubuntu Precise, confirmed by<br></span><div><font color="#262626" face="arial, sans-serif"><span style="line-height:16px"><a href="https://github.com/travis-ci/travis-ci/issues/2046" target="_blank">https://github.com/travis-ci/travis-ci/issues/2046</a></span></font></div><div><span style="color:rgb(38,38,38);font-family:arial,sans-serif;font-size:13px;line-height:16px"><br></span></div><div><span style="color:rgb(38,38,38);font-family:arial,sans-serif;font-size:13px;line-height:16px">So it lacks the ROS debians to build, for example, MoveIt's Indigo branch. Its frustrating to have all pull requests for Indigo fail i.e.</span></div><div><font color="#262626" face="arial, sans-serif"><span style="line-height:16px"><a href="https://github.com/ros-planning/moveit_ros/pull/490" target="_blank">https://github.com/ros-planning/moveit_ros/pull/490</a></span><br></font><div><font color="#262626" face="arial, sans-serif"><span style="line-height:16px"><br></span></font></div><div><font color="#262626" face="arial, sans-serif"><span style="line-height:16px">Thanks!<br></span></font><div><div class="gmail_extra"><br clear="all"><div><div dir="ltr"><div><span style="color:rgb(51,51,51);font-family:arial,sans-serif;background-color:rgb(255,255,255)"><font>dave coleman</font></span></div><div><br></div></div></div>
<br><div class="gmail_quote">On Mon, Sep 8, 2014 at 6:00 AM, <span dir="ltr"><<a href="mailto:ros-release-request@code.ros.org" target="_blank">ros-release-request@code.ros.org</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">Send ros-release mailing list submissions to<br>
<a href="mailto:ros-release@code.ros.org" target="_blank">ros-release@code.ros.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.ros.org/mailman/listinfo/ros-release" target="_blank">http://lists.ros.org/mailman/listinfo/ros-release</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:ros-release-request@code.ros.org" target="_blank">ros-release-request@code.ros.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:ros-release-owner@code.ros.org" target="_blank">ros-release-owner@code.ros.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of ros-release digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: dropping unmaintained Ubuntu distributions ? (Tully Foote)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Sun, 7 Sep 2014 13:58:45 -0700<br>
From: Tully Foote <<a href="mailto:tfoote@osrfoundation.org" target="_blank">tfoote@osrfoundation.org</a>><br>
To: The ROS release mailing list <<a href="mailto:ros-release@code.ros.org" target="_blank">ros-release@code.ros.org</a>><br>
Subject: Re: [ros-release] dropping unmaintained Ubuntu distributions<br>
?<br>
Message-ID:<br>
<CAM7qi7U9NcH6-drP82rPTU=Rp8C=<a href="mailto:jbwcLMe4u7Yy5EsCyx9-pA@mail.gmail.com" target="_blank">jbwcLMe4u7Yy5EsCyx9-pA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Yes, we do plan to spin down the builds of EOL'd Ubuntu platforms. we have<br>
not done this yet as we do not have that level of configuration built into<br>
the buildfarm. So we'll need to do some development to support that.<br>
<br>
With respect to libgphoto2 this isn't an EOL issue. It appears that in<br>
Saucy only libgphoto2-6-dev was released to replace libgphoto2-2-dev but<br>
the decision was reverted in trusty. So to fix this we just need to update<br>
the rosdep rule.<br>
<br>
<br>
Link online:<br>
<a href="http://packages.ubuntu.com/search?keywords=libgphoto2-6-dev&searchon=names" target="_blank">http://packages.ubuntu.com/search?keywords=libgphoto2-6-dev&searchon=names</a><br>
<br>
>From saucy/amd64 Packages file:<br>
Package: libgphoto2-6-dev<br>
Priority: optional<br>
Section: libdevel<br>
Installed-Size: 11550<br>
Maintainer: Ubuntu Developers <<a href="mailto:ubuntu-devel-discuss@lists.ubuntu.com" target="_blank">ubuntu-devel-discuss@lists.ubuntu.com</a>><br>
Original-Maintainer: Debian PhotoTools Maintainers <<br>
<a href="mailto:pkg-phototools-devel@lists.alioth.debian.org" target="_blank">pkg-phototools-devel@lists.alioth.debian.org</a>><br>
Architecture: amd64<br>
Source: libgphoto2<br>
Version: 2.5.2-0ubuntu5<br>
Replaces: libgphoto2-2-dev<br>
Depends: libgphoto2-6 (= 2.5.2-0ubuntu5), libexif-dev, libusb-1.0-0-dev,<br>
libc-dev, pkg-config<br>
Conflicts: libgphoto2-2-dev<br>
Filename:<br>
pool/main/libg/libgphoto2/libgphoto2-6-dev_2.5.2-0ubuntu5_amd64.deb<br>
Size: 3340498<br>
MD5sum: d57c9dc5d1d22c38edeec64902755179<br>
SHA1: 6f1ad45da2c535f799268e13f9b7f81fcc6b151f<br>
SHA256: 9974beae6a435a5678e24d8e02abfefe36097e8db9c009920ee5cd783f68f019<br>
Description: gphoto2 digital camera library (development files)<br>
Homepage: <a href="http://www.gphoto.org/proj/libgphoto2/" target="_blank">http://www.gphoto.org/proj/libgphoto2/</a><br>
Description-md5: 09f6d0ae3f118a398b90fb84845618e0<br>
Bugs: <a href="https://bugs.launchpad.net/ubuntu/+filebug" target="_blank">https://bugs.launchpad.net/ubuntu/+filebug</a><br>
Origin: Ubuntu<br>
Supported: 9m<br>
<br>
<br>
<br>
Tully<br>
<br>
<br>
On Sun, Sep 7, 2014 at 3:01 AM, Vincent Rabaud <<a href="mailto:vincent.rabaud@gmail.com" target="_blank">vincent.rabaud@gmail.com</a>><br>
wrote:<br>
<br>
> Hi all,<br>
><br>
> just a thought: we've had problems with Quantal and Oneiric builds in the<br>
> past. And I see the same thing now on Saucy (<br>
> <a href="http://jenkins.ros.org/view/IbinS32/job/ros-indigo-rospilot_binarydeb_saucy_i386/" target="_blank">http://jenkins.ros.org/view/IbinS32/job/ros-indigo-rospilot_binarydeb_saucy_i386/</a><br>
> simply because for some reason,<br>
> <a href="http://packages.ubuntu.com/lucid/libgphoto2-2-dev" target="_blank">http://packages.ubuntu.com/lucid/libgphoto2-2-dev</a> was not released in<br>
> Saucy).<br>
> Indigo is also an LTS for 5 years and I doubt we'll keep maintaining 10<br>
> Ubuntu distributions.<br>
><br>
> Wouldn't completing REP003 with dropping an Ubuntu distribution once it's<br>
> out of life a good thing ? Do we have stats on package downloads to back<br>
> that up ? Docs for what to drop here: <a href="https://wiki.ubuntu.com/Releases" target="_blank">https://wiki.ubuntu.com/Releases</a><br>
> That would also obviously make bloom and builds faster (or cheaper).<br>
><br>
> Thoughts ?<br>
><br>
> _______________________________________________<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="http://lists.ros.org/mailman/listinfo/ros-release" target="_blank">http://lists.ros.org/mailman/listinfo/ros-release</a><br>
><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.ros.org/pipermail/ros-release/attachments/20140907/953fc4be/attachment-0001.html" target="_blank">http://lists.ros.org/pipermail/ros-release/attachments/20140907/953fc4be/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
_______________________________________________<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="http://lists.ros.org/mailman/listinfo/ros-release" target="_blank">http://lists.ros.org/mailman/listinfo/ros-release</a><br>
<br>
<br>
End of ros-release Digest, Vol 35, Issue 3<br>
******************************************<br>
</blockquote></div><br></div></div></div></div></div>
</blockquote></div></div></div><br></div>
<br>_______________________________________________<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="http://lists.ros.org/mailman/listinfo/ros-release" target="_blank">http://lists.ros.org/mailman/listinfo/ros-release</a><br>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
ros-release mailing list<br>
<a href="mailto:ros-release@code.ros.org">ros-release@code.ros.org</a><br>
<a href="http://lists.ros.org/mailman/listinfo/ros-release" target="_blank">http://lists.ros.org/mailman/listinfo/ros-release</a><br>
<br></blockquote></div><br></div>