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

  • Sp1983@programming.devOP
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    1 day ago

    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:

    • creation of virtual machines with dynamic IP addresses
    • creation of bug tracking system tickets with unique ticket IDs
    • looking up in databases where fetched records have unique IDs

    etc

    • thesmokingman@programming.dev
      link
      fedilink
      arrow-up
      2
      ·
      1 day ago

      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.

      1. Why wouldn’t you use IaC tools for this? All the majors have Python already.
      2. What build or deploy task needs to both create and reference a bug ticket?
      3. What build or deploy task needs to do database lookups? Or possibly what task needs those across multiple, independent stages?
      • Sp1983@programming.devOP
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        1 day ago

        If you use tools gluing them into YAML - you get YAML bloated with time . When you say those tools already having Python - excellent I would like to use those Python libs or SDK directly in my Python code instead of juggling those tools as cli or code blocks inside YAML

        UPDATE: and yeah , re-read again - I guess the most of automation is done today via “CI” pipelines even when those are not meant to be CI only, like you said … anyways the rest I have said stands true for me … don’t bake your code into YAML )