Details
-
Improvement
-
Status: In Review (View Workflow)
-
Critical
-
Resolution: Unresolved
-
b06
-
-
Blue Ocean 1.1, Blue Ocean 1.2-beta1, Blue Ocean 1.2-beta2, Blue Ocean 1.4 - beta 3, Blue Ocean 1.5 - beta 2
-
1.14.0
Description
This improvement is on the Blue Ocean project roadmap. Check the roadmap page for updates.
Same pipeline as JENKINS-38337
stage "Stage 1"
stage ("Trigger jobs") {
parallel(
downstream1: {
build 'downstream1'
},
downstream2: {
build 'downstream2'
}
)
}
In the logs, we see things like Starting building: downstream2 #3, however unlike the classic console, this is not a link, so you can't browse to the other build.
Out of scope:
When the "don't wait" mode is used, there is no link to the resultant downstream job, so no need to link it back ( ie build job: 'downer', wait: false)
Attachments
Issue Links
- is duplicated by
-
JENKINS-44730 pipeline build command does not display other job in blueocean UI
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
JENKINS-44685 Make links to builds triggered with the 'build' step clickable
-
- Resolved
-
-
-
- Closed
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- is related to
-
-
- Closed
-
- relates to
-
-
- Resolved
-
-
-
- Resolved
-
- links to
- mentioned in
-
Page Loading...
Activity
Luis Roalter
added a comment - Sometimes it works. but not always. For some reasons the NodeDownstreamBuildAction is missing when using the api /blue/rest/organizations/jenkins/pipelines/
When going closer into /blue/rest/organizations/jenkins/pipelines/<project>/runs/x/nodes/y/ the information is missing in this endpoint too.
Funny fact, I've debugged it with the Script console by replaying the code from https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-pipeline-api-impl/src/main/java/io/jenkins/blueocean/listeners/DownstreamJobListener.java. This works and all the triggered builds are there.
But for me it's too complex to dig into the blue-ocean rest and debug there.
Any suggestion from anyone how to debug it?
Luis Roalter
added a comment - Sometimes it works. but not always. For some reasons the NodeDownstreamBuildAction is missing when using the api /blue/rest/organizations/jenkins/pipelines/
When going closer into /blue/rest/organizations/jenkins/pipelines/<project>/runs/x/nodes/y/ the information is missing in this endpoint too.
Funny fact, I've debugged it with the Script console by replaying the code from https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-pipeline-api-impl/src/main/java/io/jenkins/blueocean/listeners/DownstreamJobListener.java . This works and all the triggered builds are there.
But for me it's too complex to dig into the blue-ocean rest and debug there.
Any suggestion from anyone how to debug it? I've been looking into this as well. What I've found so far:
- The downstream runs have an associated BuildUpstreamNodeAction contributed by the build step.
- The BuildUpstreamNodeAction action has an upstreamNodeId pointing back to the build step that triggered the downstream run.
- This DownstreamJobListener adds a NodeDownstreamBuildAction to the node pointed to by the upstreamNodeId.
- This upstreamNodeId doesn't match the id of the node typically selected when viewing the Blue Ocean pipeline graph (that node is typically a stage or parallel branch node)
- There's code in PipelineNodeGraphVisitor.java that accumulates actions from nodes within a branch or stage and then adds them to the node for that branch or stage. I believe this is the source of the issue.
Stuart Rowe
added a comment - - edited I've been looking into this as well. What I've found so far:
The downstream runs have an associated BuildUpstreamNodeAction contributed by the build step.
The BuildUpstreamNodeAction action has an upstreamNodeId pointing back to the build step that triggered the downstream run.
This DownstreamJobListener adds a NodeDownstreamBuildAction to the node pointed to by the upstreamNodeId.
This upstreamNodeId doesn't match the id of the node typically selected when viewing the Blue Ocean pipeline graph (that node is typically a stage or parallel branch node)
There's code in PipelineNodeGraphVisitor.java that accumulates actions from nodes within a branch or stage and then adds them to the node for that branch or stage. I believe this is the source of the issue.
Roi BB
added a comment - Hi, any estimation when the fix will be released? Tnx.
I have raised a bug for this JENKINS-60995
as it is a regression of existing functionality