[ros-users] Software Status Reporting and Custom Builds

[William Woodall]

I forgot to mention that there is a jenkins plugin which performs the same
pull request verification as travis-ci, but we haven't set that up yet.

--


On Fri, Sep 6, 2013 at 11:10 AM, William Woodall
<william at osrfoundation.org>wrote:

> So, yes travis-ci is awesome, I use it frequently to build ROS and ROS
> agnostic things:
>
> https://github.com/wjwwood/serial/blob/master/.travis.yml
>
> https://github.com/ros-perception/perception_pcl/blob/hydro-devel/.travis.yml
> https://github.com/ros-infrastructure/bloom/blob/master/.travis.yml
>
> But I would also point out that if you have your repository (containing
> one or more packages) listed in the `source.yaml` file for a given ROS
> distribution, like this one:
>
> https://github.com/ros/rosdistro/blob/master/hydro/source.yaml
>
> Then our buildfarm (jenkins.ros.org) will do "devel" jobs for your
> packages which build it, run the tests, and report back to you. The benefit
> of this approach over travis-ci is that for catkin packages it already
> knows how to resolve your dependencies for you, build your code and run the
> tests (and hook into the test results). So it is a bit more zero
> configuration than travis-ci for catkin (ROS) packages.
>
> Not saying we shouldn't use travis-ci, I just wanted to make sure people
> knew about this option.
>
> --
>
>
> On Fri, Sep 6, 2013 at 10:51 AM, Thomas Moulard <thomas.moulard at gmail.com>wrote:
>
>> On Fri, Sep 6, 2013 at 10:48 PM, Edwards, Shaun M. <sedwards at swri.org>
>> wrote:
>> > All,
>> >
>> >
>> >
>> > I looked at Travis briefly but it seemed to be set up for stand-alone
>> > libraries or those with minimal dependencies.  I assume “installing”
>> ROS was
>> > not an option and building ROS packages would be impossible.  Am I
>> missing
>> > something?
>>
>> Travis is providing you with a Ubuntu 12.04 virtual machine at each build.
>> Starting from that, there is no reason to not be able to install ROS on
>> it and
>> check your build.
>> The tricky part is that they decide whether or not your use is "fair" or
>> not.
>> Without notifying them first a full switch of the ROS community is
>> therefore
>> risky. AFAIK if your build takes less than 30 minutes they are fine.
>>
>> So for vision_visp I am fine:
>> https://travis-ci.org/laas/vision_visp/branches
>>
>> As for how to do it, it is exactly what you would do on your own machine.
>> The .travis.yml call the .travis/before_install script which setup the apt
>> repositories, get the key and run apt-get install.
>>
>> https://github.com/stack-of-tasks/redundant_manipulator_control/blob/master/.travis.yml
>>
>> https://github.com/stack-of-tasks/redundant_manipulator_control/blob/master/.travis/before_install
>>
>> Best,
>> --
>> Thomas Moulard（ムラー トマ）
>> CNRS-AIST JRL (Joint Robotics Laboratory), UMI3218/CRT, Tsukuba, Japan
>> http://thomas.moulard.net | Tel: +81 (0)80-9436-1985 | GPG Key Id:
>> 516FC68F31496D58
>> Add me on LinkedIn: http://www.linkedin.com/in/moulard
>> _______________________________________________
>> ros-users mailing list
>> ros-users at code.ros.org
>> http://lists.ros.org/mailman/listinfo/ros-users
>>
>
>
>
> --
> William Woodall
> ROS Development Team
> william at osrfoundation.org
> http://williamjwoodall.com/
>



-- 
William Woodall
ROS Development Team
william at osrfoundation.org
http://williamjwoodall.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ros.org/pipermail/ros-users/attachments/20130906/c7c76fe3/attachment.html>