I always try to put as little logic into CI-Runner-specific tooling as possible and rather have everything automated via the usual programming language build tooling, which you can run locally.
How to Test and Run GitHub Actions Locally - Earthly Blog
Submitted 11 months ago by Die4Ever@programming.dev to programming@programming.dev
https://earthly.dev/blog/using-github-actions-locally/
Comments
Knusper@feddit.de 11 months ago
Die4Ever@programming.dev 11 months ago
Yeah I need to start doing this more lol
taaz@biglemmowski.win 11 months ago
snowe@programming.dev 11 months ago
act is so hard to use and the docs are terrible. Every time I go to use it I give up a few hours later having gotten nowhere. Incredibly frustrating experience.
onlinepersona@programming.dev 11 months ago
BeanCounter@sh.itjust.works 11 months ago
Because if they try, you get gems like XÆA-12
odium@programming.dev 11 months ago
You do get some pretty good names like Netflix, roomba, Skype, etc.
thesmokingman@programming.dev 11 months ago
One of the frustrating things with Dagger is that you still have to set up your pipeline tool. Sure, you’re theoretically running the same thing local and remote, but it doesn’t remove much in the way of CI work. Azure stuff is (was?) less supported. And while the move away from CUE was the right one, there’s still a lot of CUE around.
worldofgeese@lemmy.world 11 months ago
My employer, garden.io, offers pipelines you can run anywhere, in GitHub Actions, GitLab CI, locally, wherever! We capture all your dependencies in a dependency graph, then cache all your inputs: builds, tests, run scripts. We’re open source at github.com/garden-io/garden