4 ms·
GHA is "good enough" (GitLab CI was/is much better IMO), and it'll likely never go away because of how dominant GitHub is. Also, a simpler solution that takes
by hardwaresofton 3y ago
GHA is "good enough" (GitLab CI was/is much better IMO), and it'll likely never go away because of how dominant GitHub is.
Also, a simpler solution that takes a bit more discipline is writing all your CI tasks as scripts/makefile|justfile targets/etc and using containers to run them in GHA.
IIRC containers are a little slower than running scripts in the VM directly (more than it must necessarily be), and also cross-platform builds might be slightly more complicated...
- XorNot 3y agoGitlab CI desperately needs backwards dependencies. A huge number of my remaining problems with it would be solved if I could subscribe to upstream outputs from my own pipelines.
- mdaniel 3y agoI'm aware it says Premium but FWIW it does seem that exists since 12.8: https://docs.gitlab.com/ee/ci/pipelines/#trigger-a-pipeline-when-an-upstream-project-is-rebuilt https://docs.gitlab.com/ee/ci/pipelines/#trigger-a-pipeline-... I can also appreciate that the devil's in the details, so all its current constraints may not cover your use case
- XorNot 3y agoSo this seems to be enabled on the edition I'm using at work, but the limit is bizarrely "two pipelines". Which I already exceed since I have projects using git-dependencies in Python with 3+ repo dependencies. But it's also a weird project setting not a .gitlab-ci one.