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

Control of BB PR behavior on multi-branch pipelines

XMLWordPrintable

      For any multi-branch pipeline we would like to be able to control:

      • Enable/Disable building pull requests.
      • Enable/Disable building pull requests originating from forked repositories

      This is in support of the Blue Ocean story JENKINS-35790.

          [JENKINS-35991] Control of BB PR behavior on multi-branch pipelines

          James Dumay created issue -
          James Dumay made changes -
          Epic Link New: JENKINS-35386 [ 171179 ]
          James Dumay made changes -
          Link New: This issue blocks JENKINS-35790 [ JENKINS-35790 ]
          James Dumay made changes -
          Rank New: Ranked higher

          Jesse Glick added a comment -

          github-branch-source issue is JENKINS-33161.

          Jesse Glick added a comment - github-branch-source issue is JENKINS-33161 .
          Jesse Glick made changes -
          Component/s Original: github-branch-source-plugin [ 20858 ]
          Jesse Glick made changes -
          Link New: This issue is related to JENKINS-33161 [ JENKINS-33161 ]

          James Dumay added a comment -

          jglick does this mean this issue is defunct?

          James Dumay added a comment - jglick does this mean this issue is defunct?

          Jesse Glick added a comment -

          No, just that you filed it against two plugins, and there was already an issue open for one of them.

          Jesse Glick added a comment - No, just that you filed it against two plugins, and there was already an issue open for one of them.
          Jesse Glick made changes -
          Summary Original: We would like control how pull requests are built on multi-branch pipelines New: Control of BB PR behavior on multi-branch pipelines

            amuniz Antonio Muñiz
            jamesdumay James Dumay
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: