Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The worst thing about Jenkins is that it works (2019)

twitchard.github.io

Post reply on HN
Print view View original

191–200 of 275 posts

Re: The worst thing about Jenkins is that it works (2019)

#191

Post by bruckie »

hospadar wrote: post #49
dig1 wrote: post #20

Jenkins is not perfect by any means, but I can say it is much better than existing solutions (taking pros and cons after trying and using many of them). Sure, it doesn't have fancy UI or flying buttons, nor is it rust/PWA/react/whatever-rage-is-these-days, but it does its job - it works, is free, and has been very well-maintained for ages. Download a single file and run it. Want to extend it? There is a plugin for ev…

I hear you, I want my CI to be boring and just work, and using something old and and a little cooky is fine but... omg switching away from jenkins (in our case to gitlab CI) was a revalation. SO much easier to use. There were a ton of things we were avoiding doing in CI (or at all) that we started doing (easily) once we switched. > it must work properly, and I don't expect it to be pretty Too often it really _didn't_…

What did you switch to?

Re: The worst thing about Jenkins is that it works (2019)

#192

Post by gnulinux »

ebiester wrote: post #76
theptip wrote: post #72

> The head of SRE championed Gitlab CI. I resisted this idea because I, the relatively inexperienced manager of a nascent team, was daunted by the prospect of trying to supplant Jenkins, Github, and JIRA all at once. I think this is a really big scoping mistake. There is a clean glide path, and I have no idea why you'd think you need to replace Jira. You can use Gitlab Runners in Github ( https://docs.gitlab.com/ee/u…

Gitlab is 29/month. It’s hard to stomach 29 + the money for GitHub and Jira, depending on the features you need. (Minimum 11/mo)

If you can't afford $30 a month, do you really have a business?

Re: The worst thing about Jenkins is that it works (2019)

#193

Post by opello »

hedora wrote: post #122
twunde wrote: post #100

Earlier quoted context omitted.

I'm general, it's an anti pattern since it's makes everything much more complicated. The typical reason to have it is so that there are dev tools in the dev container (autoformatter, linter etc) or support for hot reloading and then the prod container is locked down. The other pattern you'll sometimes see is that the prod container will include an agent or a certificate bundle, although it's more common to use sideca…

Multi-stage docker files mostly solve this problem: https://docs.docker.com/build/building/multi-stage/

I agree that multi-stage builds help address this, but that also means there are different images.

Re: The worst thing about Jenkins is that it works (2019)

#194

Post by ljlolel »

bruckie wrote: post #191
hospadar wrote: post #49

Earlier quoted context omitted.

I hear you, I want my CI to be boring and just work, and using something old and and a little cooky is fine but... omg switching away from jenkins (in our case to gitlab CI) was a revalation. SO much easier to use. There were a ton of things we were avoiding doing in CI (or at all) that we started doing (easily) once we switched. > it must work properly, and I don't expect it to be pretty Too often it really _didn't_…

What did you switch to?

He wrote GitLab CI

Re: The worst thing about Jenkins is that it works (2019)

#196

Post by Sophistifunk »

i386 wrote: post #163
maratc wrote: post #130

Earlier quoted context omitted.

Thanks for that, we use it all day every day! It's too bad it's been declared "end of life", without any replacement in sight, and nobody these days is fixing some bugs that are really bothering us sometimes...

I really wished we finished it and made it the default UI. Jenkins is very extensible, so there are a LOT of extension points. We certainly didn't have the right approach to the API and devex for creating react plugin extension points either.

We almost made it... Still bums me out. Good to see you're still lurking broseph ;-)

Re: The worst thing about Jenkins is that it works (2019)

#197

Post by SOLAR_FIELDS »

dig1 wrote: post #20

Jenkins is not perfect by any means, but I can say it is much better than existing solutions (taking pros and cons after trying and using many of them). Sure, it doesn't have fancy UI or flying buttons, nor is it rust/PWA/react/whatever-rage-is-these-days, but it does its job - it works, is free, and has been very well-maintained for ages. Download a single file and run it. Want to extend it? There is a plugin for ev…

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 (2019)

#198

Post by Scramblejams »

dangus wrote: post #96
dig1 wrote: post #20

Jenkins is not perfect by any means, but I can say it is much better than existing solutions (taking pros and cons after trying and using many of them). Sure, it doesn't have fancy UI or flying buttons, nor is it rust/PWA/react/whatever-rage-is-these-days, but it does its job - it works, is free, and has been very well-maintained for ages. Download a single file and run it. Want to extend it? There is a plugin for ev…

I don’t think the issue with Jenkins is the lack of bells and whistles. The UI it has is unintuitive - I always feel like I can’t find what I’m looking for anytime I am in there. It has two different UIs (last I checked) which is kind of insane, blue ocean still sucked the last time I used it and the product can’t 100% move away from the old UI (again, last I checked…) On top of all that it’s not really fun to admini…

And Blue Ocean’s effectively deprecated!

Re: The worst thing about Jenkins is that it works (2019)

#199

Post by Sophistifunk »

As somebody who has spent his share of time interacting with Jenkins as a user, and messing around inside it as a developer, I am definitely biased. For or against, I'm not sure tho ;-)

But the problem with Jenkins is the problem with all CI. Our (software in general, not Jenkins specifically) build process are all godforsaken nightmares that would put HP Lovecraft and Rube Goldberg into rubber rooms. You can't add a bunch of extra automation to any of these systems and get something better, let alone a system that needs to be able to automate so many different and unique snowflake horrors.

Re: The worst thing about Jenkins is that it works (2019)

#200

Post by x3n0ph3n3 »

dig1 wrote: post #20

Jenkins is not perfect by any means, but I can say it is much better than existing solutions (taking pros and cons after trying and using many of them). Sure, it doesn't have fancy UI or flying buttons, nor is it rust/PWA/react/whatever-rage-is-these-days, but it does its job - it works, is free, and has been very well-maintained for ages. Download a single file and run it. Want to extend it? There is a plugin for ev…

I like to borrow Churchill's quote about democracy and reframe it around Jenkins.

Jenkins is the worst CI/CD tool, except for all the others.

Post reply on HN