-
Improvement
-
Resolution: Unresolved
-
Minor
-
workflow-1.13
In the current flow graph it's impossible to understand, which labels have been actually required by the node() call. Such info would be useful for the build analysis.
In WorkspaceActionImpl we get all labels of the build, so this info is not relevant.
- is related to
-
JENKINS-32225 Workflow's ExecutorStep should support searching of the node
-
- Open
-
-
JENKINS-31582 Log / document the plugin usage in the flow nodes
-
- Resolved
-
- relates to
-
JENKINS-52394 api/json?depth=2 - Duration not available
-
- Closed
-
The summary of the issue is clear enough, but the description is mangled. WorkspaceAction.getLabels() is clearly documented to be the labels of the node owning the workspace, and the implementation matches the documentation and will not be changed.
What you are asking for is access to the ExecutorStep.getLabel()—the requested label expression. This is not really the responsibility of WorkspaceAction, which is used in a couple of other places, of which WorkspaceStepExecution has no associated label expression, and CpsScmFlowDefinition could (but currently does not, and anyway that information would be statically available in the job definition).
What might be more generally useful is to record the step configuration as an action in the StepNode.
JENKINS-31582requests that the plugins associated with the step be recorded, but we might as well just record the whole configuration, since it is typically not very large, and the plugin information can be reconstructed from that.