Compare Bamboo and TeamCity 
- Users report that Bamboo excels in its integration capabilities, scoring a remarkable 9.7, which allows seamless connections with various tools and services, making it a favorite among teams that rely on multiple software solutions.
- Reviewers mention that TeamCity shines in deployment-ready staging, achieving a score of 9.1, which facilitates smoother transitions from development to production, a critical feature for teams focused on continuous delivery.
- G2 users highlight Bamboo's extensibility with a score of 9.0, allowing teams to customize their workflows and processes effectively, which is particularly beneficial for organizations with unique requirements.
- Users on G2 note that TeamCity's automation features are robust, scoring 8.7, which helps streamline repetitive tasks and enhances overall productivity, a key advantage for teams looking to optimize their CI/CD pipelines.
- Reviewers say that Bamboo's reporting capabilities, with a score of 7.9, could use improvement, as some users find it less intuitive compared to TeamCity's reporting features, which scored 8.0 and are praised for their clarity and ease of use.
- Users report that both products have similar ease of use ratings at 8.2, but TeamCity's slightly higher quality of support score of 8.5 suggests that users may find more responsive assistance when encountering issues.
- Up to 10 jobs, Unlimited local agents, No remote agents
- Unlimited web users
- Unlimited concurrency
- Fleet of Linux, Windows and macOS build agents maintained by JetBrains
It's easy to use for easy things. Fortunately most of what I do is easy. It's harder to do harder things but in most cases it is possible to work within the constraints of the system. The documentation is pretty good once you figure out where it is. ...
Inability to define jobs as code. Everything is declarative, which is great when you're learning but not if you have multiple jobs that share the same properties with small variances.
TeamCity makes it extraordinarily easy to configure individual builds. By far the best feature is its ability to use parameters for builds, which makes it very easy to create generic build configurations that can be used over and over again.
Documentation sucks, and is very difficult to set up and upgrade
It's easy to use for easy things. Fortunately most of what I do is easy. It's harder to do harder things but in most cases it is possible to work within the constraints of the system. The documentation is pretty good once you figure out where it is. ...
TeamCity makes it extraordinarily easy to configure individual builds. By far the best feature is its ability to use parameters for builds, which makes it very easy to create generic build configurations that can be used over and over again.
Inability to define jobs as code. Everything is declarative, which is great when you're learning but not if you have multiple jobs that share the same properties with small variances.
Documentation sucks, and is very difficult to set up and upgrade
