AWS CodeBuild vs. TeamCity

It is really good for building projects in the cloud. If you try to do build the project first locally and then push that stack to the cloud it could take a lot of time. In this way, it also consumes a lot of resources in the computer and in the network.

Incentivized

TeamCity is very quick and straightforward to get up and running. A new server and a handful of agents could be brought online in easily under an hour. The professional tier is completely free, full-featured, and offers a huge amount of growth potential. TeamCity does exceptionally well in a small-scale business or enterprise setting.

Incentivized

• Customization
• Do code builds within a schedule or when the source code changes
• Only pay for the build time used

Incentivized

• TeamCity provides a great integration with git, especially Bitbucket.
• When a new code release (build) fails TeamCity has a great tool for investigation and troubleshooting.
• TeamCity provides a user-friendly interface. While some technical knowledge is required to use TeamCity, the design helps simply things.

Incentivized

• Sometimes it runs an outage and developers don't know why. We have to contact DevOps most of the time.
• Sometimes it is slow

Incentivized

• The customization is still fairly complex and is best managed by a dev support team. There is great flexibility, but with flexibility comes responsibility. It isn't always obvious to a developer how to make simple customizations.
• Sometimes the process for dealing with errors in the process isn't obvious. Some paths to rerunning steps redo dependencies unnecessarily while other paths that don't are less obvious.

Incentivized

TeamCity runs really well, even when sharing a small instance with other applications. The user interface adequately conveys important information without being overly bloated, and it is snappy. There isn't any significant overhead to build agents or unit test runners that we have measured.

Incentivized

AWS CodeBuild provides the option to fully implement the build in the cloud without wasting your local resources (computer and network) providing independence to developers to invest those resources in other processes. It also provides a robust platform with a lot of customizations or just a script for each language.

Incentivized

TeamCity is a great on-premise Continuous Integration tool. Visual Studio Team Services (VSTS) is a hosted SAAS application in Microsoft's Cloud. VSTS is a Source Code Repository, Build and Release System, and Agile Project Management Platform - whereas TeamCity is a Build and Release System only. TeamCity's interface is easier to use than VSTS, and neither have a great deployment pipeline solution. But VSTS's natural integration with Microsoft products, Microsoft's Cloud, Integration with Azure Active Directory, and free, private, Source Code repository - offer additional features and capabilities not available with Team City alone.

Incentivized

• It has a positive ROI

Incentivized

• TeamCity has greatly improved team efficiency by streamlining our production and pre-production pipelines. We moved to TeamCity after seeing other teams have more success with it than we had with other tools.
• TeamCity has helped the reliability of our product by easily allowing us to integrate unit testing, as well as full integration testing. This was not possible with other tools given our corporate firewall.
• TeamCity's ability to include Docker containers in the pipeline steps has been crucial in improving our efficiency and reliability.

Incentivized