Likelihood to Recommend Spinnaker suits well for applications which are stateless and can adapt to an immutable architecture of deployment. But for applications which are stateful and cannot afford to spin up new servers for every deployment doesn't go well with Spinnaker. It can handle only deployments which are VM based and cannot support deployments to serverless architecture like AWS Lambda etc.
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 Fast deployments. Can be integrated with a good variety of other products. Also provides some insights from your environment. Read full review 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 It does NOT support CFN based deployments Windows based systems finds it difficult to onboard to Spinnaker. Pipeline level access authorisation is not there. Support for EBS volume encryption is probably missing. Attach/detach EBS volumes during deployments is difficult. No support to deploy the artifacts without re-creating the servers. Only pure immutable deployment are allowed. Open-source - so good and bad! Spinnaker on its own has 10 underlying micro services. Managing Spinnaker needs a focussed platform approach. User authentication is easy but authorisation management is not straight forward. Debajit Kataki Sr. Devops Mgr. ( Tools, automations , Release Engineering/ CICD , AWS )
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 • Pipeline Expressiveness • Self-Service/Override • Visibility of Client Teams • Operability of Client Teams - • High-Quality Integrations (AWS, IHP, Google) • Extensibility – (Ability to add code) • The maturity of Deployment Process • Speed/Ease of Onboarding
Read full review 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 By using Spinnaker we are able to deploy new versions of our product quickly. A deployment takes in average 2 minutes. Our investment on Spinnaker was just time learning it. 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