lt101018's profile - activity

Are they different CI tools or they work together become a CI works for ROS? I find following passage but not quite understand it:

The ROS build farm is used to provide the official ROS packages and successfully works with a large number of repositories and packages. Beside building Debian packages it also provide continuous integration builds, GitHub pull request testing as well as documentation generation. Jenkins provides an easy interface to the result of all unit and rostests. It is build around the recommended ROS tools and uses Docker to perform easily repeatable results.

The Python package also provides a command line interface to use each job type in other environments, e.g. on any CI server (e.g. how to run a devel job on Travis) or locally. It can be used to deploy a custom build farm to build and release custom, optionally closed-source packages, build for platforms and architectures not provided by the official ROS build farm, and/or customize any part of the process to specific needs.

I'm currently looking for a CI which could integrated with bitbucket. I find a list of CIs here http://wiki.ros.org/CIs but an objective comparison is not provided. Could anyone give me some advice about the pros and cons of each CI?

Relationship between ROS build farm and Jenkins Are they different CI tools or they work together become a CI works for

Thank you I will try

CI recommendation I'm currently looking for a CI which could integrated with bitbucket. I find a list of CIs here http:/