How a Jenkins Job Broke our Jenkins UI

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.

[ Parent | on HN ]

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

[ Parent | on HN ]

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.

[ Parent | on HN ]

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?

[ Parent | on HN ]

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.

[ Parent | on HN ]