TeamCity is the ideal tool for agile teams using continuous integration
November 30, 2018
TeamCity is the ideal tool for agile teams using continuous integration
Score 8 out of 10
Vetted Review
Verified User
Overall Satisfaction with TeamCity
TeamCity was used by the technology department of the organization, especially by the web development team.
We used TeamCity to test and release code from our development environment to our production environment. Our web developers worked under an agile project management system and used continuous integration. In this system, TeamCity allowed us to integrate our git repository with our ticketing system, as well as help us quality assure and properly release clean code to production.
We used TeamCity to test and release code from our development environment to our production environment. Our web developers worked under an agile project management system and used continuous integration. In this system, TeamCity allowed us to integrate our git repository with our ticketing system, as well as help us quality assure and properly release clean code to production.
- 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.
- Upgrading TeamCity is a long and manual process.
- Java skills are needed to fully utilize TeamCity, although they are not necessary for basic or medium-level use.
- TeamCity provides positive ROI by catching errors before code releases and providing helpful details about the errors.
- TeamCity saves our developers time by automating the build process as much as possible.
While TeamCity is more limited product than VSTS (VSTS includes a git repository), it is easier to use and better priced.