• vvv@programming.dev
    link
    fedilink
    arrow-up
    4
    ·
    7 months ago

    The sentiment of the first half of your comment is the cause of the problem you describe in the second half. Why /should/ the CI tool have any “steps” built in? Use a task runner, or script in your repo for any task you expect CI to do. Configure CI to run the same command you would run locally.

    • SparrowRanjitScaur@lemmy.world
      link
      fedilink
      arrow-up
      6
      ·
      edit-2
      7 months ago

      It’s not the same thing. Sometimes there are rules/conditions in the pipeline you need to test. Sometimes there are child pipelines. There really should be a way to simulate a pipeline run locally.

    • FizzyOrange@programming.dev
      link
      fedilink
      arrow-up
      1
      ·
      7 months ago

      I totally agree, with some caveats:

      1. It can make the UI much nicer (though I agree there are probably better ways to do it, e.g. native support for letting the program output determine the UI).
      2. Sometimes you need to run different things on different machines/OSes, and it’s easier if you have separate steps there.