4 ms·
I may be targeted for calling this the “correct” way, but it is - it’s the only correct way. Otherwise you need complicated setups to test any of the stuff you
by lucasyvas 2y ago
I may be targeted for calling this the “correct” way, but it is - it’s the only correct way.
Otherwise you need complicated setups to test any of the stuff you put up there since none of it can be run locally / normally.
GitHub Actions, like any CI/CD product, is for automating in ways you cannot with scripting - like parallelizing and joining pipelines across multiple machines, modelling the workflow. That’s it.
I would really appreciate an agnostic templating language for this so these workflows can be modelled generically and have different executors, so you could port them to run them locally or across different products. Maybe there is an answer to this that I’ve just not bothered to look for yet.
- giancarlostoro 2y ago> I would really appreciate an agnostic templating language for this so these workflows can be modelled generically and have different executors, so you could port them to run them locally or across different products. Maybe there is an answer to this that I’ve just not bothered to look for yet. Terraform? You can use it for more than just "cloud"
- jasonlotito 2y agoIn addition, adding our own custom modules for terraform is, all things considered, fairly easy. Much easier than dealing with the idiosyncrasies of trying to use YAML for everything.
- giancarlostoro 2y agoI have not used Terraform outside of for Azure resources, but I am always astounded by how much it can handle.
- HdS84 2y agoMaybe packer? That's terraform syntax, but optimized for building Vms.
- donatj 2y agoIt was YAML but I actually really liked Drone CI's "In this container, run these commands" it was much more sane than GitHub Actions "Here's an environment we pre-installed a bunch of crap in, you can install the stuff you want every single time you run a workflow".
- vel0city 2y agoYou can specify a container image in GHA for a job to run in. https://docs.github.com/en/actions/writing-workflows/choosing-where-your-workflow-runs/running-jobs-in-a-container https://docs.github.com/en/actions/writing-workflows/choosin...
- HdS84 2y agoYou can also do that in Gh. Gizlab does that, too. But I hate it. When you do this, every build becomes cargo culting commands until it works. Ntm every build it's is own special snowflake from hell. I want standardized builds which output everything I need (artifact, warnings, security issues etc) without me feeling like a necromancer. Gh solves this okayish, but extending and debugging is a pain.
- dleeftink 2y agoMaybe what .devcontainers does? As a thin wrapper to Docker, I find it makes testing configurations easier.