News for hackers. Stuff that matters.
Re:How a Jenkins Job Broke our Jenkins UI by mdeeks on Thursday June 03, 2021 @03:00PM (#27385841)
As a counter point, we had major issues with just paying for it via CircleCI. Excessive downtimes, a UI so slow it was nearly unusable, etc. We decided at the time we couldn't bet our company on it and we moved to Jenkins. We have far more control, build time and build costs are lower, uptime is better (All of this at the expense of initial dev time and maintenance of course). Generally we are a SaaS company, but paying for a solution just doesn't always work when you get larger and when there are limited options out there.
Re:How a Jenkins Job Broke our Jenkins UI by diroussel on Thursday June 03, 2021 @03:12PM (#27385991)
Try gitlab. You can run it yourself. Great up time.

And best of all it’s much easier to run and upgrade than Jenkins.

Jenkins and it’s plugins can get quite brittle and is quite an art to automate the installation and config of all those plugins.

Re:How a Jenkins Job Broke our Jenkins UI by mdeeks on Thursday June 03, 2021 @04:11PM (#27386676)
I'm interested in trying Gitlab, but this does not look easy to run (from their docs): https://plantuml.gitlab-static.net/png/U9oDLbrlsZ0KVVUli9gNB...
Re:How a Jenkins Job Broke our Jenkins UI by dfcowell on Thursday June 03, 2021 @04:45PM (#27387056)
Unless you’re a very large organization, you’re not going to be managing each of those components individually.

The “Omnibus installation” as they call it is pretty easy to use. Just bring a Postgres DB and a redis instance.

Re:How a Jenkins Job Broke our Jenkins UI by crummy on Thursday June 03, 2021 @05:37PM (#27387674)
You don't even need to BYO databases - they have an omnibus docker compose setup that runs everything for you.

https://docs.gitlab.com/omnibus/docker/#install-gitlab-using...

Re:How a Jenkins Job Broke our Jenkins UI by richwater on Thursday June 03, 2021 @05:47PM (#27387804)
The discussion chain is everything that's wrong with modern engineering. A complex topic progressively simplified and abstracted to just "Run this container", ensuring no one in your org actually understands how it works, how to maintain it and how to debug it.
Re:How a Jenkins Job Broke our Jenkins UI by crummy on Thursday June 03, 2021 @06:11PM (#27388086)
The GP was interested in "trying" Gitlab. If you want to try it out, but are wary of the time involved, isn't a docker-compose installation a great solution?
Re:How a Jenkins Job Broke our Jenkins UI by Aeolun on Thursday June 03, 2021 @06:25PM (#27388213)
Gitlab is a complex system. I wouldn’t expect anyone to suddenly understand my companies’ product either.