How switching from Jenkins to Bamboo changed the way we work – Part 2

From last week

So, last week I wrote a lot about the differences, different terminology, and how Jenkins and Bamboo are, at least for the first part, pretty similar.

So, lets jump into…

The differences

The things Jenkins does better

Oh boy, this will be a long one.

Of course, with Jenkins being open source and having been around for decades now (Hudson was released Feb 2005), there are a lot more plugins in Jenkins than in Bamboo. Jenkins, quite literally, has support for everything that could even remotely be considered “alive” as far as tools are concerned.

And.. Well, this is a point that is no contest. Money. Jenkins doesn’t cost a thing. 0 € for as long as you want. This, of course, Bamboo can’t compete with.

Then, we have the overview. This is a point that I have to give to both. Jenkins does have better logs, shows you the test graph and coverage graph (which bamboo can’t do), and, at least for me, it does show the builds a bit better in general (you immediately see the red builds, the icon is much more visible).

The things Bamboo does better

And here’s where Jenkins fans will murder me.

Bamboo has better branch support. Sorry guys, but automatically creating branch builds, merging the master into a branch, and running tests without me even needing to press a button? Yes, thank you very much, I’ll take that functionality anytime.

And, no contest again, Bamboo has much better Atlassian tools support. Yes, you CAN use a plugin for Jenkins to show your builds in JIRA, but that’s about it. With Bamboo, you immediately see branch builds on Stash, issue builds on JIRA, and you can trigger builds from Stash as well.

This allows every JIRA user to see what’s going on in development, without needing any specific insight. Brilliant for Product Owners and Managers.

Again, the overview. While Jenkins displays the logs and the build status better, Bamboo has a much cleverer way of organizing the builds themselves. You have different stages, with multiple tasks in them. This allows for a brilliant overview in a multi-staged build, and immediately shows the failed stage and task. Plus, you have the deployment plans, which help a lot in planning your versions (splitting between testing, stages, and production)

 

This is all for this week, a bit shorter this time, because last week’s wall of text did seem a bit much. But be prepared for next week, as I’ll have some exciting news for you then.

Leave a Reply

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

*
*

15 − 4 =