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

Multibranch pipeline cannot exclude/remove perforce streams

    Details

    • Similar Issues:

      Description

      Seems like there is no way to exclude streams from the 'build strategies'. I had originally set up my multibranch pipeline job to build all streams. We now want to exclude some specifically named streams but this doesn't seem to be possible by using a regular expression for a named branch and choosing 'None Strategies Match'. See screenshot.

       

      After adding this to my multibranch config, the stream 'OBSOLETE - int_2.0.2' still shows up as a job and still attempts to run. The multibranch config is setup to discard old items.

      A system configured as above should remove the job from list of jobs in the multibranch pipeline.

        Attachments

          Issue Links

            Activity

            Hide
            p4karl Karl Wirth added a comment -

            Hi Barrett Lowe - Thanks for highlighting this. I'll make sure the developers see this.

            The following job exists to solve the general problem - JENKINS-58346  (Add exclude filter multibranch option)

            The workaround mentioned are:

            • Use Perforce protections to hide *-Private from Jenkins user.
            • Have multiple inclussionary expressions. For example '(.[1-9].*Rel)|(.[1-9].QA)|(.[1-9].*Dev)

            The protections option should work but I have not tested the inclusionary method with streams. I also think that if you delete the Jenkinsfile in the stream then at minimum it wont build and possibly it wont be added to the pipeline.

            You can find more on Perforce protections in:

                 https://www.perforce.com/manuals/p4sag/Content/P4SAG/protections.set.html

             

            Show
            p4karl Karl Wirth added a comment - Hi Barrett Lowe - Thanks for highlighting this. I'll make sure the developers see this. The following job exists to solve the general problem - JENKINS-58346   (Add exclude filter multibranch option) The workaround mentioned are: Use Perforce protections to hide *-Private from Jenkins user. Have multiple inclussionary expressions. For example '(. [1-9] .*Rel)|(. [1-9] . QA)|(. [1-9] .*Dev) The protections option should work but I have not tested the inclusionary method with streams. I also think that if you delete the Jenkinsfile in the stream then at minimum it wont build and possibly it wont be added to the pipeline. You can find more on Perforce protections in:      https://www.perforce.com/manuals/p4sag/Content/P4SAG/protections.set.html  

              People

              • Assignee:
                Unassigned
                Reporter:
                belowe Barrett Lowe
              • Votes:
                1 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: