TEAMCITY VS JENKINS INSTALL
Well, I hope our sysadmin will install the Extra Status Icon Plugin or we'll have to live without the big colored circles next to the build.Īt my work we use TeamCity for some things and Gitlab CI for others.
I guess I'm defeated, Jenkins caught up on basic core functionality only a decade late, I can't justify to pay for working and polished tools anymore. Well, jenkins finally got a progress bar too a couple years ago. Teamcity offers that out of the box for maybe 15 years now. The project is built, or is it building? It's easy to tell because there is a clear colored status icon and the estimated time to completion is displayed. How is the build matrix plugin in Jenkins lately? Broken as usual? If you want to aim for specific tool versions, there are presets variables on all hosts to filter where to build and to use in build scripts so paths are always right. The JVM and the Visual Studio are detected automatically on all the build slaves and the project is already building in the right places. Does jenkins even understand what is a requirements.txt? Hint: It's not a bash script. If it's any of C# or Java for example, the ant/maven/sln/nuget files are detected automatically, just click next and it's built. How many plugins does it take to checkout a project in jenkins? Is there even a git plugin working nowadays?
It's so trivial to be 10 times better.įirst you checkout the project from the repo and it just works, doesn't matter GIT, SVN or whatever. Users frequently want to install a new (barely maintained) plugin to solve a problem they have, complex interactions lead to difficult to understand failure modes that require time consuming investigations ("your CI tool is the problem and broke my build". In all the CI systems I've used though, there has not been one that I haven't encountered some major difficulties with.īeyond that, anything to do with build automation for a large number of users always quickly becomes a support & maintenance quagmire. Atlassian itself doesn't appear to be investing in it much anymore judging by the slow pace of development in recent years and at their most recent conference, you can hardly find it mentioned or see much presence for it anywhere. Some plugins are even maintained by an external vendor that produces the tool you're trying to integrate with and are either better supported or the first to get timely updates.īamboo on the other hand is IMO the worst of the commercial CI tools by far and where I work has gone down for us the most. Of the CI tools I've used (most of them) TeamCity was my personal favorite-but the advantage of Jenkins is that it's very widely used, has a greater breadth of capabilities due to the huge plethora of plugins, and a huge amount of support info readily available online.
0 kommentar(er)
