Status: In Review (View Workflow)
Blue ocean 1.17.0
I have encountered an issue that severely limits the usability of the BlueOcean plugin when used with downstream jobs.
When triggering a downstream job BlueOcean normally displays the following section with a link to the downstream job, as introduced in JENKINS-38339
However, after upgrading to BlueOcean 1.17 this behaviour seems to have regressed:
There are a lot of comments on the original ticket JENKINS-38339 listing the same issue.
I am aware that this was once an issue for declarative pipelines and fixed as part of https://github.com/jenkinsci/blueocean-plugin/pull/1918/files
But I am running legacy groovy pipeline.
It is important to note that this does not always happen: sometimes a run will show the link, then when the exact same run is re-ran again it fails to show.
I have found this issue with both sequential and parallel pipelines where jobs are kicked off.
JENKINS-66367 pipeline-build-step-plugin: "triggeredBy UpstreamCause" when condition in declarative pipeline is broken
- links to
vlatombe allan_burdajewicz any idea if this is going to be progressed? Is there anything I can do to help expedite a fix here? Thanks
Hello, any updates on this issue? We are still seeing this in our builds a few years later.
I guess that now that Blue Ocean is deprecated, it's hard that this issue gains traction. And yes, it also happens for me yet.
Still present in Blue Ocean 1.25.2, Jenkins 2.319.1