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

• CloudBees CI (CloudBees Core)
• CloudBees CI (CloudBees Core) on modern cloud platforms - Managed controller
• CloudBees CI (CloudBees Core) on modern cloud platforms - Operations Center
• CloudBees CI (CloudBees Core) on traditional platforms - Client controller
• CloudBees CI (CloudBees Core) on traditional platforms - Operations Center
• CloudBees Jenkins Platform - Client controller
• CloudBees Jenkins Platform - Operations Center

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