| || |
Bamboo vs. Hudson (Jenkins)
Which do you prefer as far as Continuous Integration?
Bamboo or Hudson (Jenkins)
Why do you prefer one over the other, and which cases would be best for both?
I'm using bamboo now, I've setup Jenkins CI at a couple other companies in the past and like Jenkins quite a bit.
Some observations I have
+ Popular open source, easy to find plugins for. (for example, there's a testswarm plugin for Jenkins, and I had to write my own set of build scripts to do the same in bamboo because a plugin didn't exist)
+ Easy to find other users and get help on Jenkins.
+ Free, and easy to setup
- Does not do automatic branching/merging
+ Supports automatic branching and merging (This is the main reason my current company uses Bamboo, because we want to automatically branch our CI plans and make sure all our dev branches are covered by CI, in Jenkins, each branch and merge means we'd have to copy and reconfigure each plan)
+ Integrates well with rest of Atlassian suite. So if you use Jira for bugs and story management, and confluence for documentation, it's easy to get bamboo to auto close stories/bugs as they're deployed, and update confluence documentation with each completed story.
+ Has some cool bells and whistles like detecting if a plan is currently deadlocked. (by comparing it against a threshold of build times of previous builds, like if a build is taking 50% longer to build the the last successful build)
- It's hard to find plugins for non-common tasks or setup. (For example, I couldn't find a TestSwarm plugin for Bamboo)
- It's less popular than Jenkins. Hard to find other users to talk shop or ask for help.
I like Bamboo more. But when I need to write complicated custom build scripts because a plugin doesn't exist. Then I wish I had Jenkins. But I think the Automatic Branching/Merging support makes Bamboo a far nicer workflow for developers.
Last edited by dlai; 08-20-2013 at 03:01 PM.
My favorite right now is actually Travis-CI.
Automatic branching, spawns a clean new virtual machine with each job (so don't have to worry about dirty environment, and cloud based.
I'm currently using Travis in my open source projects like https://travis-ci.org/wiredrive/wtframework
Integrates well with github. It marks my branches red when it's unstable so people know not to pull from it when unit and integration tests arn't passing.
Bamboo or Hudson
Bamboo vs Hudson, at an incredibly exterior stage, look like to move toward down to Bamboo. I work on it and I'm not worried in relation to hosting.
Originally Posted by Mike_Branco
> It has bunch of reports are nice, but not important.
> It can report you via email, RSS, IM, an IDE plugin.
The price of a Bamboo permit is quite little.
Hope This helps.