| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
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.
Please take a look at this repository:
https://github.com/felixduvallet/ros-...
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-pract...
I hope these resources help you.
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: 2017-02-05 20:40:39 -0600
Seen: 617 times
Last updated: May 26 '20
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
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.
See .travis.yml for a simple example that tests against two ROS releases.