Re:How a Jenkins Job Broke our Jenkins UI
by globular-toast on Thursday June 03, 2021 @02:45PM
(#27385619)
Gitlab.
[ Parent
| on HN ]
Re:How a Jenkins Job Broke our Jenkins UI
by nobleach on Thursday June 03, 2021 @02:53PM
(#27385733)
Both Gitlab and Bitbucket Pipelines fall under the "sufficient" category in my book. I've used both in large productions deploys and, they for the most part, get the job done. Gitlab has moments where it doesn't work - and one needs to go check the status page... and at times report an outage. But honestly, I still place it in higher regards than Jenkins.
Re:How a Jenkins Job Broke our Jenkins UI
by diroussel on Thursday June 03, 2021 @03:06PM
(#27385921)
Yes gitlab so so much nicer to run on than Jenkins.
Sure there is something missing for more elaborate build pipelines, but not enough missing to block you.
The best think about gitlab vs Jenkins is that there are no plugins. So it’s very clean what is gitlab and what is your config of it.
Whereas Jenkins has so many plugins and config for the plugins that it’s hard to say where Jenkins ends and your build pipelines begin.