[ros-users] Software Status Reporting and Custom Builds

Edwards, Shaun M. sedwards at swri.org
Fri Sep 6 19:10:22 UTC 2013


I’m not sure I quite understand what you are saying here, but it would be my preference to use the build farm over anything else.  Here are a couple of questions:

*         Can the build farm build multiple repo branches for a single ROS release?  We typically have a stable release branch (groovy) and a similar branch with the latest and greatest (groovy_devel).  Is it possible to build both on the build farm?

*         Does the build farm monitor repos for changes or is it triggered in the release process and/or when dependencies change?  The ROS-I Jenkins server monitors the repo and triggers a build whenever anything has changed.

*         Can we add metrics or other analysis to the build farm, like Bosch did (see Tully’s email)?  Things like reporting warning, line counts, and code coverage could be done without much configuration of the build server (just minor modifications to the build scrips).  Jenkins would have to be reconfigured to display the associated plots/charts as well.

Shaun Edwards
Senior Research Engineer
Manufacturing System Department

Join the ROS-Industrial Developers List<https://groups.google.com/group/swri-ros-pkg-dev/boxsubscribe>
Southwest Research Institute

From: ros-users-bounces at code.ros.org [mailto:ros-users-bounces at code.ros.org] On Behalf Of William Woodall
Sent: Friday, September 06, 2013 1:10 PM
To: User discussions
Subject: Re: [ros-users] Software Status Reporting and Custom Builds

So, yes travis-ci is awesome, I use it frequently to build ROS and ROS agnostic things:


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:


Then our buildfarm (jenkins.ros.org<http://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<mailto:thomas.moulard at gmail.com>> wrote:
On Fri, Sep 6, 2013 at 10:48 PM, Edwards, Shaun M. <sedwards at swri.org<mailto: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:

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.

Thomas Moulard(ムラー トマ)
CNRS-AIST JRL (Joint Robotics Laboratory), UMI3218/CRT, Tsukuba, Japan
http://thomas.moulard.net | Tel: +81 (0)80-9436-1985<tel:%2B81%20%280%2980-9436-1985> | GPG Key Id:
Add me on LinkedIn: http://www.linkedin.com/in/moulard
ros-users mailing list
ros-users at code.ros.org<mailto:ros-users at code.ros.org>

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

More information about the ros-users mailing list