First stage is always showing master as the node where the stage was executed.
Reproducible with this script (and having a node tagged as my-tag):
Antonio Muñiz made changes -
|Field||Original Value||New Value|
|Assignee||Antonio Muñiz [ amuniz ]|
|Assignee||Sam Van Oort [ svanoort ]|
|Status||Open [ 1 ]||In Progress [ 3 ]|
[ [~marcus_phi] We're well aware that the existing implementation does not handle every case correctly and you find this frustrating. It's being addressed by a completely new set of pipeline APIs and a full rewrite of the pipeline stage view internals to use them. This will yield the full and correct set of node labels for each stage, as well as providing future support for parallel handling in JENKINS-33185 (and use of block-scoped stages).
This work is encapsulated in https://issues.jenkins-ci.org/browse/JENKINS-34038
This depends on a new set of pipeline graph analysis APIs I am writing in https://github.com/jenkinsci/workflow-api-plugin/pull/2/files (1800 lines, and counting).
If you'd like to see the fix sooner than I can deliver it when working full-time on this problem -- well, the code is open source. I'd certainly welcome your assistance with the aforementioned PR or a skeletal visitor implementation that collects this information (consuming the new APIs). ]
R. Tyler Croy made changes -
|Workflow||JNJira [ 169188 ]||JNJira + In-Review [ 185694 ]|
|Status||In Progress [ 3 ]||Resolved [ 5 ]|
|Resolution||Done [ 10000 ]|
CloudBees Inc. made changes -
|Remote Link||This issue links to "CloudBees Internal OSS-634 (Web Link)" [ 18854 ]|