✧✦Catherine✦✧today is the first time i encountered recursive submodules in the wild (i'm looking at a repository that includes itself as a submodule 13 times)
working with this repo does not spark joy
i am slowly becoming a "(GitHub|Forgejo) Actions expert" in the same way and sense as i have become a CMake expert
distressing.
0xC0DEC0DE07EA@whitequark I dislike the Actions model and prefer GitLab’s CI system which is basically just shell wrapped in YAML. That’s maybe wrong-headed of me; I don’t know.
We still use Jenkins at work and, for my sins and indiscretions, I have to deal with a bunch of Groovy scripting and plugins. My longer term takeaway from this is that CI should reuse the same scripting or patterns that a maintainer uses to perform the build and testing runs and not something else. I don’t know if that’s something that generalizes fully, but I’d make it that way in a heartbeat if I could at work.
We still use Jenkins at work and, for my sins and indiscretions, I have to deal with a bunch of Groovy scripting and plugins. My longer term takeaway from this is that CI should reuse the same scripting or patterns that a maintainer uses to perform the build and testing runs and not something else. I don’t know if that’s something that generalizes fully, but I’d make it that way in a heartbeat if I could at work.
@c0dec0dec0de I mean nothing stops you from making an Actions workflow that's one big
run: step@whitequark that’s a good point. As long as any reporting can be done from logs of that stage or cached artifacts, that would get the best of both worlds.
@whitequark at some point in the indeterminate future, I will probably need to assist in migrating from Jenkins to GitLab CI and we’re going to lose the convenient all-in-one-app metrics/diagnostics except as downloadable reports (as I understand it).