I wish the premium paid features were available for free on public repos. I mean my public repos are not real free and open source projects. I’m just learning and playing around but if you let me use premium features maybe some day I can pester my boss to get them at work
i think that the idea of actions (actions the concept not actions the product) is a really good way of building CI pipelines…
we all know that shell scripts are rubbish, so building your CI pipeline out in composable steps written in a proper language is much more robust
having those steps maintained by the open source community inside a marketplace is also excellent! you don’t need to manage things like setting up AWS variables, managing refresh tokens, etc: you can use an action just by referencing it, easier than you’d install a package… and those actions can use well-maintained open source libraries to do their jobs
there’s a whole lot more, but all the reasons basically revolve around the fact that the composable units written in a modern language shared with everyone is so, so much better than chaining bash scripts together: even if they can be run inside containers (which GHA can do too)
(also, i’ve found github actions much faster than gitlab ci… not comparing runner speed because obviously that’s highly dependent on what you host it in; just time to pick up jobs and time to start the agent)
GitHub is so far behind GitLab in CICD it’s not even funny
Is this feature available on GitLab?
IIRC, Gitlab labels it “merge train”
Thanks! Unfortunately, my company is a cheapskate, so I don’t get to use it… It’s available on the premium tier.
I wish the premium paid features were available for free on public repos. I mean my public repos are not real free and open source projects. I’m just learning and playing around but if you let me use premium features maybe some day I can pester my boss to get them at work
i think quite the opposite… gitlab ci is very last-gen: github actions is where everyone in ci will be headed from now on!
Why do you think it’s better? Genuinely wondering
i think that the idea of actions (actions the concept not actions the product) is a really good way of building CI pipelines…
we all know that shell scripts are rubbish, so building your CI pipeline out in composable steps written in a proper language is much more robust
having those steps maintained by the open source community inside a marketplace is also excellent! you don’t need to manage things like setting up AWS variables, managing refresh tokens, etc: you can use an action just by referencing it, easier than you’d install a package… and those actions can use well-maintained open source libraries to do their jobs
there’s a whole lot more, but all the reasons basically revolve around the fact that the composable units written in a modern language shared with everyone is so, so much better than chaining bash scripts together: even if they can be run inside containers (which GHA can do too)
(also, i’ve found github actions much faster than gitlab ci… not comparing runner speed because obviously that’s highly dependent on what you host it in; just time to pick up jobs and time to start the agent)