commentBlock = $("#comment_post_31830").find('.comment-blocks'); commentBlock.find('.loading').hide(); commentBlock.find('.see-all-comments').hide(); commentBlock.html("
<\/a>
\"it_user326337<\/a>
it_user326337<\/a>Customer Success Manager at PeerSpot<\/span><\/div>
<\/span>Consultant<\/span><\/div>
<\/i><\/div>
<\/i>Report as inappropriate<\/a><\/div><\/div><\/div>

Victor, is your overall preference for Jenkins still relevant today (since you wrote this review in February 2015)?<\/p><\/div>

<\/i>Like<\/span>(0<\/span>)<\/a><\/i>Reply<\/span><\/a><\/div>
<\/div><\/div>
<\/a>
\"it_user185772<\/a>
it_user185772<\/a>Senior Software Architect with 5,001-10,000 employees<\/span><\/div>
<\/span>Vendor<\/span><\/div>
<\/i><\/div>
<\/i>Report as inappropriate<\/a><\/div><\/div><\/div>

In most cases I prefer Jenkins over Bamboo. Jenkins is much more flexible and can be extended with plugins to do almost anything one can imagine. Bamboo, on the other hand, brings easier integration with the rest of Atlassian products (Jenkins can be integrated as well but it requires a bit more time) and it looks nicer (if that\'s important to anyone). I had many problems with Bamboo when I wanted it to do something that Atlassian didn\'t think of and had to resolve using some really ugly hacks. For example, when build jobs call deployments, there is no way to go back to the build job and do some post-deployment tasks. Another example would be duplication of build/deployment jobs. Often things that I can do with one Jenkins job requires several Bamboo jobs. Inability to provide input parameters (especially for deployment jobs) is very annoying. The list of Bamboo downsides goes on and on. Jenkins also has it\'s problems but they are much fewer than those of Bamboo.<\/p>\n\n

All in all, I\'d choose Jenkins.<\/p><\/div>