How to Avoid Build Storms When Updating Pipeline Template Catalogs

Issue

Making changes to a pipeline template catalog will trigger builds for all jobs using that template. This can severely impact a controller’s performance.

Environment

Workaround

Adding an id field in the SCM source section of the template.yaml file will prevent builds from triggering, as long
as the id value remains the same:

version: 1
type: pipeline-template
name: no-trigger-template
templateType: MULTIBRANCH
parameters:
  - name: repoUrl
    displayName: Repo URL
multibranch:
  branchSource:
    git:
      remote: ${repoUrl}
      id: something

Have more questions?

0 Comments

Please sign in to leave a comment.