`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/CANfRfr3DSDy%3D8VcChOL4xQzZYCrD9aTOYkG0%2B2SaZ_ft%3DbwkdA%40mail.gmail.com.
