CI jobs artifacts should not be difficult

(deadsimpleci.sparrowhub.io)

19 points by melezhik 3 days ago|15 comments

•

tuxie_ 3 days ago

> 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".

[0] https://deadsimpleci.sparrowhub.io/doc/introduction

•

melezhik 3 days ago

Yep - tiny , simple structured YAML on the top ( only to list jobs technically) everything else is general purpose programming languages

•

tuxie_ 3 days ago

But then your claim is immediately false. It's confusing at best, a loss of trust with the reader at worst.

•

melezhik 3 days ago

Ok, maybe I will need to add better wording , but the idea stays the same unlike in many ci systems ( GitHub/gitlab/etc pipeline code is general purpose programming language not YAML ), if you read further jobs/tasks you will see

•

drfloyd51 3 days ago

Some of your intended audience will not read further. Which is the point about trust.

You’ve got something cool to show, and a reader is telling you an impediment to your sharing.

Fix your description. 99% less YAML!

•

melezhik 3 days ago

I like the idea, thanks

•

melezhik 2 days ago

changed on the website

•

formerly_proven 3 days ago

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.

•

melezhik 3 days ago

Oh. It’s just a typo. Why it’s worse ?

•

thenewnewguy 3 days ago

It's a typo that carried over to the second code example of trying to read the file too? Is the sample code completely untested?

•

melezhik 3 days ago

the example is fixed, thanks for spotting that

•

melezhik 3 days ago

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 ...

•

nkapias 3 days ago

What's difficult about artifacts ?

•

melezhik 3 days ago

In the systems I am familiar with one has to explicitly describe jobs artifacts via YAML files as dependencies, for the most cases it’s not needed as all I need is to pass files between jobs. I don’t want explicit syntax for that, just shared ~/artifacts directory

•

anon7000 3 days ago

This feels like it’s not built for massively parallelized CI steps