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

21–30 of 275 posts

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

#21

Post by rqtwteye »

DarkNova6 wrote: post #8
aloisdg wrote: post #5

Earlier quoted context omitted.

or enshittificated

Jetbrains is among the very few companies I’ll trust for the time being

Same here. Although I am super nervous that they will either cash out by going public or selling to some investor. That will be the end of it.

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

#24

Post by xp84 »

anon23432343 wrote: post #9

Jenkins works... No it dosen't or maybe it does for java which I don't care about. The ui looks like from the 90s. Finding anything in bigger projects/companies is impossible... I have browser bookmarks to find anything. The log view is annoying at best. I have nothing good to say about jenkins, it feels like it is stuck in the 2000s and refuses to change.

The 90s were the last actual advance in UI design anyway. Design has drifted in a terrible direction, in the past decade or two especially. Some of this is justified (by some) by optimizing for mobile, but that’s precisely the kind of thing I wouldn’t want creeping into my CI tooling anyway. I don’t do that on a phone.

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

#25

Post by [deleted] »

xp84 wrote: post #24
anon23432343 wrote: post #9

Jenkins works... No it dosen't or maybe it does for java which I don't care about. The ui looks like from the 90s. Finding anything in bigger projects/companies is impossible... I have browser bookmarks to find anything. The log view is annoying at best. I have nothing good to say about jenkins, it feels like it is stuck in the 2000s and refuses to change.

The 90s were the last actual advance in UI design anyway. Design has drifted in a terrible direction, in the past decade or two especially. Some of this is justified (by some) by optimizing for mobile, but that’s precisely the kind of thing I wouldn’t want creeping into my CI tooling anyway. I don’t do that on a phone.

[deleted]

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

#26

Post by juunpp »

DarkNova6 wrote: post #8
aloisdg wrote: post #5

Earlier quoted context omitted.

or enshittificated

Jetbrains is among the very few companies I’ll trust for the time being

"For the time being" is an understatement. The company has been around for 20+ years, and while I haven't used TeamCity, if it is anything like their other products, you can be certain it is built with a high level of attention to detail and that that won't change anytime soon. It is one of the few companies left I license stuff from.

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

#27

Post by btbuilder »

The kubernetes plug-in for Jenkins works well for us, and as the checkout/clone happens in the pod you don’t have the workspace bind mount problem. We are using docker-in-docker at the moment but looking at buildah. We do parallel windows container builds as well.

Jenkins is a bit like Perl IMO: there are ways to use it that avoid the majority of its sharp edges (eg putting logic in bash and just call bash, avoid groovy) if you know the perils that lurk.

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

#28

Post by juunpp »

rqtwteye wrote: post #21
DarkNova6 wrote: post #8

Earlier quoted context omitted.

Jetbrains is among the very few companies I’ll trust for the time being

Same here. Although I am super nervous that they will either cash out by going public or selling to some investor. That will be the end of it.

They aren't a silly con valley startup and they've been around for 20+ years.

https://www.jetbrains.com/company/

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

#29

Post by 2OEH8eoCRo0 »

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…

It's infrastructure. It should be boring, unchanging, and without surprises. It should be so reliable that we take it for granted.

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

#30

Post by nerdponx »

zdw wrote: post #16

All of the test runners have their issues. I've had as much problems with Jenkins as I've had with Github Runners and similar solutions. The best way out of this is to subdivide responsibilities: - Put all build/publish/test logic in Makefiles or scripts in the repo. This means that devs can run it locally as well. The only interaction between a test runner and the codebase should be running `make `. - Put all permis…

This is basically what we do, using TeamCity. DevOps sets up all the permissions and VCS integration, and helps figure out all the AWS IAM stuff. Then we get a nice clean little sandbox to run our build and deploy scripts in, which we commit to version control, including CloudFormation templates. It works really well: it's a comfortable separation of responsibilities that allows our team to move quickly with relatively little risk, and it involves almost no hands-on attention from DevOps once it's up and running, so they can direct their efforts elsewhere.
Post reply on HN