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

Allow merge commits to be built from origin PRs

XMLWordPrintable

      There should be an option by which the normal suppression of Multibranch projects for origin PRs would be disabled, so you would get two projects:

      1. one building the head of the branch
      2. one building the speculative merge commit.

      There could also be an option to suppress the origin branch project when a PR is filed from the branch. This would cause the origin branch project to be deleted once the PR is filed. (It could be resurrected if the PR is closed but the branch not deleted.) This option would necessitate a new API in github-branch-source to filter branches.

          [JENKINS-33161] Allow merge commits to be built from origin PRs

          Manuel Recena Soto created issue -
          Manuel Recena Soto made changes -
          Description Original: There should be an option by which the normal suppression of branch projects for origin PRs would be disabled, so you would get two projects:

          # one building the head of the branch
          # one building the speculative merge commit.

          There could also be an option to suppress the origin branch project when a PR is filed from the branch. This would cause the origin branch project to be deleted once the PR is filed. (It could be resurrected if the PR is closed but the branch not deleted.) This option would necessitate a new API in {{github-branch-source}} to filter branches.           		New: There should be an option by which the normal suppression of branch projects for origin PRs would be disabled, so you would get two projects:

          # one building the head of the branch
          # one building the speculative merge commit.

          There could also be an option to suppress the _origin_ branch project when a PR is filed from the branch. This would cause the origin branch project to be deleted once the PR is filed. (It could be resurrected if the PR is closed but the branch not deleted.) This option would necessitate a new API in {{github-branch-source}} to filter branches.
          Jesse Glick made changes -
          Link New: This issue is related to JENKINS-33237 [ JENKINS-33237 ]
          Patrick Wolf made changes -
          Labels New: 2.0
          Jesse Glick made changes -
          Labels Original: 2.0 New: 2.0-planned
          Jesse Glick made changes -
          Labels Original: 2.0-planned New: 2.0

          Patrick Wolf added a comment -

          This should be as consistent as possible across all branch source plugins that work with PRs. Unless we want to track all of them separately.

          Patrick Wolf added a comment - This should be as consistent as possible across all branch source plugins that work with PRs. Unless we want to track all of them separately.

          Michael Neale added a comment -

          If in the happy case of the branch being update with the master when a pull request is opened, ideally a new build would not be triggered, instead it could just use the build previously done on the branch (but it could show up as a new build?? perhaps??).

          Michael Neale added a comment - If in the happy case of the branch being update with the master when a pull request is opened, ideally a new build would not be triggered, instead it could just use the build previously done on the branch (but it could show up as a new build?? perhaps??).
          James Dumay made changes -
          Labels Original: 2.0 New: 2.0 blueocean
          Michael Neale made changes -
          Priority Original: Minor [ 4 ] New: Major [ 3 ]

            jglick Jesse Glick
            recena Manuel Recena Soto
            Votes:
            12 Vote for this issue
            Watchers:
            26 Start watching this issue

              Created:
              Updated:
              Resolved: