We have a build step that runs a TestNG suite, with the command looking something like this:
java -jar -Done-jar.main.class=org.testng.TestNG the-jar.jar TheTest.xml If the process is aborted in any way (manual intervention, Jenkins build timeout, etc.) OR if the slave loses connection from the master long enough to fail the build, then there is a Java process left behind. This is particularly damaging to us, as we load a DLL in the Java process, locking the file handle. If we attempt the job again, we cannot load the DLL again, meaning that all future builds will fail without manual intervention (killing the leftover process manually). Has anyone encountered a similar problem/have a workaround/have the ability to escalate a bug, if necessary? -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/11c2dda4-ed02-43ba-966c-fddc7c8766f9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
