Comment by paskejl
15 days ago
I'll add one more annoying part: testing the CI/CD script on gitlab. It doesn't exist, and it's hell.
Edit: perhaps it's skill issue too, but I'm annoyed they don't have a similar feature to jump to definitions as github does.
Yeah, my experience on testing GitLab CI/CD script logic is to use a sacrificial branch and grind through test commits until it works, then Squash commits when merging back into main branch.
It's so sad that we can't just run local validations on the CI/CD script through a local emulator. If they had a local emulator approach similar to what is provided by Firebase for their cloud products, that would be amazing.
Did you give https://gitlab.com/RadianDevCore/tools/gcil a try yet? The developer has been a pretty long record of maintaining the project and it allows you to get some level of debugging locally before pushing.
> testing the CI/CD script on gitlab. It doesn't exist, and it's hell.
Did you try the pipeline editor? It's at <project_url>/-/ci/editor
You can see how GitLab expands the code, validate it (syntax), validate it against a branch (i.e. what happens when I get a push on main), and visualize the full YAML spec of what you have in the editor.
I have that problem with GitHub at the moment because we're switching from self-hosted GL to GH due to company policies, and for me it's much less readable (but I also know I've been playing with it ~1 month so far instead of the 7+ years I spent on GitLab, so need to learn tools etc).