Bamboo vs Jenkins vs TeamCity comparison

Cancel
You must select at least 2 products to compare!
Atlassian Logo
3,414 views|3,401 comparisons
75% willing to recommend
Jenkins Logo
6,896 views|5,921 comparisons
88% willing to recommend
JetBrains Logo
3,373 views|2,977 comparisons
92% willing to recommend
Comparison Buyer's Guide
Executive Summary

We performed a comparison between Bamboo, Jenkins, and TeamCity based on real PeerSpot user reviews.

Find out what your peers are saying about GitLab, Jenkins, Google and others in Build Automation.
To learn more, read our detailed Build Automation Report (Updated: April 2024).
768,415 professionals have used our research since 2012.
Featured Review
Quotes From Members
We asked business professionals to review the solutions they use.
Here are some excerpts of what they said:
Pros
"Bamboo's integration with the rest of Atlassian's tech tools, like Jira, helps manage the end-to-end development and release process.""The most valuable feature of Bamboo is that it is a good tool for CI/CD integration.""One of the big things that made us choose Bamboo, is it seamlessly integrates its APIs into NetSuite, which is our main ELP system.""The most valuable features are compiling and deployment.""In my experience Bamboo is scalable.""The most useful feature of Bamboo is its integration with other solutions such as Jira and BitBucket, also offered by Atlassian. It is easier to use tools all provided by one vendor.""It's one of the best solutions in this line of work. We have many Atlassian products. We use Bamboo, JIRA, Service Desk, and some other Atlassian plugins. We like that it's easy to integrate into each other. It's a suite of services.""In Bamboo, build and deployment have been segregated. The build plan and deployment plan are different. When comparing Bamboo to other solutions, the native feature you will not find in another tool, such as Jenkins. They have segregated the build and deployment plan. This means, building the application and deploying it are two separate parts in Bamboo, they have segregated it apart from the UI. This makes the tool a bit better compared to other tools."

More Bamboo Pros →

"The most valuable aspect of Jenkins is pipeline customization. Jenkins provides a declarative pipeline as well as a scripted pipeline. The scripted pipeline uses a programming language. You can customize it to your needs, so we use Jenkins because other solutions like Travis and Spinnaker don't allow much customization.""The most valuable features of Jenkins are its ease of use and good plugins available. You are able to connect to a lot of solutions.""I am not aware of the available options in the market right now compared to Jenkins, but I am pretty much happy with the service that Jenkins is providing our company.""I like that you can find a wide range of plugins for Jenkins.""A lot of support material exists via a single web search of exactly what you're looking for.""Has a good interface, is reliable and saves time.""Jenkins is very easy to use.""Different types of jobs, such as Pipeline, Build, Freestyle, Maven, etc."

More Jenkins Pros →

"The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine.""TeamCity's GUI is nice.""The most valuable aspect of the solution is its easy configuration. It also has multiple plugins that can be used especially for building .net applications.""The integration is a valuable feature.""TeamCity is very useful due to the fact that it has a strong plug-in system.""VCS Trigger: Provides excellent source control support.""It provides repeatable CI/CD throughout our company with lots of feedback on failures and successes to the intended audiences via email and Slack.""One of the most beneficial features for us is the flexibility it offers in creating deployment steps tailored to different technologies."

More TeamCity Pros →

Cons
"The solution needs to support more customization in the training. What's offered is pretty generic. They need better training and should offer more guidance.""Scalability depends on the use case. If it is really a big customer with a lot of tests, it might not be a scalable option for them.""One area that could be enhanced is the governance process, particularly with regard to building approvals and transitions between stages. In comparison to other solutions, such as Jira, which features a workflow that supports approval processes, this capability is not natively available in Bamboo. To implement this functionality, integration with other solutions, such as GSM may be necessary. Although some add-ons, such as Adaptavist ScriptRunner, are available in the market to circumvent this limitation, they may not offer the exact functionality needed. Therefore, there is certainly room for improvement in this area.""It can be challenging for someone new to the system or ecosystem to grasp, making it difficult to train new people and help them understand.""The performance around the deployment feature could be improved.""It should be much easier to use. It shouldn't require a lot of reading to be able to use it. It should have just two or three screens rather than hundreds of screens requiring a lot of clicking. It also requires a lot of integration. It has a steep learning curve. It takes a lot of time to understand and put in the data. There is also no proper training.""It would be great if Bamboo could introduce a more containerized deployment model.""The marketing strategy of Bamboo is an area of concern where improvements are needed."

More Bamboo Cons →

"Jenkins relies on the old version of interface for configuration management. This needs improvement.""We cannot change the ownership of any directory or file or any kind of directory.""For this solution to be a 10, it has to be a lot more stable. Maybe the public version of Jenkins is stable, but in our case it's not stable.""Better and easy-to-use integration with Docker would be an improvement.""Jenkins takes a long time to create archive files.""The UI must be more user-friendly.""Developer documentation for plugins, plugin development, integrations: Sometimes it’s tricky to do pretty obvious things.""Jenkins could improve the integration with other platforms."

More Jenkins Cons →

"If there was more documentation that was easier to locate, it would be helpful for users.""I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does.""Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted.""We've called TeamCity tech support. Unfortunately, all their tech support is based in Europe, so we end up with such a big time crunch that I now need to have one person in the US.""The upgrade process could be smoother. Upgrading major versions can often cause some pain.""Their online documentation is fairly extensive, but sometimes you can end up navigating in circles to find answers. I would like them (or partner with someone)​ to provide training classes to help newcomers get things up and running more quickly.""REST API support lacks many features in customization of builds, jobs, and settings.""Integrating with certain technologies posed challenges related to time and required support from the respective technology teams to ensure smooth integration with TeamCity."

More TeamCity Cons →

Pricing and Cost Advice
  • "There is a subscription required to use Bamboo."
  • "If Bamboo could provide more flexibility on pricing, that would help. On the agent side, if you want to increase the number of agents it should be less expensive. If they can provide some better pricing model, it will help, whether we are going to use it or are already using it."
  • "The server products for small teams used to offer excellent pricing. However, Atlassian has since changed the offering and the pricing is more expensive. I do still think the solution offers good value for money."
  • "The price of Bamboo is reasonable."
  • "I rate the product’s pricing a five out of ten."
  • More Bamboo Pricing and Cost Advice →

  • "It is a free product."
  • "Jenkins is open source."
  • "​It is free.​"
  • "Some of the add-ons are too expensive."
  • "It's free software with a big community behind it, which is very good."
  • "I used the free OSS version all the time. It was enough for all my needs."
  • "Jenkins is open source and free."
  • "There is no cost. It is open source."
  • More Jenkins Pricing and Cost Advice →

  • "Start with the free tier for a few build configs and see how it works for you, then according to your scale find the enterprise license which fits you the most."
  • "The licensing is on an annual basis."
  • More TeamCity Pricing and Cost Advice →

    report
    Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
    768,415 professionals have used our research since 2012.
    Comparison Review
    Anonymous User
    Moving to TeamCity from Jenkins At work, we’re slowly migrating from Jenkins to TeamCity in the hope of ending some of our recurring problems with continuous integration. My use of Jenkins prior to this job has been almost strictly on a personal basis, although I pretty much only use Travis nowadays. The biggest difference upon initial inspection is that TeamCity is far more focused on validating individual commits rather than certain types of tests. Jenkins’ front page presents information that is simply not useful in a non-linear development environment, where people are often working in vastly different directions. How many of the previous tests passed/failed is not really salient information in this kind of situation. Running specific tests for individual commits on TeamCity is far more trivial in terms of interface complexity than Jenkins. TeamCity just involves clicking the ”…” button in the corner on any test type (although I wish it wasn’t so easy to click “Run” by accident). I generally find TeamCity a lot more intuitive than Jenkins out of the box. There’s a point at which you feel that if you have to scour the documentation to do anything remotely complex in an application, you’re dealing with a bad interface. One disappointing thing in both is that inter-branch merges improperly trigger e-mails to unrelated committers. I suppose it is fairly difficult to determine who to notify about failure in situations like these, though. It seems like TeamCity pulls up the… Read more →
    Questions from the Community
    Top Answer:Bamboo's integration with the rest of Atlassian's tech tools, like Jira, helps manage the end-to-end development and… more »
    Top Answer:I rate the product’s pricing a five out of ten.
    Top Answer:The tools and capabilities of the system are extensive. It can be challenging for someone new to the system or ecosystem… more »
    Top Answer:When you are evaluating tools for automating your own GitOps-based CI/CD workflow, it is important to keep your… more »
    Top Answer:Jenkins has been instrumental in automating our build and deployment processes.
    Top Answer:TeamCity is a very user-friendly tool.
    Top Answer:It's open source, however, if you want your solution to be deployed on their cloud or on the cloud in general without… more »
    Top Answer:It's just a tool that I used. I needed to deliver something, so I did. I wasn't looking at it in a way to criticize it… more »
    Ranking
    5th
    out of 41 in Build Automation
    Views
    3,414
    Comparisons
    3,401
    Reviews
    7
    Average Words per Review
    542
    Rating
    7.7
    2nd
    out of 41 in Build Automation
    Views
    6,896
    Comparisons
    5,921
    Reviews
    39
    Average Words per Review
    386
    Rating
    7.8
    6th
    out of 41 in Build Automation
    Views
    3,373
    Comparisons
    2,977
    Reviews
    2
    Average Words per Review
    574
    Rating
    8.0
    Comparisons
    GitLab logo
    Compared 43% of the time.
    GitHub Actions logo
    Compared 7% of the time.
    Harness logo
    Compared 7% of the time.
    Tekton logo
    Compared 7% of the time.
    AWS CodePipeline logo
    Compared 3% of the time.
    GitLab logo
    Compared 16% of the time.
    AWS CodePipeline logo
    Compared 9% of the time.
    IBM Rational Build Forge logo
    Compared 7% of the time.
    Tekton logo
    Compared 7% of the time.
    Digital.ai Release  logo
    Compared 4% of the time.
    GitLab logo
    Compared 44% of the time.
    CircleCI logo
    Compared 17% of the time.
    Harness logo
    Compared 6% of the time.
    Tekton logo
    Compared 6% of the time.
    AWS CodePipeline logo
    Compared 2% of the time.
    Learn More
    Overview
    Bamboo is a continuous integration and delivery tool that ties automated builds, tests and releases together in a single workflow. It works great alongside JIRA and Stash providing a fully traceable deployment pipeline.

    Jenkins is an award-winning application that monitors executions of repeated jobs, such as building a software project or jobs run by cron.

    TeamCity is a Continuous Integration and Deployment server that provides out-of-the-box continuous unit testing, code quality analysis, and early reporting on build problems. A simple installation process lets you deploy TeamCity and start improving your release management practices in a matter of minutes. TeamCity supports Java, .NET and Ruby development and integrates perfectly with major IDEs, version control systems, and issue tracking systems.

    Sample Customers
    Neocleus, MuleSoft, Interspire
    Airial, Clarus Financial Technology, cubetutor, Metawidget, mysocio, namma, silverpeas, Sokkva, So Rave, tagzbox
    Toyota, Xerox, Apple, MIT, Volkswagen, HP, Twitter, Expedia
    Top Industries
    REVIEWERS
    Computer Software Company40%
    Financial Services Firm20%
    Marketing Services Firm10%
    Non Tech Company10%
    VISITORS READING REVIEWS
    Financial Services Firm18%
    Manufacturing Company14%
    Computer Software Company13%
    Government8%
    REVIEWERS
    Financial Services Firm33%
    Computer Software Company23%
    Media Company9%
    Comms Service Provider9%
    VISITORS READING REVIEWS
    Financial Services Firm20%
    Computer Software Company17%
    Manufacturing Company11%
    Government6%
    REVIEWERS
    Financial Services Firm13%
    Computer Software Company13%
    Media Company7%
    Hospitality Company7%
    VISITORS READING REVIEWS
    Financial Services Firm21%
    Computer Software Company15%
    Manufacturing Company9%
    Comms Service Provider7%
    Company Size
    REVIEWERS
    Small Business30%
    Midsize Enterprise30%
    Large Enterprise40%
    VISITORS READING REVIEWS
    Small Business15%
    Midsize Enterprise14%
    Large Enterprise71%
    REVIEWERS
    Small Business27%
    Midsize Enterprise16%
    Large Enterprise58%
    VISITORS READING REVIEWS
    Small Business17%
    Midsize Enterprise11%
    Large Enterprise72%
    REVIEWERS
    Small Business37%
    Midsize Enterprise15%
    Large Enterprise48%
    VISITORS READING REVIEWS
    Small Business25%
    Midsize Enterprise9%
    Large Enterprise66%
    Buyer's Guide
    Build Automation
    April 2024
    Find out what your peers are saying about GitLab, Jenkins, Google and others in Build Automation. Updated: April 2024.
    768,415 professionals have used our research since 2012.