Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-55268

Multibranch pipelines cannot have different "Named Branch" configurations when created by the organization plugin


      I am utilizing the Jenkins Organization Job to scan and track Jenkinsfiles across a number of different github repositories, which trigger builds using a github webhook configuration that notifies jenkins.

      Our repositories Jenkinsfiles are managed by the developers. Some of them want their pipeline to build on pushes to only the "master" branch. Others want them to build on pushes to the "develop", "staging", and "master" branches.

      However, the "Named Branch" build strategy setting is only configurable at the Organization job level, and is passed down to all jobs created by it. This prevent developers from configuring their jobs independently.

            Unassigned Unassigned
            mjf Maxwell Flanders
            1 Vote for this issue
            2 Start watching this issue