[ros-users] Software Status Reporting and Custom Builds

Edwards, Shaun M. sedwards at swri.org
Fri Sep 6 13:48:45 UTC 2013


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?

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 Adolfo Rodríguez Tsouroukdissian
Sent: Friday, September 06, 2013 2:50 AM
To: User discussions
Subject: Re: [ros-users] Software Status Reporting and Custom Builds

On Fri, Sep 6, 2013 at 4:59 AM, Thomas Moulard <thomas.moulard at gmail.com<mailto:thomas.moulard at gmail.com>> wrote:
On Fri, Sep 6, 2013 at 11:29 AM, Edwards, Shaun M. <sedwards at swri.org<mailto:sedwards at swri.org>> wrote:
> Looks like the discussion has died down.  I agree with Adolfo's changes and
> will incorporate them.  Unfortunately, I didn't hear an overwhelming
> response that the entire ROS community would find the status reporting
> useful.  I had hoped to incorporate the status symbols into the broader ROS
> wiki, instead of the "Industrial" sub pages.  For now I will leave the
> status descriptions where they are and mark the ROS-Industrial specific
> packages appropriately.  Maybe over time we will see if others choose to use
> them.
Sorry, I am arriving a bit late but so far the easiest way I found to
validate the projects
I maintain is through GitHub+Travis.

By putting a badge in your root README.md file, it becomes easy to see
if the stack
is working fine or not:
(change the branch to fuerte or groovy to see release per release status)

You can have different .travis.yml file on different branches so that
you can check
for all currently maintained ROS versions.

The killer feature compared to the usual buildfarm is that it
annotated automatically
pull requests with the CI status so that you can see if you can merge
the pull request
safely or not.

Great that you bring this up Thomas. Another tool that I've seen you're using is coveralls<https://coveralls.io>, which adds much needed visibility to coverage information (free for open source projects).

As for the CLA, I am currently using on another project the one from
the Canonical
Harmony project:
http://www.harmonyagreemeI'm junts.org/<http://www.harmonyagreements.org/>
...and I keep the signature on echosign:

See the CONTRIBUTING.md of this project for instance:

I wasn't familiar with CLAs until this thread. It's good to start raising awareness on these things.

Thomas Moulard
ros-users mailing list
ros-users at code.ros.org<mailto:ros-users at code.ros.org>

Adolfo Rodríguez Tsouroukdissian
Senior robotics engineer
adolfo.rodriguez at pal-robotics.com<mailto:adolfo.rodriguez at pal-robotics.com>

c/ Pujades 77-79, 4º4ª
08005 Barcelona, Spain.
Tel. +34.93.414.53.47
Skype: adolfo.pal-robotics
Facebook<http://www.facebook.com/palrobotics1> - Twitter<http://twitter.com/#%21/palrobotics> - PAL Robotics YouTube Channel<http://www.youtube.com/user/PALRobotics>

AVISO DE CONFIDENCIALIDAD: Este mensaje y sus documentos adjuntos, pueden contener información privilegiada y/o confidencial que está dirigida exclusivamente a su destinatario. Si usted recibe este mensaje y no es el destinatario indicado, o el empleado encargado de su entrega a dicha persona, por favor, notifíquelo inmediatamente y remita el mensaje original a la dirección de correo electrónico indicada. Cualquier copia, uso o distribución no autorizados de esta comunicación queda estrictamente prohibida.

CONFIDENTIALITY NOTICE: This e-mail and the accompanying document(s) may contain confidential information which is privileged and intended only for the individual or entity to whom they are addressed.  If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of this e-mail and/or accompanying document(s) is strictly prohibited.  If you have received this e-mail in error, please immediately notify the sender at the above e-mail address.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ros.org/pipermail/ros-users/attachments/20130906/fb8c2b0e/attachment.html>

More information about the ros-users mailing list