You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the Maven build is part of a Jenkins job and a timeout occurs, no report is written.
Having the report could help to understand why the built lasted for so long.
It would be great if the extension could try to write the information already available, even though the JVM is forcibly shutting down.
This probably means relying on java.lang.Runtime.addShutdownHook(Thread), i.e. this is on a best effort basis.
In case the build is successful, then there is no need to write the same report twice.
The text was updated successfully, but these errors were encountered:
When the Maven build is part of a Jenkins job and a timeout occurs, no report is written.
Having the report could help to understand why the built lasted for so long.
It would be great if the extension could try to write the information already available, even though the JVM is forcibly shutting down.
This probably means relying on
java.lang.Runtime.addShutdownHook(Thread)
, i.e. this is on a best effort basis.In case the build is successful, then there is no need to write the same report twice.
The text was updated successfully, but these errors were encountered: