Continuous integration environment

[Paweł Paprota]

On 11/12/2012 10:31 PM, Eric Theise wrote:
> Got it to green.  8-)
>

Looks good!

I've been thinking some more about the CI stuff... some questions:

1. Should we go for one "official" CI environment/account? 
cruise.osm.org looks like a good start if we want to have something in 
our own infrastructure.

2. Should it be possible for anyone to add their own repo/branch to such 
environment? Otherwise only the master/deploy branch of the main repo 
will be built and everyone will have to set up their own CI.

I personally have most experience with Hudson/Jenkins. In comparison, 
Cruise Control and Travis look rather simplistic. What would be useful 
is to have some code metrics, test breakdown, test coverage etc. This 
stuff is cheap to set up and can be helpful for developers and code 
reviewers.

Quick search brought up several interesting things:

https://wiki.jenkins-ci.org/display/JENKINS/Ruby+metrics+plugin
https://wiki.jenkins-ci.org/display/JENKINS/Configuring+a+Rails+build

I also managed to find some random live instance of Jenkins running 
Ruby/Rails builds:

https://jenkins.id774.net/jenkins/job/automaticruby/

Test coverage reports look very tempting:

https://jenkins.id774.net/jenkins/job/automaticruby/ws/coverage/rcov/index.html

What do you think? Now that we know that Rails Port can be built 
automatically without problems, setting up something like Jenkins should 
be quite easy.

Paweł