I have to say, pretty much every CI/CD tool, build automation or whatever you want to call it, sucks.
Somehow they all manage not to offer boilerplate actions since that would be too restrictive, yet they also stand in your way if you want to have advanced features.
I often end up writing pipeline steps/jobs thinking “how is that not already built-in?”.
And my absolutely biggest pain point: why the fuck is there not a single tool that lets me execute pipelines locally? Why do I have to have 200 commits all saying a variation of “pipeline test”?
I agree so, so much; and I’ve been saying similar things for years.
But I recognize that it’s probably a hard problem. For one thing, auth is almost never going to work the same way in CI as it does locally.
…still, though, I feel like there could be some much nicer tooling here.
It can’t be that hard to create a test harness, so I can plug my own variables into the runner context.
Even just an 80% solution would speed up development tremendously.
Well, for GitHub Actions, there’s this: https://github.com/nektos/act
That actually looks quite promising. You don’t happen to know of a similar project for Gitlab runners?
The sentiment of the first half of your comment is the cause of the problem you describe in the second half. Why /should/ the CI tool have any “steps” built in? Use a task runner, or script in your repo for any task you expect CI to do. Configure CI to run the same command you would run locally.
I totally agree, with some caveats:
- It can make the UI much nicer (though I agree there are probably better ways to do it, e.g. native support for letting the program output determine the UI).
- Sometimes you need to run different things on different machines/OSes, and it’s easier if you have separate steps there.
haven’t tried it myself, but I’ve heard https://earthly.dev/ is supposed to address the execute locally problem
