CI jobs artifacts should not be difficult(deadsimpleci.sparrowhub.io)
18 pointsby melezhik6 hours ago5 comments
  • tuxie_5 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

    • melezhik5 hours ago
      Yep - tiny , simple structured YAML on the top ( only to list jobs technically) everything else is general purpose programming languages
      • tuxie_5 hours ago
        But then your claim is immediately false. It's confusing at best, a loss of trust with the reader at worst.
        • melezhik4 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
          • drfloyd514 hours 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!

            • melezhik3 hours ago
              I like the idea, thanks
  • melezhik6 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 ...

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

    • melezhik5 hours ago
      Oh. It’s just a typo. Why it’s worse ?
      • thenewnewguy4 hours 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?
        • melezhik2 hours ago
          the example is fixed, thanks for spotting that
  • nkapias4 hours ago
    What's difficult about artifacts ?
    • melezhik4 hours 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
  • anon70003 hours ago
    This feels like it’s not built for massively parallelized CI steps