Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Atlassian Bamboo
Score 6.7 out of 10
N/A
Australian company Atlassian offers Bamboo, a continuous integration server.
$1,200
Travis CI
Score 7.3 out of 10
N/A
Travis CI is an open source continuous integration platform, that enables users to run and test simultaneously on different environments, and automatically catch code failures and bugs.
$69
per month
Webpack
Score 0.0 out of 10
N/A
Webpack is an open source build solution for web and NodeJS applications. At its core, webpack is a static module bundler for JavaScript applications. When webpack processes an application, it internally builds a dependency graph from one or more entry points and then combines every module a project needs into one or more bundles, which are static assets to serve content from. It does not require a configuration file to bundle projects.N/A
Pricing
Atlassian BambooTravis CIWebpack
Editions & Modules
1 Remote Agent
$1200
5 Remote Agents
$3200
10 Remote Agents
$5840
25 Remote Agents
$11,600
100 Remote Agents
$23,280
250 Remote Agents
$58,160
500 Remote Agents
$87,280
1000 Remote Agents
$133,840
2000 Remote Agents
$187,380
1 Concurrent Job Plan
$69
per month
Bootstrap
$69
per month 1 concurrent job
2 Concurrent Jobs Plan
$129
per month
Startup
$129
per month 2 concurrent jobs
5 Concurrent Jobs Plan
$249
per month
Small Business
$249
per month 5 concurrent jobs
Premium
$489
per month 10 concurrent jobs
Platinum
$794+
per month starting at 15 concurrent jobs
Free Plan
Free
No answers on this topic
Offerings
Pricing Offerings
Atlassian BambooTravis CIWebpack
Free Trial
NoYesNo
Free/Freemium Version
NoYesNo
Premium Consulting/Integration Services
NoNoNo
Entry-level Setup FeeNo setup feeNo setup feeNo setup fee
Additional DetailsDiscount available for annual pricing.
More Pricing Information
Community Pulse
Atlassian BambooTravis CIWebpack
Considered Multiple Products
Atlassian Bamboo
Chose Atlassian Bamboo
We selected Bamboo because its capabilities to integrate with other Atlassian products specially Jira Software, Bitbucket and in some useful scenarios with Confluence. Also, we found these pros important for us: great user interface, easily agent deployment, Docker …
Chose Atlassian Bamboo
Bamboo's ability to integrate with Bitbucket and Jira (the other two key systems we use) pretty much sealed the deal on our decision to choose Bamboo over other alternatives. Being able to map every build result back to the relevant code changes and Jira issues are just too …
Chose Atlassian Bamboo
Jenkins is the only other we had briefly considered for continuous deployment type of products, but being open source could not get the same level of reliability and support offered from Bamboo's product maturity.
Chose Atlassian Bamboo
Bamboo has a friendlier interface than either TeamCity or Jenkins and has better integration with Jira and Bitbucket
Chose Atlassian Bamboo
We looked at Bitbucket and some other providers but they did not have the full requirements that we needed from a customization perspective. We wanted customization while keeping a lot of the configurability intact.
Chose Atlassian Bamboo
In the beginning we had selected Bamboo and were down the path of going all in for all of our projects. However after about a year we decided that Azure DevOps was better suited for our business needs. We are now in the process of migrating everything off of the Bamboo …
Chose Atlassian Bamboo
We used Jenkins before for our projects.
While Jenkins has an extensive plugins list that makes it more flexible to integrate it with other tools, we switched to Bamboo for nicer User Interface but mostly for the seamless integration with Jira and Bitbucket. Also Bamboo has more …
Chose Atlassian Bamboo
Bamboo is great tool when compared to the open-source alternative Jenkins, with mainly the same functionality in both it really shines with its integration of the Atlassian product line. Jenkins works really well with a huge community of users and plenty of plugins that are …
Chose Atlassian Bamboo
We chose Bamboo over Jenkins for 2 reasons - one, for its tight integration amongst all the products in the tool suite. We find explicit value in the traceability from JIRA issues all the way down to the Bamboo build that was triggered by the check in of those issues. The …
Chose Atlassian Bamboo
Bamboo has these advantages while asana does not:
  • Easy to configure
  • Easy to use
  • Clean UI and easy permission controls
Chose Atlassian Bamboo
Jenkins works great, but Bamboo is just fantastic when integrated with other Atlassian tools. Since we were using JIRA and Bitbucket, we went for Bamboo.
Chose Atlassian Bamboo
Bamboo's seamless integration with Bitbucket made it a simple choice, and I couldn't be happier with its ease of use, logging, and reliability.
Chose Atlassian Bamboo
We selected bamboo after a thorough review process, we considered the following aspects:
  • Ease of use, cost, scalability, plugins, setup and maintenance, community and product support
  • Made sure it integrated with JIRA and Confluence
Chose Atlassian Bamboo
I use bamboo because it is mandated as the CI/CD solution to use across the organization that I work for. If I were working on my own project, I would almost certainly use a free solution like Travis CI or just spin up my own build servers using Docker, AWS, or something like …
Chose Atlassian Bamboo
Bamboo won solely based on the fact we were "all-in" with Atlassian. TeamCity is now in the process of taking over as we transition off of Bamboo, and I think TeamCity stacks up nice against Bamboo thus far (too soon to tell).
Chose Atlassian Bamboo
Bamboo integrates directly with our bug system (Jira) and source control system (Bitbucket). It allows us to get what we need to done without worrying about how it works with our other systems.
Chose Atlassian Bamboo
Bamboo is hands-down the best of these options if you rely on other products of Atlassian origin. Bamboo is not just built for teams, but teams-of-teams and teams of many workers. It has the administrative features you need to manage and maintain CI at scale. Enterprise model …
Chose Atlassian Bamboo
I didn't select Bamboo. I mentioned how it compared in other parts of this review, but to summarize:

  • Pros: easier to use and cleaner UI
Travis CI
Chose Travis CI
Jenkins is probably the leading choice for automation and has loads of features and a large community behind it, but it can be overkill for many projects. It also has more of a web 1.0 look and interface.
CircleCI is another similar big competitor, but cannot compete with Travis …
Chose Travis CI
There are a few other options out there, CircleCI, Codeship and Wrecker would be a few good ones I can also recommend, each one has its particularity but I believe Travis has the best interface and flexibility of all of them.
I'd recommend trying them all and seeing which one …
Chose Travis CI
Jenkins is much more complicated to configure and start using. Although, one you have done that, it's extremely powerful and full of features. Maybe many more than Travis CI. As per TeamCity, I would never go back to using it. It's also complicated to configure but it is not …
Chose Travis CI
There are a number of alternatives to Travis CI, but Travis remains the most popular, since it was one of the first to show up. It has a lot of examples, support for building dozens of languages, and good documentation. Significant portions of the system are open source, so you …
Webpack

No answer on this topic

Best Alternatives
Atlassian BambooTravis CIWebpack
Small Businesses
GitLab
GitLab
Score 8.8 out of 10
GitLab
GitLab
Score 8.8 out of 10
GitLab
GitLab
Score 8.8 out of 10
Medium-sized Companies
GitLab
GitLab
Score 8.8 out of 10
GitLab
GitLab
Score 8.8 out of 10
GitLab
GitLab
Score 8.8 out of 10
Enterprises
GitLab
GitLab
Score 8.8 out of 10
GitLab
GitLab
Score 8.8 out of 10
GitLab
GitLab
Score 8.8 out of 10
All AlternativesView all alternativesView all alternativesView all alternatives
User Ratings
Atlassian BambooTravis CIWebpack
Likelihood to Recommend
6.4
(0 ratings)
6.0
(0 ratings)
-
(0 ratings)
Usability
9.3
(0 ratings)
5.0
(0 ratings)
-
(0 ratings)
Support Rating
7.3
(0 ratings)
4.0
(0 ratings)
-
(0 ratings)
User Testimonials
Atlassian BambooTravis CIWebpack
Likelihood to Recommend
Large companies will find it particularly useful, but smaller companies and independent developers will not be able to afford the cost, and will not see many advantages compared to using an open source solution. However, having some software to handle continuous integration build servers as well as deployments, and doing this consistently between products, is absolutely essential.
Read full review
TravisCI is suited for workflows involving typical software development but unfortunately I think the software needs more improvement to be up to date with current development systems and TravisCI hasn't been improving much in that space in terms of integrations.
Read full review
No answers on this topic
Pros
  • Continuous Deployment - you can use Bamboo to automatically build and deploy whenever there are changes in the source code.
  • Continuous Integration - by integrating the automated tests and the integration tests before deploying you make sure you know immediately if the latest code fits into the whole scheme of apps.
  • Integration with Jira and Bitbucket.
  • Flexibility with the program language used for builds: Maven, Ant, PowerShell, any command line tools.
Read full review
  • It's simple and easy to get started (it can detect the language being used based on build configuration files like a Maven pom.xml).
  • It's free (as in beer) for open source projects.
  • It has a responsive staff (you can file issues on GitHub to ask for new languages or packages to be supported, and the turnaround time isn't too bad for the free offering).
  • The user interface is beautiful and easy-to-use, including features like live-tailing in-progress builds.
  • It supports specifying private environment variables and encrypted credentials, so that you can safely automate deployments (for example, pushing built docker images to DockerHub).
Read full review
No answers on this topic
Cons
  • Extremely hard barrier to entry for non-backend developers
  • Blackbox makes it hard to customize functionality
  • The inability to add features without breaking core functionality
  • No cloud solution
  • Tasks cannot be put in if/else statements
  • No clear right way to form build plans
Read full review
  • Travis CI is a fairly mature platform now, and most, if not all of the common complaints have been improved. This includes documentation and logs with color support.
Read full review
No answers on this topic
Usability
Bamboo offers solid usability for teams looking for an integrated, scalable CI/CD solution, especially those using Atlassian tools. Its interface is intuitive for existing Atlassian users, and its focus on deployment automation makes it a strong option for continuous delivery. However, its complexity and cost may pose challenges for small teams or those new to CI/CD. Overall, Bamboo’s usability shines in environments where ease of integration and streamlined workflows are prioritized. Still, it may require more effort for teams unfamiliar with its setup or without dedicated resources.
Read full review
TravisCI hasn't had much changes made to its software and has thus fallen behind compared to many other CI/CD applications out there. I can only give it a 5 because it does what it is supposed to do but lacks product innovation.
Read full review
No answers on this topic
Support Rating
Support for Bamboo has started lack a little over the years. Atlassian has been moving more towards Bitbucket Pipelines and away from the on-premise install of Bamboo. While the tool is still great, it may take a little bit of time to get a question answered by official support.
Read full review
After the private equity firm had bought this company the innovation and support has really gone downhill a lot. I am not a fan that they have gutted the software trying to make money from it and put innovation and product development second.
Read full review
No answers on this topic
Alternatives Considered
We chose Bamboo over Jenkins for 2 reasons - one, for its tight integration amongst all the products in the tool suite. We find explicit value in the traceability from JIRA issues all the way down to the Bamboo build that was triggered by the check in of those issues. The second reason was for support - we didn't want the burden of figuring out how to support Jenkins in our production environment, as can be the case with so many open source products.
Read full review
Jenkins is probably the leading choice for automation and has loads of features and a large community behind it, but it can be overkill for many projects. It also has more of a web 1.0 look and interface. CircleCI is another similar big competitor, but cannot compete with Travis CI's free account [in my opinion].
Read full review
No answers on this topic
Return on Investment
  • Bamboo was neither very positive or negative. Most of our spend was in man hours on research and development
  • We felt it was worth it for larger projects
  • Smaller projects had too much setup and run and caused a negative ROI
Read full review
  • It saves you in infrastructure and setup costs, since running a server and installing and maintaining Jenkins can be a hassle.
Read full review
No answers on this topic
ScreenShots