• CodeMonkey
    link
    fedilink
    arrow-up
    4
    ·
    2 months ago

    Do you think that is too slow or too fast? Many of the CICD pipelines I work with take much longer than that. We have integration tests that deploy a fresh Kubernetes instance, install our software stack into it, and run several test suites against it.

    If I am working on bug found by a pipeline that takes more than a couple minutes to run, it is generally worth my time to figure out how to run the failing test individually on my dev machine. That approach does not help when I am debugging issues with the pipeline itself.

    • onlinepersona
      link
      fedilink
      arrow-up
      3
      ·
      2 months ago

      At least for all the things I’ve worked on 10 minutes are considered unbearable. 20 means it’ll be forgotten because a new task has been started.

      What do you while waiting for the CI? Practice fencing?

      Anti Commercial-AI license

      • pwshguy (mdowst)OP
        link
        fedilink
        arrow-up
        4
        ·
        2 months ago

        This one in particular takes around an hour to run. It deploys a bunch of resources to Azure and runs a all of our integration tests. It does a complete wipe and redeploy each time, so it takes a while. Fortunately, this pipeline is only run as a final test before prompting to production, so normally I only run it once a month or so. While it’s running I’ll work on my pull requests, release notes, closing user stories, etc.