Saturday, March 3. 2012
Jenkins (formerly hudson) is a very cool CI-Tool. It is easily possible to automate building, testing and deployment with Jenkins. It is possible to split the task into several Jenkins jobs. This has a few advantages:
I will give a short introduction how to setup such a build chain here.
To be consistent, it is important to deploy exactly the code which has been tested before. This can be achieved by copying the tested workspace into the next project. There are two plugins which help you to build such a szenario:
To play around this, let’s create two Jenkins jobs. Configure the first one as you normally would. E.g. check out source regulary from SVN and execute "
Next, you have two options: You can check "
The second job is configured with "
You can chain many more jobs, you can also execute them in parallel (for example a sonar analyse can be done parallel to the deployment). Here is a screenshot of a (still very small) build pipeline:
Now your workspace looks like a full checkout.
Display comments as (Linear | Threaded)