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

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

    • 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

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

          R. Tyler Croy created issue -

          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
          Michael Neale made changes -
          Priority Original: Minor [ 4 ] New: Major [ 3 ]
          Michael Neale made changes -
          Assignee New: Vivek Pandey [ vivek ]
          Michael Neale made changes -
          Epic Link New: JENKINS-35759 [ 171771 ]
          Michael Neale made changes -
          Sprint New: Blue Ocean 1.4 - beta 3 [ 416 ]
          Michael Neale made changes -
          Description Original: When creating a "New Pipeline" from within Blue Ocean for an existing repository which contains a {{Jenkinsfile}} ([this one to be precise|https://github.com/CodeValet/canary]), 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 :(
          New: When creating a "New Pipeline" from within Blue Ocean for an existing repository which contains a {{Jenkinsfile}} ([this one to be precise|https://github.com/CodeValet/canary]), 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
          Michael Neale made changes -
          Priority Original: Major [ 3 ] New: Critical [ 2 ]
          R. Tyler Croy made changes -
          Attachment New: ideal-traits.png [ 40725 ]

          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

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

              Created:
              Updated:
              Resolved: