buildg VS dagger

To install buildg follow the instructions on the Buildg GitHub page.

https://github.com/ktock/buildg

Sounds a lot like https://dagger.io/ . Maybe you can take some inspiration from them

Anyshift.io AppCD AppMap.io CloudTruth Dagger.io DryRun Security Overmind Prequel RunWhen Stanza

Have you seen https://dagger.io? (by the OG creators of Docker)

Fully containerized builds based on BuildKit with a SDK interface. Works really well on both linux and mac

Does the caching, parallel, lazy DAG really well, removes the need for intermediate or base containers to run builds, or more generally containerized workflows

If you want this concept, but without the Yaml, check out https://dagger.io

> GHA has "service containers", but unfortunately the feature is too basic to address real-world use cases: it assumes a container image can just … boot! … and only talk to the code via the network. Real world use cases often require serialized steps between the test & the dependencies, e.g., to create or init database dirs, set up certs, etc.)

My biased recommendation is to write a custom Dagger function, and run it in your GHA workflow. https://dagger.io

If you find me on the Dagger discord, I will gladly write a code snippet summarizing what I have in mind, based on what you explained of your CI stack. We use GHA ourselves and use this pattern to great effect.

Disclaimer: I work there :)

Dagger (https://dagger.io) is a great way to use BuildKit through language SDKs. It's such a better paradigm, I cannot imagine going back.

Dagger is by the same folks that brought us Docker. This is their fresh take on solving the problem of container building and much more. BuildKit can more than build images and Dagger unlocks it for you.