Comment by esafak
3 months ago
Since you're exercising, you can take it to the next level where you don't specify the next step but the inputs to each task, allowing you to infer the DAG and implement caching...
3 months ago
Since you're exercising, you can take it to the next level where you don't specify the next step but the inputs to each task, allowing you to infer the DAG and implement caching...
You can do this with cue/flow, but have not turned it into a full CI system. The building blocks are there
Never heard of cue/flow will definitely check it out
cue/flow is a Go package and what powers the scripting / custom tools part of CUE. It's built on top of the language and a graph resolver.
I have another custom flow implementation that I find more ergonomic: https://hofstadter.io/getting-started/task-engine/