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.