Live data from Hacker News

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

twitchard.github.io

31–40 of 275 posts

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

#31
I don't mind Jenkins pipeline limitations because my philosophy is that CI should be as simple and contain as little build logic as possible.

Every job should be a few simple commands or a python script or something I can run locally. This simplifies reproducing and debugging issues caught by CI -- there's nothing worse than wasting time trying to reproduce what happened.

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

#32
post #26

Earlier quoted context omitted.

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.

It is a capitalist enterprise, which means control by its very owners is contingent on making enough profit to pay the bills, in the very best of cases. This is not my opinion.

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

#33
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…

Agreed - I'd much rather spend more time working around Jenkins' peculiarities once than constantly deal with change for the sake of change because some PM wants more "engagement" to justify their job and promotion.

Tools need to be boring and get out of my way - something "modern" tooling forgets since everyone's paycheck depends on forgetting that.

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

#34

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 gro…

> We are uding docker-in-docker at the moment

You can also run a "less privileged" container with all the features of Docker by using rootless buildkit in Kubernetes. Here are some examples:

https://github.com/moby/buildkit/tree/master/examples/kubern...

https://github.com/moby/buildkit/blob/master/examples/kubern...

It's also possible to run dedicated buildkitd workers and connect to them remotely.

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

#35
Jenkins is rock solid. Been using it for three years to deliver highly critical software. The development experience is the worst of all ci tools since no one wants to setup jenkinspipelineunit to test the pipelines. Dagger might be the salvation here, but even that tool didn't support Jenkins out of the gate. And for those that are reading this, the statement about pipeline groovy being a trap is exactly right. Avoid writing groovy at all costs. No one on the team wants to get good groovy and if you do, you're weird. The way we do it is to just use the Jenkins file to call the scripts (or tools) with bare minimal script code.

Edit, forgot to add that I recently interviewed a bunch of candidates for a high paying job at a ai hardware company and every one of those candidates stated they worked on or near a project that involved moving from Jenkins to Gitlab CI.

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

#36
post #2

Avoid Jenkins, and if you can, try https://www.jetbrains.com/teamcity "TeamCity Professional is free – even for commercial use – and has no limitations on features, number of users, or build time. It allows you to configure up to 100 builds and run up to 3 builds in parallel, which is more than enough for most projects"

Yeah, I use TeamCity for both my test and production setups. I've only had positive experiences with it, very nice seamless integration with Jetbrains' IDEs as well.

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

#37
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 BlueOcean is one of the best "fancy UIs"

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

#38
post #13
post #2

Avoid Jenkins, and if you can, try https://www.jetbrains.com/teamcity "TeamCity Professional is free – even for commercial use – and has no limitations on features, number of users, or build time. It allows you to configure up to 100 builds and run up to 3 builds in parallel, which is more than enough for most projects"

> TeamCity Professional is free – even for commercial use – and has no limitations on features, number of users, or build time. Yeah, no. There's obviously gonna be a catch in the future.

Maybe, yes. But it's exactly the same license / pricing since i first used it and that's somewhat around 5-7 years. Quite some time so far.

I would recommend TeamCity to everyone, it's awesome.

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

#39
post #13
post #2

Avoid Jenkins, and if you can, try https://www.jetbrains.com/teamcity "TeamCity Professional is free – even for commercial use – and has no limitations on features, number of users, or build time. It allows you to configure up to 100 builds and run up to 3 builds in parallel, which is more than enough for most projects"

> TeamCity Professional is free – even for commercial use – and has no limitations on features, number of users, or build time. Yeah, no. There's obviously gonna be a catch in the future.

Just as a note: TeamCity originally launched around 2005 sometime, so it's coming up to be 20 years old soon. I think TeamCity Professional, when self-hosting, has been free since always.

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

#40

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.

Maybe they will at one point, but JetBrains so far did never take VC capital (and if I remember correctly said "no" more than once) [1]. That doesn't tell about the future, but they probably had many options to cash out and never did.

[1] https://www.bloomberg.com/news/articles/2020-12-18/czech-sta...

Post reply on HN