Job not executing on Jenkins with the Docker plugin

Jenkins is one of my favourite tools. Docker is in that league too. Putting them together will really leverage the strengh of both tools. The Docker plugin can do that for you. This plugin can run a Docker container as a Jenkins slave on your Docker host. If the job on the slave is done, the container will be removed automatically.

However when running it on one particular Jenkins instance, it did not work! The slave was created, but somehow the job was not executed and stayed in the queue. On other Jenkins instances it did work. What was going on? After a while i figured it out. The job used for testing, was not a freestyle job. I used a multiconfiguration job accidently. After changing the job to a freestyle job, it worked like a charm!

Creating tags or branches for Subversion based on Hudson builds

Hudson has a builtin mechanism for tagging. Using this default mechanism helps a lot. However if you have multi-module jobs, you could still be stuck making the same changes in all those paths. Especially when you want to create branches instead of tags. Of course these manual changes are very errorprone. Especially when you are in a hurry. So it can be improved and that’s what this Ant script is about. Read more

Trigger a Hudson build from Subversion on Windows

You can configure Subversion to trigger a build in Hudson when anything is commited into a repository. You do this by using the post-commit hook on your Subversion repository. Nearly all the samples i found work on a Unix/Linux machine. They all tell you to use something called wget, but wget is not something that comes with Windows. So you need to get a Windows version for it. Here is one that worked for me.

The content of the post-commit hook on your Subversion repository should look something like:

E:\programs\wget -b http://yourserver:8080/job/yourjobname/build

Some tips