4 ms·
GHA have always been a PITA for any serious DevOps; it's quite clear they were designed to integrate in 7 lines of code and then tell everyone who complains tha
by Normal_gaussian 5mo ago
GHA have always been a PITA for any serious DevOps; it's quite clear they were designed to integrate in 7 lines of code and then tell everyone who complains that they're doing it wrong.
This does not surprise me.
- freedomben 5mo agoIt is a PITA, but that can be significantly improved IMHO if you just write shell script wrappers for your tasks. Not only does it make it easier to run CI locally, but it also makes it so much easier to move platforms in the future. When the GH action YAML is just invoking shell scripts, I find it quite pleasant to use
- tracker1 5mo agoThat's mostly been my approach as well... I've also started relying on Deno for a lot of general shell scripting as you can use repository modules without an install step and shebang works outside Windows (or inside with bash).
- jamesfinlayson 5mo agoYeah this what I've always done too - already had to migrate from GitHub to GitLab once and a test.sh script saved me a lot of time.
- datadrivenangel 5mo agoYou've perfectly described how microsoft operates and how github actions is apparently based on AzureDevOps pipelines.
- youre-wrong3 5mo agoNo. GHA has always been trash before MS got to it. A lot of GHA influenced ADO.
- tracker1 5mo agoIMO the .yaml config for ADO was an improvement... though it carries similar issues to GHA. I mostly use it as a script runner.