DSCI is simple yet super flexible pipeline engine to write CI code on regular programming languages, integrates with Forgejo using web hooks. Intended for small teams hosting Forgejo on single VM VPS and willing to create pipelines on regular programming languages
Only as high level glue , main logic is just normal programming languages - see here https://github.com/melezhik/DSCI/tree/main/examples
You can (and should!) do exactly the same with “traditional” GitHub Actions style YAML.
Avoid putting commands in the YAML - put those in separate scripts and call them from the YAML. The YAML should only be used for things that can’t be done from scripts (e.g. job matrices, uploading artifacts, reporting status etc.)
This is exactly what I try to avoid, cause:
many people (in my experience ) even don’t bother refactoring YAML spaghetti code to separate scripts and we end up unmaintainable codebase
and even if one has to do such a refactoring what is the point of using YAML at all ?
All I need just a collection of tasks/jobs written on languages of choice and I don’t need YAML “programming” language at all )
PS And btw I don’t mind having a minimal amount of YAML as configuration layer and this is what is presented in DSCI, but only minimal ))
It allows the CI engine to determine which jobs to start, what their steps are etc.
To be fair I have worked on one project that had very complex CI and we almost decided to generate the CI graph procedurally with a Python script (Gitlab supports this, somewhat awkwardly). But in the end we decided it wouldn’t be worth the overhead of writing, maintaining and learning a whole new CI system on top of Gitlab’s CI.
The issues you had just proves that YAML based CI approach always leads to troubles with time. And yeah, I have been there, code generators for YAML. Hundreds of lines for YAML pipelines, etc ))
Yep, like a said , I don’t mind to have such a configuration inside YAML, but this should NOT be pipeline code itself )