Australian company Atlassian offers Bamboo, a continuous integration server.
$1,200
1 remote agent
Bitbucket
Score 8.6 out of 10
N/A
Bitbucket is a Git repository and code collaboration platform, featuring automated testing and code deployment. Bitbucket Cloud Premium provides AI-powered development, more granular access controls, and enforced code quality, and Bitbucket Data Center provides a self-hosted option.
$0
Azure DevOps Server
Score 8.4 out of 10
N/A
Azure DevOps Server (formerly Team Foundation Server, or TFS) is the on-premise version of Azure DevOps. To license Azure DevOps Server an Azure DevOps license and a Windows operating system license (e.g. Windows Server) for each machine running Azure DevOps Server.
N/A
Pricing
Atlassian Bamboo
Atlassian Bitbucket
Azure DevOps Server
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
Free
$0
for up to 5 users
Standard
$3.30
per month per user
Premium
$6.60
per month per user
Bitbucket Data Center
starting at $44,000
per year 1 - 500
No answers on this topic
Offerings
Pricing Offerings
Atlassian Bamboo
Bitbucket
Azure DevOps Server
Free Trial
No
Yes
No
Free/Freemium Version
No
Yes
Yes
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
—
—
—
More Pricing Information
Community Pulse
Atlassian Bamboo
Atlassian Bitbucket
Azure DevOps Server
Considered Multiple Products
Atlassian Bamboo
Verified User
Engineer
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 …
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 …
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.
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 …
Verified User
Employee
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 …
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.
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 …
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).
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.
The majority of SCM tools are Git based. What makes this solution stand out from the rest is it's web-based interface, which implements version control standards very intuitively. As a result, the learning curve shortens and productivity is highly improved.
Bitbucket was inherited from an acquisition and not used by choice. The acquired company chose Bitbucket because - at the time - they were the market leader for private source code repositories and the team was already using JIRA.
The primary reasons we went with Bitbucket over TFS and/or other options are as follows: 1) Ability to integrate with other documentation and development tools we were using. 2) Cost - with our size and current business needs, we were able to implement what we needed in …
Bitbucket provides a better price compared to the others as well as private repositories for people who do not want everything they do to be completely public and accessible for all to see.
Drastically simpler both in pricing and ease of use than the competition. For only $10/month your team has unlimited private repos! That is an outright bargain! If you are a small team that doesn't require all of the advanced services that come with larger infrastructure and …
Azure DevOps is a fully integrated solution that solves all of the problems that our separate tools did in a much easier-to-use way. Before we implemented DevOps we had three different solutions that we had to integrate with each other and required a lot of manual intervention …
Overall Atlassian products seem to be less stable. Azure DevOps [Server (formerly Team Foundation Server)] also has Test Center and Build functionality built in. This prevents needing a handful of separate products loosely coupled together to get a comprehensive solution to …
Azure DevOps server has quite an upper hand while we compare it with other tools in the market. Its not just a tool in fact its been a complete suit. If we look out at other products available as alternative options to Azure DevOps Server, they are meant for a specific purpose …
The advantage of Team Foundation Server is the integration capability with Microsoft technologies and products, such as Visual Studio. Although this is an important consideration, Team Foundation Server is not a straightforward tool and needs to be improved to work seamlessly …
The JIRA integration with Bitbucket is a little nicer for sure, since they're both Atlassian products. Still, the Visual Studio and Azure integration with TFS made this a no-brainer for me.
Price-wise they are similar but you get a lot more with your TFS subscription. For the …
Based on the fact we are Microsoft shop, it makes sense and it has an great integration to RM for code release. At the time it was the best decision for what we needed as a team. If it were up to me, moving to Git would be the right direction. It is less costly and it is …
If you value integration over cost, Bamboo is clearly the way to go. It offers tight integration to the rest of the Atlassian suite, and when you need traceability from issue to build, Atlassian is the right way to go. However, if you find yourself needing to save on costs, you may consider taking an approach of rolling your own build system with open source alternatives, such as Jenkins, if you don't [mind] putting in a little extra elbow grease.
As a team we need to push code into the repo on daily basis, Bitbucket has proven that is a reliable and secure server to save and get the code available in no time. The administration part is really easy and there's an extra tool for every developer profile either if you want to use the console or a GUI like Sourcetree.
Azure DevOps is good to use if you are all-in on the Microsoft Azure stack. It's fully integrated across Azure so it is a point-and-click for most of what you will need to achieve. If you are new to Azure make sure you get some outside experience to help you otherwise it is very easy to overcomplicate things and go down the wrong track, or for you to manually create things that come out of the box.
Levels of granularity. Organization has many projects that have many build plans that have many jobs that have many tasks, etc. And branch builds allow source control branches to be built separately.
Versatility. I can use bamboo to manage my Java, node, or .NET build plans. I can use it to spin up Windows or Linux build agents, or install it on a Mac to build there as well.
Bamboo integrates with other Atlassian products like Bitbucket, Stash, JIRA, etc. If a company commits to the entire Atlassian stack then work can be tracked through the whole development lifecycle which is really useful.
Very easy to integrate with other DevOps tools like Jenkins and with project/workflow management tools like JIRA.
Very efficient in managing security and compliance standards for code, especially during pull requests, merge requests, branching, etc.
Very robust in performance, especially the cloud and datacenter versions hardly hit any performance issues and supports more than 2000+ developers in my company.
All products have room for improvement. The system improves over time with better and better integrations and I look forward to even more features without paying extra! The system has increased transparency across my organization and with this transparency comes increased throughput on projects. I don't think I can go back to any other system and we are definitely married to this product.
Because we are a Microsoft Gold Partner we utilize most of their software and we have so much invested in Team Foundation Server now it would take a catastrophic amount of time and resources to switch to a different product.
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.
The architecture of Bitbucket makes it more easily scalable than other source code management repositories. Also, administration and maintaining the instance is very easy. It integrates with JIRA and other CI/CD applications which makes it more useful to reduce the efforts. It supports multiple plugins and those bring a lot of extra functionality. It increases the overall efficiency and usefulness of Bitbucket.
For standard users the interface is friendly. but if you are a manager some tools are a little confusing to use, like the query system that you always need to create from scratch. Templates should be more helpful for queries and for standard procedures that you need to duplicate PBIs over time. The search history of Work Items is a little painful to use.
Bamboo is a fairly small product but having said that it was fairly easy to get assistance. Especially for the small to easy things. Anything large or fairly complex was an issue finding detailed answers for. This caused a lot of trial and error on our part to try to find a solution.
The customer support provided by Atlassian (Bitbucket's parent company that also makes Jira, Confluence, etc.) is very helpful. They seem to be very concerned about any issues reported with their products and even just questions about functionality. They are constantly improving the products with new features in nearly every release. Plus they have a plethora of online documentation to reference.
I have not had to use the support for Azure DevOps Server. There have never been any issues where I was not able to figure it out or quickly resolve. Our Scrum Master has used support before though, and the service has always been prompt and clear with a customer-focus
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 compability, simply to maintain / manage, and straightforwardly integration with different notification platforms
For the features we were looking at, Bitbucket, GitHub and GitLab were all at par and were in a similar price range. We found that GitHub was the most full featured should we need to scale very quickly. GitLab was at par with GitHub for our future needs, but GitHub was a more familiar tool compared to GitLab. Bitbucket won out because of its close integration with Jira and being in the Atlassian family. It was also cheaper than GitHub. As we started with Jira, Bitbucket addition became a natural next step for us. We really liked Bitbucket and stayed with it but we do know we have great options in the form of GitHub and GitLab should we need to scale fast.
In my opinion, DevOps covers the development process end to end way better than Jira or GitHub. Both competitors are nice in their specific fields but DevOps provides a more comprehensive package in my opinion. It is still crazy to see that the whole suite can be used for free. The productivity increase we realized with DevOps is worth real money!
It helped us achieve the Continuous Deployment and Continuous Integration goals for our applications, a huge milestone that saved a lot of time for developers in making the builds and deployments and saved time for QA in running the automated tests.
Helped with DevOps: we moved the formal approval from the email to the system and allowed the approver to actually push the button for the production deployments.
Biggest positive impact of using Bamboo is that it improved our response time to customers and increased the frequency of our deliveries to them.
It has streamlined the pipeline and project management for our agile effort.
It has helped our agile team get organized since that is a new methodology being leveraged within the Enterprise.
The calendar has improved visibility into different OOOs across the project team since we all come from different departments across the larger organization.