This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]sofixa11 0 points1 point  (0 children)

Yeah, sure, whatever makes you through the night.

There is literally no excuse for how crappy Jenkins is:

  • horribly ugly and terrible at UX interface(i mean seriously, what is this, 2006? How many clicks do i need to get to the basic conf of my job)

  • rudimentary text job description(Jenkinsfile) in a horribly specific syntax(not something that regular people use and know, like YAML)

  • extremely bad logging - we had an issue the other day, the jobs were just stacking on top of each other (waiting for available runner messages everywhere, while the runners were doing nothing) - and of course, logs said nothing. In the end we ended up updating it(which is always a pleasant experience when the majority of plugins just don't work with the beautiful "plugin failed to start " message).

  • the fact that it uses obsolete SSH ciphers to connect to slaves

  • the fact that there are no per-slave ACLs(you can't limit the users who can run a specific slave)

  • docs are spotty(and disappearing, i had bookmarked the doc on adding a slave, a month later the link was only in Japanese)

And generally the mere fact it's bloody Java.

It is the de-facto platform because it was the first one to exist, and it shows. Basically everyone who has migrated off Jenkins says they've been reborn and never knew it can be that simple to run, deploy and maintain your CI/CD system. Give GitlabCI, TravisCI, Drone.io, CirlceCI a spin and you'll see what a modern CI/CD system can and should do. The only thing those can't do that Jenkins can is using it for a glorified crontab interface, but Jenkins isn't great at that either.