Skip trigger on pipeline install

Is there any way to have a pipeline not trigger right after it is installed - but instead on any subsequent versions?

We sometimes wipe everything clean and repave all our pipelines. When we do this all pipelines will trigger on the most recent commit and we get a huge stampede of redundant notifications.

Anyone else have something similar?

The short answer is no; there’s no way to tell the Concourse scheduler to not trigger on the version available when you recreate a pipeline.

Some ideas:

  • Keep the pipelines or job(s) paused until you know a new version is available; manually unpausing the pipeline/job(s) later
  • Keep the pipelines or job(s) paused and unpause automatically after x hours or at a certain time (9am when everyone comes into the office)