Hello, I wonder what's the reason for the JUnit plugin to define <https://github.com/jerrinot/junit-plugin/blob/9482f6b552c2067b8474e4a45dc3932f4cf1834d/src/main/java/hudson/tasks/junit/XMLEntityResolver.java#L52-L52> a new global XML Parser Configurator? I believe the XMLEntityResolver is only useful for the junit plugin itself - when it's parsing TestNG output. Other parts of Jenkins do not benefit from this extension and I don't understand why the resolver is registered globally.
I realized this is causing performance issues: The JUnit plugin initiates a RPC to fetch parser configurators <https://github.com/jerrinot/jenkins/blob/96150d3a465f428b5fbc5d03c8cd00115f4749c9/core/src/main/java/hudson/util/io/ParserConfigurator.java#L81-L81> before parsing *each* test result XML file. Now image what happens when you have 1000's XML files to parse and a non-trivial network latency between a master Jenkins installation and slave agents. I had sent a PR to cache <https://github.com/jenkinsci/jenkins/pull/2806> the parser configurators and it was suggested to completely remove the global registration - here is a PR with a candidate fix. <https://github.com/jenkinsci/junit-plugin/pull/65> Can anyone have a look at the new PR <https://github.com/jenkinsci/junit-plugin/pull/65>? Cheers, Jaromir -- 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/8983ae85-7021-4e60-87b4-12d4bedee299%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
