buildkite-plugin

steps:
  - label: "Detecting which mono-repo has changed"
    plugins:
      - chronotc/monorepo-diff#v1.3.0:
          diff: "git diff --name-only HEAD~1"
          watch:
            - path: "folder-a/"
              config:
                label: ":pipeline: Continue blue-alice pipeline"
                command: "buildkite-agent pipeline upload ./folder-a/.buildkite/pipeline.yml"

Many of our builds save an artifacts in step 1 and then download it in steps 2..N. We've seen several flaky builds this week based on failure to download artifacts from step 1 on only one of the later steps. They are all 502 errors.

Copying from an email discussion with support@, would be great if this was retried more proactively (with sensible backoff and limits, of course - don't want to mak

• Cleans up pd4 tempdirs
• Cleans up read-only files from client workspaces