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

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

    Details

    • Epic Link:
    • Sprint:
      Blue Ocean 1.4 - beta 3
    • Similar Issues:

      Description

      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

        Attachments

          Issue Links

            Activity

            Hide
            michaelneale Michael Neale added a comment -

            hey James Dumay 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

            Show
            michaelneale Michael Neale added a comment - hey James Dumay 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
            Hide
            rtyler R. Tyler Croy added a comment -

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

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

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

            Show
            michaelneale Michael Neale added a comment - raising priority as this seems to be a regression in behavior. Likely just need to add a trait
            Hide
            michaelneale 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 

            Show
            michaelneale 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 
            Hide
            rtyler 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.

            Show
            rtyler 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.
            Hide
            jamesdumay James Dumay added a comment -

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

            Show
            jamesdumay James Dumay added a comment - Karl Shultz this would be a good candidate for some exploratory testing I think

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: