* Tech stack - Bamboo is suitable for any language, and other popular technologies like AWS CodeDeply, Docker, and Amazon S3. You can choose from a big variety of available tasks for both build and deployment projects, or search for free add-ons! * Deployment projects - Bamboo gives deployments the first-class treatment with deployment projects and environments. A deployment project holds the software project you are deploying: releases that have been built and tested, and the environments to which releases are deployed. * Dedicated agents - With Bamboo's dedicate agents feature, you can run hot fixes and critical builds right away! When you dedicate an agent, no other activity will be able to use it, unless it is dedicated to that activity as well. This means no wait in the queue for free build agents when there are critical bugs to fix! * Visibility - Before deploying a new release, see the full roll-up of code changes and JIRA software issues that have come in since the previous deploy. Ops teams can anticipate what they'll be responsible for deploying and supporting in production, and release managers get a clear view of what is going live. * Bamboo + Bitbucket + JIRA Software * Integrate the three for full traceability. * Connect Bamboo to Bitbucket and JIRA Software and follow the development process from planning to final delivery. Get full visibility on builds, pull requests, deployments, and more. * Parallel tests - Bamboo supports up to 100 remote build agents, giving you the power to run batches of tests in parallel, keep the queue flowing, and get feedback to developers quickly. * Docker agents - Other than Docker tasks for build plans and deployments that let you create your own image and push it to a registry, there are ready to use Bamboo agent images on Docker Hub to grab and run. * Permissions - With per-environment permissions, developers and QA can deploy to their own environments on demand while production stays locked down. Build engineers and ops teams spend less time servicing deploy requests, and one more bottleneck bites the dust. * Quarantine - Don't let red builds become the norm. Keep flakey or broken tests out of sight (but not out of mind), and keep the build green with one-click quarantine.

* Technology Awareness - One reason TeamCity is dubbed an "Intelligent CI server" is its approach to integration. When we say we support a tool, we mean it in every way possible. For example, support for Visual Studio projects provides automatic detection of tool versions, testing frameworks support, code coverage, static code analysis, and more. And the best thing is, you get all this support without installing any plugins and with no modifications to build scripts! * Configuration - Skillful software developers try to avoid code duplication; similarly, build engineers avoid duplication of settings. TeamCity understands this and provides several ways to reuse settings. * VCS Interoperability - TeamCity version controls systems integration is comprehensive. It’s hard to imagine a project whose source code couldn’t be retrieved by TeamCity. * Key Integrations - It’s impossible to imagine a great CI and CD server without an integration with some key tools like your version control, you issue tracker, your build tool, and your package repository. TeamCity takes it very seriously to provide full support for these key integrations. * Build History - We believe that keeping a history of builds, changes and failures is crucial to the success of any software development process. TeamCity enables you to run history builds, see statistics and test history reports, as well as pin, tag, and add builds to favorites. All of the changes are accumulated in the change log. * Extensibility and Customization - TeamCity provides you with multiple ways of interaction, customization, and extending your server. Use service messages in your build scripts, interact via REST API, or create plugins for TeamCity using Open API. * Cloud Integrations - TeamCity takes advantage of cloud computing by dynamically scaling out its build agents farm on Amazon EC2, Microsoft Azure, and VMware vSphere. * Build Infrastructure - Imagine a conveyor belt of changes from developers and a bunch of testers taking the changes, verifying them and complementing these changes with verification results. TeamCity is such a conveyor, except that testers are replaced with Build Agents. * System Maintenance - TeamCity helps you maintain your CI server healthy and stable even when no builds are running so that you don’t waste your time when it’s needed the most. It provides you with useful reports like Disk Usage, Build Time, and Server Health reports