DSCI: Dead Simple CI makes job artifacts trivial
CI jobs artifacts should not be difficult
DSCI, a new CI tool, treats any file in ~/artifacts/ as a job artifact. Jobs simply write files there, and subsequent jobs read them from the same location. Removing a file makes it unavailable downstream, so artifacts act as a pipeline data buffer. No configuration or upload steps are needed.
Artifacts de-facto is any file located in ~/artifacts dir
- tuxie_
> The idea is that - Git server + YAMLess pipelines for CICD (...)
The first thing I see in the introduction [0] is a YAML configuration. What is YAMLess supposed to mean? I assumed it was "no YAML".
- melezhik
IN DSCI CI artifacts are easy, every job can create a file inside ~/artifacts directory and all subsequent will see it. If any job remove a file for ~/artifacts all the subsequent jobs won't see it.
So artifacts works as a pipeline data buffer
Very easy. No need for explicit links via YAML/whatever ...
- formerly_proven
The example contradicts itself in such a short blog post (the example creates and reads ~/artifacts.txt, the prose claims repeatedly artifacts are anything in ~/artifacts/).
This is also an even worse design than path artifacts in Gitlab CI.