Jenkins is an open source automation server. Jenkins provides hundreds of plugins to support building, deploying and automating any project. As an extensible automation server, Jenkins can be used as a simple CI server or turned into a continuous delivery hub for any project.
N/A
TeamCity
Score 8.2 out of 10
N/A
TeamCity is a continuous integration server from Czeck company JetBrains.
I have experience with TeamCity. It looks pretty good after Jenkins, the user interface is friendly and modern. The functionality is similar to Jenkins. It is not a big problem to migrate configuration from Jenkins to TeamCity or to return back. You need licenses to use it in …
Jenkins is ideal for developing software with high-security demands. It is hosted and set up locally and has no outside connections. But these pros could become cons when you work on open source projects and need to waste time for initial setup and maintenance over a project's …
I would use TeamCity if Jenkins was not already in place. TeamCity seems a lot more stable when it comes to upgrading the software and job templates the way TeamCity handles them is an absolute killer feature. Jenkins is a bit of a wild animal, quite unpredictable but with the …
TeamCity is another viable option for Continuous Integration/Development. We picked Jenkins in this case because there was a lot of support for Amazon CloudFormation and other AWS integrations which fit the task at hand. For just straight compiling Microsoft based builds, TeamCi…
When looking for alternatives for Jenkins we found CircleCI and TeamCity are good too. Jenkins was considered for reasons like it has a wide variety of plugins which integrate well with any kind of system. And its ease of use.
One of the other greater advantage is it is open …
Both Jenkins and TeamCity do a good job of automating CI/CD. Jenkins runs much leaner than TeamCity - it only needs about a Gig of free memory, whereas TeamCity needs a fat 4 Gig free. Many tasks in Jenkins yml config can be very cumbersome, especially running local and …
Jenkins is the only tool I would consider using for CTCI deployment. Its plugins make it easy to customize to any environment you can conjure up and will always be custom fit to your needs as a DevOps engineer. Other tools have better support but lack the customizability and …
It is free, of course that's the best advantage. Great number of plugins. Largest active developer community among peer competitors. Very few competitors have got the pipelines features right as good as Jenkins.
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 …
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 …
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 …
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, …
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.
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 …