DSCI is simple yet super flexible pipeline engine to write CI code on regular programming languages, integrates with Forgejo using web hooks. Intended for small teams hosting Forgejo on single VM VPS and willing to create pipelines on regular programming languages
Looking at the examples, you’ve just made a brand new GitHub Actions framework. There’s YAML to wrap everything together and a bunch of Python that’s so declarative it might as well be HCL. Do you have an example that’s a bit more than “do what YAML does only in bash?”
Ok, try to do it on GH actions, share states between tasks/jobs for example:
tasks/task_one/task.py
#!/usr/python3 update_state({ 'out1' : 'out1 value', 'out2' : 'out2 value' })tasks/task_two/task.py
#!/usr/python3 dict = get_state() print(dict["out1"]) print(dict["out2"])Or share states between jobs:
jobs/job1/task.py
#!/usr/python3 update_state({ 'out1' : 'out1 value', 'out2' : 'out2 value' })jobs/job2/task.py
dict = config() print(dict["_dsci_"]["job1"]["out1"]) print(dict["_dsci_"]["job1"]["out2"])I can’t imagine how much boilerplate code (if this ever possible ) one needs to write to achieve that on YAML based pipelines (GH Actions/ etc)
And don’t tell me about jobs artifacts ))
This is a boilerplate example. I asked for something more than boilerplate. Give me some reasons why I need an incredibly stateful CI engine.
it’s just because I think in real world we have a lot of tasks where state is required or extremely beneficial, some examples on top of my head:
etc
I wouldn’t do any of that in a CI-only system. If I did, I’d use tools that exist for those jobs that already allow scripting languages.