News for hackers. Stuff that matters.
Re:The worst thing about Jenkins is that it works by SOLAR_FIELDS on Sunday December 03, 2023 @11:40PM (#38513804)
Jenkins, like many CI tools, is fine when you are maintaining 1-5 builds. Sure, your artisanal bash script pasted into the shell run of the Jenkins gui is stable and it just works.

When you go beyond that is when everything falls apart. And by fall apart I mean your org starts to grow to a technical ci debt by a thousand cuts until its taking some teams hours to build and ship their code or debug a spaghetti string of code strung together across undocumented boundaries.

Have you used other solutions at all? I used Jenkins for years and a lot of things that that came after that, from industry standards like GitHub Actions and Gitlab CI to more bleeding edge stuff like Earthly and Dagger. Jenkins is the worst of all of them, even if it may do a couple of things “better” than the others

Re:The worst thing about Jenkins is that it works by ttt3ts on Sunday December 03, 2023 @11:48PM (#38513846)
My 10 year old Jenkins build still runs. My CircleCI build.... less so...
Re:The worst thing about Jenkins is that it works by esafak on Sunday December 03, 2023 @11:58PM (#38513895)
I bet companies have years old zombie pipelines running without anyone's knowledge because Jenkins lacks discoverability.
Re:The worst thing about Jenkins is that it works by Too on Monday December 04, 2023 @02:31AM (#38514593)
+1. Jenkins is only simple as long as your problem domain is simple.

Once you need a tiny bit more, you are screwed. By that time you are already too heavily invested because initial barrier to entry was so low.