Djinn CI – open-source CI platform

https://docs.djinn-ci.com/admin/configuration/

> Each configuration file for Djinn CI uses its own structured configuration language.

I sure do hope that adds as much value to your life as it causes pain for people trying to learn Yet Another Vanity DSL Because Reasons™

You will want to invest a lot more energy in the one point of documentation anyone new to this cares about: https://docs.djinn-ci.com/user/manifest/ Compare how short and ill specified that is versus https://docs.gitlab.com/ee/ci/yaml/

As a concrete example, in GLCI I have

    variables:
      thing: |
        #!/usr/bin/env bash
        echo "hello from $CI_PIPELINE_ID"

so in dijinn, is it this?

    env:
    - thing=#!/usr/bin/env bash
      echo "hello from $CI_PIPELINE_ID_IN_DIJINN"
    # or this?
    - thing=#!/usr/bin/env bash\necho "hello..."

and I know I'm not supposed to complain about website styling, but stop being cute with that width:40% -- I have a 4K monitor for a reason