Got it. We're encouraging people to move towards pipeline, but we still have a lot of these Maven jobs in our environment (across multiple masters). I'll share this internally.
Collecting labels on the pipeline jobs has been a bit of a challenge, but what I've settled on is what you describe. I wait until the build is complete, and then I traverse the flow graph. We don't really need the data in real time, so it seems to work well enough. If you can suggest a different approach though, I'm open to improving it. Thanks! On Wednesday, September 4, 2019 at 8:54:37 AM UTC-7, Jesse Glick wrote: > > `maven-plugin` does weird things with nested jobs/builds. We advise > people to not use this plugin. > > You may want to test against `matrix-project`, which also does > something similar, though in that case each sub-build would in fact > have different executor labels. > > I am not sure what you tested for Pipeline but if you are trying to > collect executor labels, `RunListener` is not going to do what you > want, since a given Pipeline build might have run zero or more `node` > blocks. If you do not need this information in real time, I guess you > can wait for the whole build to complete, then traverse the flow graph > looking for `WorkspaceAction`. > -- 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/5951caf4-210f-4a05-93f1-ca3bd9c656c9%40googlegroups.com.
