Continuous integration environment

[Shaun McDonald]

Some background.

I setup http://cruise.osm.org a few years back on my server. A while back it stopped working with some of the rails upgrades, and I've been meaning to get it working again. I decided that with there being no new development in cruisecontrol.rb and Jenkins being more flexible, also at my previous job we were moving the projects from cruisecontrol.rb to Jenkins, thus I had some experience with it, so I was going to move the OSM one over too. Jenkins does have a lot of development and plenty of plugins available.

Before reading this thread I had already started making that move (which incidentally is also on a new server I have and part of the reason for getting this project moving again). I've now got it running: http://jenkins.smsm1.net and am willing to open up the maintenance to others who wish to help, and also add more projects.

Shaun


On 13 Nov 2012, at 11:19, Paweł Paprota <ppawel at fastmail.fm> wrote:

> 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ł
> 
> 
> _______________________________________________
> rails-dev mailing list
> rails-dev at openstreetmap.org
> http://lists.openstreetmap.org/listinfo/rails-dev