Likelihood to Recommend We have a team of 500 people so it's most reliable and scalable if any new joinees. That way user's can directly create their own workspace and start working and share the work stack throughout development teams securely, to update and modify any upcoming events. The best thing about Red Hat Workspace is it's simple, with all Runtime libraries pre-installed, so no need to request a platform from Azure or any other platform provider just log in and start creating a workspace. It has version control so can easily import GIT projects can start work without worrying we don't have Java, Python or any other platform not installed just select the platform needed and start working.
Read full review 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.
Read full review Pros 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. Read full review Cons Can improve UI like Visual studio so that VS user's can switch without any difficulty. Read full review 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. Read full review Performance 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.
Read full review Alternatives Considered 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.
Eric Huggins Cloud Services Practice Manager and Principal Architect
Read full review Return on Investment No need to request for any platform again and again. Read full review 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. Read full review ScreenShots