404: Page Not Found
dev.to

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

  • thesmokingman@programming.dev
    0·
    2 months ago

    This is a boilerplate example. I asked for something more than boilerplate. Give me some reasons why I need an incredibly stateful CI engine.

    • Sp1983@programming.devOP
      0·
      2 months 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
        0·
        2 months 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?