Simon your suspicion was correct! Thank you! After downgrading several plugins, I was able to isolate the issue with the EnvInject Plugin <https://wiki.jenkins.io/display/JENKINS/EnvInject+Plugin>v2.1.5 This version of the plugin seems to inject 'dontKillMe' as the BUILD_ID for a build. This behavior is not present in EnvInject Plugin v2.13 So, I have now settled to v2.1.3 as the latest version of the plugin to install.
Best regards Ioannis On Wednesday, January 17, 2018 at 2:07:58 PM UTC-5, Simon Richter wrote: > > Hi, > > Am 17.01.2018 um 17:25 schrieb Ioannis Moutsatsos: > > > The BUILD_ID (which up to this point was equal to BUILD_NUMBER) is now > > set to 'dontKillMe' > > I dimly remember that this is a way to tell the cleanup code that kills > all processes after the build has finished to ignore certain processes. > > On Windows with Visual Studio, this is often needed because pdbserv.exe > is shared between builds, so if the build that initially started it > finishes, all the other builds that are still running will fail. > > Not sure why this is set now, but I'd suspect a plugin rather than > Jenkins core here. > > Simon > > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/c378e0d5-9d7c-4bf7-938f-ac1a9ecf7f74%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
