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

Jenkins Is Getting Old

itnext.io

Post reply on HN
Print view View original

271–280 of 340 posts

Re: Jenkins Is Getting Old

#271

Post by falsedan »

rdtsc wrote: post #262
user5994461 wrote: post #52

Earlier quoted context omitted.

TeamCity from JetBrains is the same thing as jenkins, except the core features are working core features instead of broken plugins. It's paid software though, you get what you pay for. https://www.jetbrains.com/teamcity/ On the other hand there is Bamboo from Atlassian. https://www.atlassian.com/software/bamboo I really don't understand this mentality of there is no better tools when there are better tools than jenki…

I agree. I used TeamCity and liked it. It was like Jenkins, but easier to setup, less messy and just worked for what we needed it. It was worth paying every penny for it.

When I used it, I found that devs loved to set up jobs as it was way easier than Jenkins configuration

Re: Jenkins Is Getting Old

#272

Post by jl-gitlab »

staticsnow wrote: post #264
jl-gitlab wrote: post #258

Earlier quoted context omitted.

Thanks for the incredible feedback! CI/CD product director here. A few thoughts: - Templates We actually have done a lot here recently, we've improved includes so that they have a lot more flexibility ( https://docs.gitlab.com/ee/ci/yaml/#include ), and have even refactored our own Auto DevOps implementation to take advantage of this: https://docs.gitlab.com/ee/topics/autodevops/#using-componen... . In this way, you…

I hear you on plugins, and I agree they are problematic. I went back and forth on whether to include this or not TBH. I'll give you a couple of examples of use cases for plugins: We have an artifact repo that can store NPM, Python and other artifacts (Nexus if you're interested). I wrote a plugin for TeamCity that can grab artifacts from a build and upload them to the repository. Obviously this can be done in a scrip…

Thanks for sharing, this is really great feedback.

Re: Jenkins Is Getting Old

#273

Post by kuschku »

jl-gitlab wrote: post #255
StavrosK wrote: post #15

Earlier quoted context omitted.

I will second this, Gitlab has the best CI I've ever used, and I don't know what it is. The UI is just so clean, it does what I need to and is easy to configure. I put all my projects on Gitlab mostly because of the CI, but also because of the other great features.

GitLab product director for CI/CD here - thanks so much for the feedback, everyone. It's really great to read how much you're getting value out of what we built. We have an overall CI/CD direction page up at https://about.gitlab.com/direction/cicd which you can drill down into the individual stages plans from. Feedback is always welcome, we love building things in partnership with real users. You can reach me at jaso…

Have you started working on providing a UI for the XML test result artifacts produced in CI runs?

They are displayed in merge requests but not anywhere in the normal CI pipeline UI and I'd live to be able to see those and see what works and what doesn't.

Re: Jenkins Is Getting Old

#274

Post by EngineerBetter »

I'm a very strong Concourse proponent. We've been using it exclusively for three years, and it's better than anything we've experienced that our customers use (I run a consultancy).

We run Concourse London User Group, and the first few instances were like some kind of Jenkins survivor's support group.

Re: Jenkins Is Getting Old

#275

Post by KaiserPro »

stefan_ wrote: post #194
jensvdh wrote: post #134

Earlier quoted context omitted.

Pretty sure they meant the UI is so ugly it's offensive.

If it was only ugly. No, Jenkins UI is the dumpster fire that you would have gotten 20 years ago throwing a bunch of ActiveX components onto a VB panel. Like, let me just drag this Camera component to my snazzy program. Any one click can be a gateway into a one million miles deep rabbithole of unbridled mediocrity and brokenness.

looks? naa thats not the problem.

Its badly laid out, inconsistent and worst of all lazy loading. So its not like you click a button and everything displays.

No, you click a button and wait 1.5 seconds whilst everything jiggles about.

Re: Jenkins Is Getting Old

#276

Post by KaiserPro »

jniedrauer wrote: post #146
KaiserPro wrote: post #95

I have been with jenkins since about 2010. At its peak I had to shepherd ~50 masters of varying ages, plugins and levels of customisations. Yes, it allowed repeatable builds, and it can be, in certain circumstances a very good replacement for cron jobs where you need to administer >5000 machines. However, it has an offensive UI, the plugin system appears to be designed to deliberately cause things to break, versionin…

Do you self-host gitlab? I'd definitely consider moving but it would also mean moving my source control.

I was very much tempted last year, I went so far as to spin everything up and test.

However since the reliability has improved 10 fold in the last year, it seems less worthwhile.

I do however have a number of gitlab runners running on our own stuff. WE also have an autoscale integration to save money on GPU machines.

Re: Jenkins Is Getting Old

#277

Post by KaiserPro »

fizwhiz wrote: post #99
KaiserPro wrote: post #95

I have been with jenkins since about 2010. At its peak I had to shepherd ~50 masters of varying ages, plugins and levels of customisations. Yes, it allowed repeatable builds, and it can be, in certain circumstances a very good replacement for cron jobs where you need to administer >5000 machines. However, it has an offensive UI, the plugin system appears to be designed to deliberately cause things to break, versionin…

Why does a fictional butler offend you?

Try jumping onto a jenkins box thats been left to rot.

Has been abused by three teams of developers.

Its not been updated in two years.

Where is that builds thats failing? what has changed? what are the active plugins, who updated them, and when?

etc, etc, etc,

All of this requires a massive amount of clicking, and because it lazy loads in some versions, it can tak >3 seconds to load a page.

Re: Jenkins Is Getting Old

#278

Post by KaiserPro »

StevePerkins wrote: post #124
KaiserPro wrote: post #95

I have been with jenkins since about 2010. At its peak I had to shepherd ~50 masters of varying ages, plugins and levels of customisations. Yes, it allowed repeatable builds, and it can be, in certain circumstances a very good replacement for cron jobs where you need to administer >5000 machines. However, it has an offensive UI, the plugin system appears to be designed to deliberately cause things to break, versionin…

> " ... has an offensive UI... " > " ... suck massive genitals... " I cannot believe that this is the top-voted comment.

which bit?

was it because I mentioned genitals, or should I use stronger coprophilic comparative adjectives instead?

or was it because expressing intense dislike for a slow, arcane and frustratingly inconsistent UI.

Its not like I dismiss jenkins out of hand. There are still strong usecases. But there better, simpler, repeatable alternatives

Re: Jenkins Is Getting Old

#279

Post by KaiserPro »

majkinetor wrote: post #133
KaiserPro wrote: post #95

I have been with jenkins since about 2010. At its peak I had to shepherd ~50 masters of varying ages, plugins and levels of customisations. Yes, it allowed repeatable builds, and it can be, in certain circumstances a very good replacement for cron jobs where you need to administer >5000 machines. However, it has an offensive UI, the plugin system appears to be designed to deliberately cause things to break, versionin…

Gitlab is awesome, its impressive what you get for free. Runners are nice, can run in powershell, bash, docker, vm , you name it. The main problem with runner is that you cant easily execute build script on the host. Exec command isn't very useful and AFAIK deprecated.

You haave to install the runner on the target, then you can use exec, plus a switch to allow it to run as root. The key is it has to be configured on the target device _first_.

Then you have a root shell on your target device (I leave the "should" as an exercise for the user )

But, It won't work using the free shared gitlab runners.

Re: Jenkins Is Getting Old

#280

Post by oblio »

twunde wrote: post #112
Cyph0n wrote: post #42

Earlier quoted context omitted.

> GUI-oriented Not with pipeline files. I am a total Jenkins noob, but I was able to (relatively) quickly setup a minimal job that automatically pulls config from the relevant GH repo.

Ah yes, pipelines do make a difference in configuring jobs. However, how are you managing your plugins? Your Jenkins configs? Most likely those are manual (however if you've found a way that works well, please share). I've also found that for some functionality, I've had to add Groovy into my pipelines. That said, pipelines has made a HUGE difference. I still want to migrate but this fixes a large pain point.

Try this: https://github.com/jenkinsci/configuration-as-code-plugin
Post reply on HN