CI jobs artifacts should not be difficult

anon7000•32 minutes ago

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

tuxie_•about 2 hours 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•about 2 hours ago

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

tuxie_•about 2 hours ago

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

melezhik•about 2 hours 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

melezhik•about 3 hours 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•about 1 hour ago

What's difficult about artifacts ?

melezhik•about 1 hour 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

formerly_proven•about 3 hours 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•about 2 hours ago

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

thenewnewguy•about 1 hour 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?

CI jobs artifacts should not be difficult

⚡ Community Insights

Discussion (13 Comments)Read Original on HackerNews