I narrowed down the java.exe process that is holding the folder open. Here's the command:
"C:\Program Files\Java\jdk1.7.0_80\bin\java" -cp > c:\jenkins\maven35-agent.jar;C:\apache-maven-3.5.0\boot\plexus-classworlds-2.5.2.jar;C:\apache-maven-3.5.0/conf/logging > > jenkins.maven3.agent.Maven35Main C:\apache-maven-3.5.0 C:\jenkins\slave.jar > c:\jenkins\maven35-interceptor.jar > c:\jenkins\maven3-interceptor-commons.jar 1942 Interestingly enough, Jenkins runs under Java 1.8. The maven job is using 1.7. Not sure if this is relevant. Anyway, does anyone know what triggers the above command? On Wednesday, June 21, 2017 at 3:19:33 PM UTC-4, t3knoid wrote: > > I have another job that uses the same option and is working just fine. The > one that is failing is a Java application using Maven to build. > > On Wednesday, June 21, 2017 at 1:57:36 PM UTC-4, t3knoid wrote: >> >> I recently updated to Jenkins 2.65 and some of my plugins. Now every time >> I try to build a job that has been working all along, the job fails when >> trying to clean the workspace. It only happens after every other job. I can >> get around the issue by restarting the slave service (Windows). This is >> obviously not a solution. How can I go about checking what is causing the >> lock on the folder? >> > -- 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/b80620f4-9ae1-42c4-bdaf-8d4cd517fd00%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
