Recommended setup for Travis-CI?

I've seen a few ROS projects with a Travis-CI configuration for automatically running tests.

Is there a "best-practice" script for properly setting up a ROS environment for running tests? I'm trying to create my own based on the examples I see, but I'm finding it's a bit complicated, with little ROS documentation to guide me.

Asked by Cerin on 2017-02-05 21:40:39 UTC

Comments

Not really an answer, but you might take a look at industrial_ci. Contrary to the name, it's not limited to 'industrial' ROS pkgs at all, and takes care of a lot of things wrt Travis & ROS.

Asked by gvdhoorn on 2017-02-06 03:40:13 UTC

See .travis.yml for a simple example that tests against two ROS releases.

Asked by gvdhoorn on 2017-02-06 03:41:56 UTC

Answers

Not an answer #2 though, you might want to check http://wiki.ros.org/CIs for existing CI software/service options.

Depending on what you want to test though, if you're really in need for self-contained example, maybe velodyne has a good, short example.

Asked by 130s on 2017-02-06 20:22:11 UTC

Comments

Please take a look at this repository:

https://github.com/felixduvallet/ros-travis-integration

Citation:

This repository contains a .travis.yml file for setting up continuous integration (through Travis-CI) for any ROS package.
...
This repository also contains several example (i.e. trivial) ROS packages that serve as example packages for Travis to build and test. They also showcase how to correctly handle dependencies (system and source).

With regards to best practices, there are many Travis-CI best practices blog posts out there, unfourtunatley not ROS specific. One example: https://eng.localytics.com/best-practices-and-common-mistakes-with-travis-ci/

I hope these resources help you.

Asked by Roberto Z. on 2020-05-26 02:11:52 UTC