4 ms·
I recently had to switch from Jenkins to TeamCity, and while my very first thought fiddling with TC was that it's unnecessarily complex for my needs, I found my
by pkos98 6y ago
I recently had to switch from Jenkins to TeamCity, and while my very first thought fiddling with TC was that it's unnecessarily complex for my needs, I found myself creating the build jobs much faster and more straightforward than with Jenkins.
Jenkins plugins are very often deprecated/unmaintained with tons of security vulnerabilites and a bad UI/UX which results in inconsistent UX when using several plugins.
Also, with Jenkins you're forced to use groovy for pipeline code :/...
- EdwardDiego 6y agoI honestly find the Groovy aspect the worst part of Jenkins.
- bovermyer 6y agoThis actually wouldn't be too bad if it was full Groovy instead of a severely hampered subset of Groovy.
- zmmmmm 6y agoGroovy seems to get an awfully bad rap from Jenkins. Seems about 95% of people encounter it there in a broken state and assume the language itself is that bad. I really wonder why they have deployed it in such a way as presumably a build server can do pretty much anything so why it would be necessary to constrain groovy scripts behavior I can't understand.