3 minutes

GIT + Rails + Rcov + Jenkins = Continuous Integration

Simple and easy to configure continuous integration environment

Published Apr 24, 2012 in programming with tags: ci git hooks hudson rails rcov

Let’s set up a simple and easy to configure continuous integration environment to run automated tests and generate coverage reports for our code.

The setup consists of three steps. In the end we’ll have an automated setup which requires no further steps to use it!

Initial Situation

We have a Ruby on Rails project under GIT source control on which we want to run tests and generate coverage reports using Jenkins.

The repository consists of several branches, but the main (and interesing) branches are development, staging and master.

Tests and coverage reports should be generated for the staging and master branches every time something is commited into them.

So far so good, let’s get started.


I’m assuming that you already have the following environment up and running, If not - well…

1st - Configure the build job

I suggest you include the rcov gem in your Gemfile under the test group to assure it’s getting installed on the build server. If you don’t want to, install the gem on your build server.

group :test do
  gem 'rcov'

Create a new jenkins build job for your project and configure it.

  • Select Git under Source-Code-Management and add your build branches. In your case they would be staging and master
  • Add execute shell as build step and paste the following script, adjust the steps as you see fit for your case
# setup env
export RAILS_ENV=test

# Prepare for rcov
[ -d "coverage" ] && rm -rf coverage
mkdir coverage

# install bundle
bundle install --deployment --without development

# prepare database
mv config/database.example.yml config/database.yml
bundle exec rake db:drop
bundle exec rake db:create
bundle exec rake db:schema:load
bundle exec rake db:seed

# run tests and coverage
bundle exec rake test
bundle exec rake rcov
  • Check the Publish Rcov report option under **post-build-actions and set the Rcov report directory to coverage. Adjust the Coverage metric targets as desired but the default values are a good start.

That’s it for the basic jenkins job configuration, you can of course define other options as well, I for example use e-mail notifications as well.

2nd - Configure git hook for to trigger build process

Now, I want my build job to be triggered every time I merge into the staging or master branch. To achieve this I’m using the git post-update hook. You can, of course use the hook on your local machine without using a central GIT server. It suffices if you’re working alone or simply can’t edit GIT hooks on your repository server (which is a sad thing).

But let’s assume we have a central GIT server, so add the following script as post-update hook on your git server. The hooks are located in the git repository directory under your-repository/hooks/post-update. You can simply replace the file located there, important is the filename post-update.

# trigger jenkins build after post-update into specific branch
#if [[ `git rev-parse --abbrev-ref HEAD` =~ $stages ]]; then
	curl https://hudson.yourdomain.com/job/Your-Job/build?delay=0sec

Finally, the hook must be marked as executable, else it won’t work:

chmod +x post-update

And this part’s done too!

3rd - Develop, merge, push

The setup is complete, every time something ist commited into the staging or master branch and pushed to the GIT server your jenkins job gets triggered which in turn runs your tests and generates rcov coverage reports.

less than 1 minute

Rails 3.1 devise_for breaks db:migrate - fix

Maybe you've encountered this incredible annoying devise bug which prevents you from successfully running rake tasks like db:migrate, db:schema:load and so on..

Published Apr 21, 2012 in programming