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

"New Pipeline" from within Blue Ocean cannot Discover Pull Requests

XMLWordPrintable

    • Blue Ocean 1.4 - beta 3

      When creating a "New Pipeline" from within Blue Ocean for an existing repository which contains a Jenkinsfile (this one to be precise), the Multibranch Pipeline is not created with the appropriate "DIscover Pull Requests" traits.

      This means that Pipelines created from Blue Ocean will never have their Pull Requests view work

       

      It should build forked PRs and origin PRs as as PRs

        1. ideal-traits.png
          ideal-traits.png
          22 kB
        2. Selection_299.png
          Selection_299.png
          18 kB

          [JENKINS-48620] "New Pipeline" from within Blue Ocean cannot Discover Pull Requests

          Michael Neale added a comment -

          hey jamesdumay you have tried this from time to time, are you abel to clarify this is a regression? 

          It is likely a newer version of something (like github branch source) changed its default

          Michael Neale added a comment - hey jamesdumay you have tried this from time to time, are you abel to clarify this is a regression?  It is likely a newer version of something (like github branch source) changed its default

          R. Tyler Croy added a comment -

          michaelneale, attached an image with what I would consider the "ideal" traits for a GitHub-based Multibranch Pipeline

          R. Tyler Croy added a comment - michaelneale , attached an image with what I would consider the "ideal" traits for a GitHub-based Multibranch Pipeline

          Michael Neale added a comment -

          raising priority as this seems to be a regression in behavior. Likely just need to add a trait

          Michael Neale added a comment - raising priority as this seems to be a regression in behavior. Likely just need to add a trait

          Michael Neale added a comment -

          I do not suggest merge with target when building the PR as a default, if it causes rebuilds every time the target branch is changed 

          Michael Neale added a comment - I do not suggest merge with target when building the PR as a default, if it causes rebuilds every time the target branch is changed 

          R. Tyler Croy added a comment -

          I do not suggest merge with target when building the PR as a default, if it causes rebuilds every time the target branch is changed

          I understand this concern, but without this change the commit status on the Pull Request will be invalid if any changes are merged to the target branch between when the Pull Request was opened and when it might eventually be merged.

          R. Tyler Croy added a comment - I do not suggest merge with target when building the PR as a default, if it causes rebuilds every time the target branch is changed I understand this concern, but without this change the commit status on the Pull Request will be invalid if any changes are merged to the target branch between when the Pull Request was opened and when it might eventually be merged.

          James Dumay added a comment -

          kshultz this would be a good candidate for some exploratory testing I think

          James Dumay added a comment - kshultz this would be a good candidate for some exploratory testing I think

            jamesdumay James Dumay
            rtyler R. Tyler Croy
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: