My team was recently assigned to help out another team who had a bit too much to do for a bit too long. So, I wanted to see how easy or how hard it would be to use some of the tools that I’ve become quite use to. One of those tools of course is Jenkins. The idea was to set this new environment up to be a slave to my Master Jenkins Build Server running on Ubuntu while the slave would run on Windows. Of course Jenkins has a lot of features with regards to this and I managed to fiddle enough to get it to work and I’ve released another article called “Setup – Jenkins and Windows” where I take you through how to do this.
The next thing I’m going to do is get it to pull the source code from Team Foundation Server and running the tests so we can know when we break something. Just in case you were wondering, I do try to follow the Test Driven Development (TDD) way of writing code as much as possible and love the fact that it makes my life easier and safer. I’ve decided to write another article on this as well, but you’ll have to wait and see when it comes out whether you agree or disagree with the things I write in there J
I hope you enjoy this new platform that you can use for your CI…
So, there is now something called Jenkins in the world of Open Source Build Servers and it seems like it’s been around for a few months. Why is this remarkable? Well… Simply because Jenkins = Hudson. I was installing another server with Hudson today following the instructions in my article “Setup – Apache and Hudson” and only when I completed the install did I realise that Hudson is now actually called Jenkins. So, has anything changed? Nope, not really. Why did they decide to make this bold move? I can’t say, other than that there is some speculation that the guys over at Oracle wanted to start charging license fees for the use of Hudson and that the previously known Hudson guys then decided to for Hudson, rename it to Jenkins and to continue with the project in the old Open Source manner. Well, if this is true, then I am glad, because since I started using Hudson/Jenkins I haven’t looked back or had the urge to explore some of the other platforms out there. It simply works 🙂
To top it off, I obviously opted to uninstall Hudson and to install Jenkins and once that was done I thought that it might be a good idea to add/update another article to show you how to install the new Jenkins platform. You can find this article, called “Setup – Apache and Jenkins” here. I’m sure you’ll enjoy Jenkins as much as you’ve enjoyed Hudson and I’m also sure that we can expect to see this project grow in the coming months as we’ve seen it grow from the beginning. I wish them all the luck in their bold move and hope they continue to have fun 🙂 I know we will 🙂
Heads up though, I’m in the process of writing an article on how to use Jenkins as your Build Server runnig Continuous Integration for Ruby projects under Ruby Version Manager (RVM).