News for hackers. Stuff that matters.
Re:How a Jenkins Job Broke our Jenkins UI by clutchdude on Thursday June 03, 2021 @04:19PM (#27386761)
As someone who runs a large build cluster at a major corp, Jenkins is clunky and outdated. It's a pain to deploy and keep maintained. I'd rather stub my toe than figure out why some event isn't being properly processed in the bowels of Jenkins.

However, when coupled with Kubernetes, Jenkins is more powerful than almost any other CI tool.

You can orchestrate any iteration of build types or actions while easily providing the underlying resources transparently to your users.

Notice that almost every other CI tool mentioned here is either 3rd party hosted or severely limited in some fashion when compared to Jenkins.

Re:How a Jenkins Job Broke our Jenkins UI by Aeolun on Thursday June 03, 2021 @06:08PM (#27388049)
If you are already running in kubernetes, how is any other tool severely hampered if it also runs in kubernetes?
Re:How a Jenkins Job Broke our Jenkins UI by clutchdude on Thursday June 03, 2021 @06:50PM (#27388465)
It's partially because I'm not as familiar with other tools but they don't expose the ability to interact with an entire pod within the build.

Gitlab Action Services for instance is closer to Docker Compose.