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

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

    XMLWordPrintable

Details

    • Blue Ocean 1.4 - beta 3

    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

          is duplicated by

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-46439 Github and Bitbucket should "Discover pull requests from origin" by default

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved
          links to

          Web Link PR-1599

          mentioned in

          Page Loading...

          Activity

            Ascending order - Click to sort in descending order
            michaelneale 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

            michaelneale 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
            rtyler R. Tyler Croy added a comment -

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

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

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

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

            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 
            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.

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

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

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

            People

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

              Dates

                Created:
                Updated:
                Resolved: