4 ms·
And here I am planning on replacing Jenkins with GitLab CI.. do you really think Jenkins is better? Do you have any examples or thoughts you can share?
by skofgar 5y ago
And here I am planning on replacing Jenkins with GitLab CI.. do you really think Jenkins is better? Do you have any examples or thoughts you can share?
- orf 5y agoWe did a talk on it, happy to answer any questions. It’s definitely worth it. A lot of our Jenkins issues came down to “we are not very good at managing Jenkins”, but even if we where the massive jump in productivity, flexibility and team independence we saw after rolling it out makes me believe it’s just better. https://m.youtube.com/watch?v=k83hTlb9pMc https://m.youtube.com/watch?v=k83hTlb9pMc
- cyberpunk 5y agoYour plan is solid (source: building ci stuff for >10 years). I wouldn't really suggest much else, although argo is getting pretty good if you're deploying to k8s, I'd still keep gitlab around for creating your images.
- vultour 5y agoReally the most egregious thing: Manual job runs. They're a first-class citizen in Jenkins, where it lets you make a rudimentary UI by having several types for each variable (e.g. a selectbox). In GitLab the manual run just gives you a list of defined variables and a small text input next to each. Then there's dependencies between jobs which has gotten better lately but again it seems less developed compared to Jenkins. I also managed to kill the web UI with some of my pipelines when using dependent jobs because the javascript fails somewhere deep when trying to visualise the pipeline and the page just stays blank. Honestly it really depends on what you're doing. If you're mostly replacing automated builds and tests triggered by git changes then GitLab works just fine.