• Type: Bug
• Resolution: Duplicate
• Priority: Minor
• Component/s: blueocean-display-url-plugin
• Labels:

  None
• Environment:

  Jenkins 2.89.2 (Docker)
  All plugins up-to-date

[JENKINS-48849] No downstream links in Blue Ocean with Bitbucket Multibranch

Simon Schneider created issue - 2018-01-08 20:43

Simon Schneider made changes - 2018-01-08 20:44

Description

Original: Steps to reproduce:  * Use a BitBucket Team/Project (multibranch)  * Have a Job with a Jenkinsfile  * Use a valid build step in the Jenkinfile e.g. like {{build 'GROUP/repository/branch'}}{{}}  * Run the job  * Open the job details in Blue Ocean view  * Try to open the downstream built job using a link which doesn't exist In the step details (console) it should say something like   {{Scheduling project: GROUP » repository » branch }}{{[|http://10.16.34.52:8080/blue/organizations/jenkins/CATS%20CI/detail/CATS%20CI/28/pipeline/191#step-209-log-2]Starting building: GROUP » repository » branch #7}} Both of them are working links to the GROUP/repository/branch job (the second one linking to the exact build) in the plain old Jenkins view, but none of them are links in the Blue Ocean view.

New: Steps to reproduce:  * Use a BitBucket Team/Project (multibranch)  * Have a Job with a Jenkinsfile  * Use a valid build step in the Jenkinfile e.g. like {{build 'GROUP/repository/branch'}}  * Run the job  * Open the job details in Blue Ocean view  * Try to open the downstream built job using a link which doesn't exist In the step details (console) it should say something like {{Scheduling project: CATS » cats-endpoint-gigaspaces » develop}} {{Starting building: CATS » cats-endpoint-gigaspaces » develop #7}} Both of them are working links to the GROUP/repository/branch job (the second one linking to the exact build) in the plain old Jenkins view, but none of them are links in the Blue Ocean view.

Simon Schneider made changes - 2018-01-08 20:45

Description

Original: Steps to reproduce:  * Use a BitBucket Team/Project (multibranch)  * Have a Job with a Jenkinsfile  * Use a valid build step in the Jenkinfile e.g. like {{build 'GROUP/repository/branch'}}  * Run the job  * Open the job details in Blue Ocean view  * Try to open the downstream built job using a link which doesn't exist In the step details (console) it should say something like {{Scheduling project: CATS » cats-endpoint-gigaspaces » develop}} {{Starting building: CATS » cats-endpoint-gigaspaces » develop #7}} Both of them are working links to the GROUP/repository/branch job (the second one linking to the exact build) in the plain old Jenkins view, but none of them are links in the Blue Ocean view.

New: Steps to reproduce:  * Use a BitBucket Team/Project (multibranch)  * Have a Job with a Jenkinsfile  * Use a valid build step in the Jenkinfile e.g. like {{build 'GROUP/repository/branch'}}  * Run the job  * Open the job details in Blue Ocean view  * Try to open the downstream built job using a link which doesn't exist In the step details (console) it should say something like {{Scheduling project: GROUP »repository » branch}} {{Starting building: GROUP » repository » branch #7}} Both of them are working links to the GROUP/repository/branch job (the second one linking to the exact build) in the plain old Jenkins view, but none of them are links in the Blue Ocean view.

Collapse comment: James Dumay added a comment - 2018-02-19 00:46

James Dumay added a comment - 2018-02-19 00:46

Duplicate of JENKINS-38339 which is in progress.

Expand comment: James Dumay added a comment - 2018-02-19 00:46

James Dumay added a comment - 2018-02-19 00:46 Duplicate of JENKINS-38339 which is in progress.

James Dumay made changes - 2018-02-19 00:46

Link

New: This issue duplicates JENKINS-38339 [ JENKINS-38339 ]

James Dumay made changes - 2018-02-19 00:46

Resolution		New: Duplicate [ 3 ]
Status	Original: Open [ 1 ]	New: Resolved [ 5 ]

Jenn Briden made changes - 2018-07-06 21:08

Status

Original: Resolved [ 5 ]

New: Closed [ 6 ]