-
Improvement
-
Resolution: Fixed
-
Critical
-
-
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
- is duplicated by
-
-
- Resolved
-
- links to
- mentioned in
-
Page Failed to load
[JENKINS-48620] "New Pipeline" from within Blue Ocean cannot Discover Pull Requests
| Priority | Original: Minor [ 4 ] | New: Major [ 3 ] |
| Assignee | New: Vivek Pandey [ vivek ] |
| Epic Link | New: JENKINS-35759 [ 171771 ] |
| Sprint | New: Blue Ocean 1.4 - beta 3 [ 416 ] |
| 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 |
| Priority | Original: Major [ 3 ] | New: Critical [ 2 ] |
| Attachment | New: ideal-traits.png [ 40725 ] |
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
| Status | Original: In Progress [ 3 ] | New: In Review [ 10005 ] |
| Assignee | Original: Vivek Pandey [ vivek ] | New: James Dumay [ jamesdumay ] |