TeamCity is a continuous integration server from Czeck company JetBrains.
N/A
Pricing
TeamCity
Editions & Modules
No answers on this topic
Offerings
Pricing Offerings
TeamCity
Free Trial
No
Free/Freemium Version
No
Premium Consulting/Integration Services
No
Entry-level Setup Fee
No setup fee
Additional Details
—
More Pricing Information
Community Pulse
TeamCity
Considered Both Products
TeamCity
Verified User
Manager
Chose TeamCity
Jenkins relies on being open source as the primary driver for its success. This low cost is a huge factor for many companies, both small and large. The professional, free tier of TeamCity offers a huge amount of growth before ever needing to pay anything. I personally also find …
Since we were already making use of other JetBrains offerings, TeamCity had a leg up on the competition due to the ease of integration with these tools. With that said, TeamCity's feature set stacks up well with the competition. Jenkins definitely has some nice features, but …
This application is easy to install and deploy at site than most of the similar solutions in market. Easy user interface is one of the reason it can be installed. However each software have its good points and bad points. Study your organizations case and then only choose …
I would also like to compare TeamCity against Snap-Ci as well as Concourse. We chose TeamCity over all of these tools because of its ability to be set up easily against a restricting corporate firewall. We needed to integrate unit tests, integration tests, pushes to production, …
TeamCity competes against the TFS build, Visual Studio Team services and Jenkins the open source workhorse. The reason for selecting TeamCity was because it was found to be a great fit for all the diverse projects on a spectrum of technologies we have which the TFS Build …
Cloud Services Practice Manager and Principal Architect
Chose TeamCity
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 …
I like the quality of Jetbrains products. TeamCity is well supported and regularly updated by Jetbrains. They have an active support forum and most questions are answered quickly.
TeamCity is very extendable and has been able to handle everything we've been required to do.
We've only ever really used TeamCity as a CI platform. Running tests on these CI clusters is worlds more efficient and just plain easier than having to run individual tests on your local machine. You just hit one button here, versus either writing some run script or even worse …
TeamCity is the best combination of price and full features. It has a good web UI and doesn't need a lot of manual configuration files, but it still is incredibly extensible and can do just about any build or release task you set it at. If it can't do it, the odds are it has a …
Jenkins and Team Foundation Server (TFS) are both strong products. Compared to Jenkins, TeamCity is much more mature and polished. Though Jenkins is open-source/free, the cost of TeamCity is a drop in the bucket compared to the total cost of even one project we're using it …
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.
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.
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.
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.
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.