AppVeyor vs. Atlassian Bamboo

AppVeyor

AppVeyor

0 Reviews and Ratings

Atlassian Bamboo

Atlassian Bamboo

96 Reviews and Ratings

Overview
Product	Rating	Most Used By	Product Summary	Starting Price
AppVeyor	Score 0.0 out of 10	N/A	AppVeyor is a continuous Integration and Deployment service for Windows developers, from the company of the same name headquartered in Vancouver. The CI/CD service is available for Windows, Linux and macOS.	$0 per month Unlimited public projects, 1 concurrent job, 5 self-hosted jobs
Atlassian Bamboo	Score 6.7 out of 10	N/A	Australian company Atlassian offers Bamboo, a continuous integration server.	$1,200

Pricing

AppVeyor

Atlassian Bamboo

Editions & Modules

Open-Source: $0
per month Unlimited public projects, 1 concurrent job, 5 self-hosted jobs
Basic: $29
per month 1 private project, 1 concurrent job, 5 self-hosted jobs
Pro: $59
per month Unlimited private project, 1 concurrent job, 5 self-hosted jobs
Premium: $99
per month Unlimited private project, 2 concurrent jobs, 5 self-hosted jobs

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

Offerings

Pricing Offerings
AppVeyor	Atlassian Bamboo
Free Trial
No	No
Free/Freemium Version
Yes	No
Premium Consulting/Integration Services
No	No

Entry-level Setup Fee

No setup fee

No setup fee

Additional Details

—

—

More Pricing Information

Community Pulse
	AppVeyor	Atlassian Bamboo
Considered Both Products	AppVeyor No answer on this topic	Atlassian Bamboo Verified User Anonymous Chose Atlassian Bamboo Not well. Incentivized Helpful? Verified User Anonymous 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 … Incentivized Helpful? Verified User Anonymous 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 … Incentivized Helpful? Rob Domenico Senior Systems Administrator 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. Incentivized Helpful? Bayley Gaillard Site Reliability Engineer II Chose Atlassian Bamboo Bamboo has a friendlier interface than either TeamCity or Jenkins and has better integration with Jira and Bitbucket Incentivized Helpful? Verified User Anonymous 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. Incentivized Helpful? Kyle Kochtan Technical Lead 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 … Incentivized Helpful? Cristian Bodnarasec Senior Software Development Manager 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 … Incentivized Helpful? Verified User Anonymous 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 … Incentivized Helpful? Verified User Anonymous 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 … Incentivized Helpful? Verified User Anonymous Chose Atlassian Bamboo Bamboo has these advantages while asana does not: Easy to configure Easy to use Clean UI and easy permission controls Incentivized Helpful? Verified User Anonymous 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. Incentivized Helpful? FC Frank Coulter Database Operations Manager 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. Incentivized Helpful? Milan Shah Technical Architect 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 Incentivized Helpful? Erik Bean Web Developer 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 … Incentivized Helpful? Marc Smith CTO 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). Incentivized Helpful? Tanner Lovelace Principal Software Engineer 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. Incentivized Helpful? Verified User Anonymous 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 … Incentivized Helpful? Ken Yee Android Architect 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 Incentivized Helpful?

Best Alternatives
	AppVeyor	Atlassian Bamboo
Small Businesses	GitLab Score 8.7 out of 10	GitLab Score 8.7 out of 10
Medium-sized Companies	GitLab Score 8.7 out of 10	GitLab Score 8.7 out of 10
Enterprises	GitLab Score 8.7 out of 10	GitLab Score 8.7 out of 10
All Alternatives	View all alternatives	View all alternatives

User Ratings
	AppVeyor	Atlassian Bamboo
Likelihood to Recommend	- (0 ratings)	6.4 (0 ratings)
Usability	- (0 ratings)	9.3 (0 ratings)
Support Rating	- (0 ratings)	7.3 (0 ratings)

User Testimonials
	AppVeyor	Atlassian Bamboo
Likelihood to Recommend	No answers on this topic	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. Incentivized Erik Bean Web Developer Read full review
Pros	No answers on this topic	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. Incentivized Cristian Bodnarasec Senior Software Development Manager Read full review
Cons	No answers on this topic	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 Incentivized Jonathan Kempf, UXC UI Engineer Read full review
Usability	No answers on this topic	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. Incentivized Verified User Anonymous Read full review
Support Rating	No answers on this topic	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. Verified User Anonymous Read full review
Alternatives Considered	No answers on this topic	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. Incentivized Verified User Anonymous Read full review
Return on Investment	No answers on this topic	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 Kyle Kochtan Technical Lead Read full review
ScreenShots