Push based builds using Jenkins and GIT

Recently we switched to Git as our Version Control System solution and I still like it. Coming from “(good) old” CVS we used Jenkins as CI server polling CVS for changes. Besides other nice features and advantages, Git also brings nice commit hooks (well, CVS also does but I finally got to use this nice feature).

Using the post-receive hook you can use your favorite scripting language to do some kick-ass checking when a git commit/push has been made. We first started to use a common approach for every repository and created the post-receive hook like this:

/usr/bin/curl --user USERNAME:PASS -s \


Configure your Jenkins job to be able to “Trigger builds remotely” and use an authentication token (1qaz2wsx in this example).

Now two issues appear:

  1. We need to change the PROJECTNAME for every single repository
  2. In case of more projects/modules in one repository we can’t figure out what specific Jenkins job has to be run.
I solved both issues using the git diff-tree feature; after a commit/push the diff-tree option will show which specific folder has been modified:
rodmidde-lan:confluence rodmidde$ git diff-tree --name-status HEAD
M	digiArchief
The following script does the trick for me, it uses the diff-tree option and kicks the corresponding Jenkins job (assuming the Jenkins job is named after the changed git project/module:
changeSet=(`git diff-tree --name-status HEAD`)
for(( i=0; i<${#changeSet[@]}; i++))
  if [ ${changeSet[$i]} == "M" ]
    /usr/bin/curl --user USERMAME:PASS -s \



Feel free to leave suggestions, improvement and use the script if you like. Questions always welcomed!



  • Facebook
  • LinkedIn

3 thoughts on “Push based builds using Jenkins and GIT

  1. It is customary to have just a single solution/project/module in a Git repository, so you should not have to pass an additional value to be able to specify what Jenkins job to use.

    If you use multiple solutions in a single repository the history of your entire repo will represent those multiple solutions. It makes it harder to see the history of a single solution.

    See http://kiln.stackexchange.com/questions/500/should-i-use-more-than-one-repository for some more background.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>