Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

REP 137 only affects Groovy and later as well as wet packages only. Setting up a build farm for Fuerte and dry stuff will be quite an effort. I would not recommend doing that.

For Groovy (or later) and wet packages you can find a draft at http://www.ros.org/wiki/buildfarm but it might not be complete.

If you plan to release the packages anyway you should really consider using the existing ROS buildfarm for the job.

As soon as Hydro is released (and Fuerte is EOL-ed) the buildfarm will receive another update to fully implement the features specified in REP 137. This should make it even easier to run a custom buildfarm.

REP 137 only affects Groovy and later as well as wet packages only. Setting up a build farm for Fuerte and dry stuff will be quite an effort. I would not recommend doing that.

For Groovy (or later) and wet packages you can find a draft at http://www.ros.org/wiki/buildfarm but it might not be complete.

If you plan to release the packages anyway you should really consider using the existing ROS buildfarm for the job.

As soon as Hydro is released (and Fuerte is EOL-ed) the buildfarm will receive another update to fully implement the features specified in REP 137. This should make it even easier to run a custom buildfarm.

Update:

By running your own buildfarm you will get exactly the same functionality as the ROS buildfarm. Customizing it is a completely different thing. The ROS buildfarm does: packaging into Debian packages from gbp repos, integration build from the source repos includes running all tests, and doc jobs.

For setting up the buildfarm you do not have to configure dependencies etc. This is all done automatically. All jobs on jenkins.willowgarage.com are autogenerated - there is not a single manually configured job anymore.