We're trying it here: https://travis-ci.org/clearpathrobotics/um6 -Ryan On Fri, Sep 6, 2013 at 9:56 AM, Adolfo Rodríguez Tsouroukdissian < adolfo.rodriguez@pal-robotics.com> wrote: > > > > On Fri, Sep 6, 2013 at 3:48 PM, Edwards, Shaun M. 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? >> > I had the same question, and a colleague pointed me to the Travis > configuration file of an existing project: > > https://github.com/PowerDNS/pdns/blob/master/.travis.yml > > Yo can pretty much do anything you'd want to setup a ROS environment: > there's apt, shell commands, scripts, you name it. I don't know if there's > a limit to the workspace size though. One thing to take into account is > that the supported compilers and versions are fixed (eg. gcc 4.6 and clang > 3.2). More here: > > http://about.travis-ci.org/docs/user/languages/cpp > > Cheers, > > Adolfo > >> **** >> >> ** ** >> >> Shaun Edwards**** >> >> Senior Research Engineer**** >> >> Manufacturing System Department**** >> >> ** ** >> >> ** ** >> >> http://robotics.swri.org**** >> >> http://rosindustrial.swri.org/**** >> >> http://ros.swri.org**** >> >> Join the ROS-Industrial Developers List >> **** >> >> Southwest Research Institute**** >> >> 210-522-3277**** >> >> ** ** >> >> *From:* ros-users-bounces@code.ros.org [mailto: >> ros-users-bounces@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 >> wrote:**** >> >> On Fri, Sep 6, 2013 at 11:29 AM, Edwards, Shaun M. >> 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: >> https://github.com/laas/vision_visp >> (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 , 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/ >> ...and I keep the signature on echosign: >> https://www.echosign.adobe.com/en/home.html >> >> See the CONTRIBUTING.md of this project for instance: >> https://github.com/roboptim/roboptim-core/blob/master/CONTRIBUTING.md**** >> >> ** ** >> >> I wasn't familiar with CLAs until this thread. It's good to start raising >> awareness on these things.**** >> >> Thanks,**** >> >> Adolfo.**** >> >> >> Best, >> -- >> Thomas Moulard**** >> >> _______________________________________________ >> ros-users mailing list >> ros-users@code.ros.org >> http://lists.ros.org/mailman/listinfo/ros-users**** >> >> ** ** >> >> >> >> -- >> Adolfo Rodríguez Tsouroukdissian >> Senior robotics engineer >> adolfo.rodriguez@pal-robotics.com >> http://www.pal-robotics.com >> >> PAL ROBOTICS S.L >> c/ Pujades 77-79, 4º4ª >> 08005 Barcelona, Spain. >> Tel. +34.93.414.53.47 >> Fax.+34.93.209.11.09 >> Skype: adolfo.pal-robotics >> Facebook - Twitter- PAL >> Robotics YouTube Channel >> >> 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. **** >> >> _______________________________________________ >> ros-users mailing list >> ros-users@code.ros.org >> http://lists.ros.org/mailman/listinfo/ros-users >> >> > > > -- > Adolfo Rodríguez Tsouroukdissian > Senior robotics engineer > adolfo.rodriguez@pal-robotics.com > http://www.pal-robotics.com > > PAL ROBOTICS S.L > c/ Pujades 77-79, 4º4ª > 08005 Barcelona, Spain. > Tel. +34.93.414.53.47 > Fax.+34.93.209.11.09 > Skype: adolfo.pal-robotics > Facebook - Twitter- PAL > Robotics YouTube Channel > > 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. > > _______________________________________________ > ros-users mailing list > ros-users@code.ros.org > http://lists.ros.org/mailman/listinfo/ros-users > >