18 engineers on Hacker News describe using GitLab CI first-hand: 8 endorse it, 3 regret it, 1 are mixed.
“I've been using it extensively the last couple of years and all in all it's been a pretty smooth experience!”
endorse · production · 2 yr · datenhorst · 2024-12-06 · source ↗ · wrong label?“omg switching away from jenkins (in our case to gitlab CI) was a revalation. SO much easier to use.”
endorse · production · hospadar · 2023-12-03 · source ↗ · wrong label?“Because its simple to switch tags, developers can create a feature branch to swap the tag and observe how long it takes.”
endorse · production · tikkabhuna · 2022-12-09 · source ↗ · wrong label?“One of the things that impressed me most about Gitlab CI was how easily we could get runners autoscaling in our own AWS environment.”
endorse · production · mcintyre1994 · 2021-09-21 · source ↗ · wrong label?“That's why we migrated to GitLab CI. We made some pretty complicated pipelines, with tens of stages... it worked with minimal hassle.”
endorse · production · stavros · 2021-09-08 · source ↗ · wrong label?“I prefer Gitlab CI/CD to Github actions (I just couldn't make sense of them).”
endorse · personal · xtracto · 2021-01-26 · source ↗ · wrong label?“In Gitlab CI, one has to check if ssh is available on the runner image, install it if it isn't present”
regret · production · mschuster91 · 2020-11-20 · source ↗ · wrong label?“we are lazy and use our GitLab CI/CD to drive model development iteration. It's not as fully featured... but it's a zero effort start.”
endorse · production · marmaduke · 2018-11-04 · source ↗ · wrong label?“To replace Gitlab CI, we moved to Buildkite since there's an integration with Phab.”
regret · production · maktouch · 2018-06-06 · source ↗ · wrong label?“We moved to GitLab CI which isn't perfect, but it provides safety rails/structure/opinions”
mixed · production · sammm · 2018-04-24 · source ↗ · wrong label?“We are stepping off of Gitlab CI because of: * Only a single pipeline allowed per repository.”
regret · production · wernerb · 2016-12-22 · source ↗ · wrong label?“It also fits really well into my gitlab ci setup for automated deployments.”
endorse · production · sanswork · 2016-12-07 · source ↗ · wrong label?“We moved off GL/GH CI for iOS apps and switched to XCode Cloud only because of the pain that Apple is w.r.t. to signing.”
neutral · production · plqbfbv · 2026-11-03 · source ↗ · wrong label?“My client has very complex pipelines which has business logic inside them... Gitlab allows splitting your pipelines to multiple files using include”
neutral · production · raptorraver · 2022-12-12 · source ↗ · wrong label?“In gitlab ci, we run govars.sh which not just sets the gopath but also adds the "bin" folder to PATH.”
neutral · production · pinkgodzilla · 2018-07-15 · source ↗ · wrong label?“These declarative configs get applied to our cluster by gitlab-ci.”
neutral · production · dfcowell · 2017-12-09 · source ↗ · wrong label?“everyone eventually moved to the GitLab CI.”
neutral · production · helb · 2017-10-17 · source ↗ · wrong label?“automated deployment from gitlab-ci. Been very happy with it.”
neutral · production · trcollinson · 2016-11-20 · source ↗ · wrong label?