> What do you need a stage name for? Just track the `FlowNode.id`. The output is intended for humans, to whom FlowNode.id will be meaningless, and it is also prone to change, meaning it can't reliably be used to track performance of a stage over time.
On Friday, July 9, 2021 at 3:03:47 PM UTC-4 Jesse Glick wrote: > On Fri, Jul 9, 2021 at 12:53 PM Gregory Paciga <[email protected]> wrote: > >> for a "stage" Step, the FlowNode (a StepStartNode) doesn't yet have a >> LabelAction associated with it. >> > > Yes, you need to wait for the next step to run, or at least some time. > Same as for `GraphListener.Synchronous`, and (depending on luck) regular > `GraphListener`. > > I could compromise by using StepListener to get the start of a step and >> GraphListener to get the end of it, but only if the stage name can be found. >> > > What do you need a stage name for? Just track the `FlowNode.id`. > > Given the FlowNode from GraphListener, is there a way to get to the >> StepContext? >> > > No. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/72a36f8c-057e-4674-b461-f1f466429515n%40googlegroups.com.
