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.
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.
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?
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.