Jenkins vs Teamcity

In web development Tags #continuous-integration #jenkins #octopus-deploy #teamcity #continuous-deploy Published 6/27/2016

Quick and simple comparison between Jenkins and Teamcity based on personal use on both for a month.
Jenkins Teamcity
Price Free
Configuration Data Internally managed XML file SQLServer
Install Easy Easy, but need to set up with SQLServer.
Build configuration Normal Normal, especially well prepared for .Net project
Deployment Can be done by Powershell script Can be done by Powershell script
Octopus integration Yes Yes
Etc large pool of plug-ins and community support Reliable as a paid product.
For both, installation of tool is easy, but setting up a build configuration can be tricky. If cost doesn't matter, I would go with TeamCity with Octopus deploy, but given limited financial support, my choice for now is Jenkins and Powershell for CI and CD for now.

Leave a comment

Please note that we won't show your email to others, or use it for sending unwanted emails. We will only use it to render your Gravatar image and to validate you as a real person.