Job failing on workspace cleanup....file is open....

[Jeff]

Windows Server 2008 R2 x64

Apache Tomcat/7.0.25

Jenkins ver. 1.472

ERROR below I get a LOT.  What the heck is going on?  I'm losing hours trying to even make simple tweaks to my jobs and maven release settings because I can't get past this without explicitly restarting the application.  WHAT IS HOLDING ON TO THIS FILE?  If I wait some indeterminate time, it will eventually work, but there are no other jobs running and I want to force builds as I change settings....

Fixes?  Suggestions?  I am getting very frustrated!!  <sorry :(>

Started by user anonymous

Building in workspace C:\.jenkins\jobs\SharedUtil (trunk)\workspace

Cleaning local Directory .

java.io.IOException: Unable to delete C:\.jenkins\jobs\SharedUtil (trunk)\workspace\.\pom.xml

at hudson.Util.deleteFile(Util.java:237)

at hudson.Util.deleteRecursive(Util.java:287)

at hudson.Util.deleteContentsRecursive(Util.java:198)

at hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:72)

at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:144)

at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:789)

at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:770)

at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:753)

at hudson.FilePath.act(FilePath.java:842)

at hudson.FilePath.act(FilePath.java:824)

at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:743)

at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:685)

at hudson.model.AbstractProject.checkout(AbstractProject.java:1248)

at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:589)

at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)

at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:494)

at hudson.model.Run.execute(Run.java:1488)

at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477)

at hudson.model.ResourceController.execute(ResourceController.java:88)

at hudson.model.Executor.run(Executor.java:236)

Skipping sonar analysis due to bad build status FAILURE

Notifying upstream projects of job completion

Finished: FAILURE

--

Jeff Vincent
preda...@gmail.com
See my LinkedIn profile at:
http://www.linkedin.com/in/rjeffreyvincent

I ♥ DropBox !! 

[Slide]

It looks like you are running into something similar to this

https://issues.jenkins-ci.org/browse/JENKINS-500

It says it is resolved, but perhaps there was a regression?

slide

--
Website: http://earl-of-code.com

[Jan Seidel]

Hi Jeff,

maybe some process called by the build is hanging.
Install Lockhunter, WhoLockMe or Systernal's Process Explorer on the Jenkins server, log on and check with one of these tools which process/handle is blocking.
I did experience similar with folders until I discovered that an open command box spawned by a job had the working dir set to the folder which had the problem. This can also happen from a machine remoting to a folder or file.
Other scenrio I had was that the SVN/CVS process did not free allocated resources due to tremndous large checkouts (upto 80 Gigs) and sticking to the last access file/folder before "crashing".

I would have been searching quite a while without one of these tools.
The reason is sometimes embarassing simple, not locatable at first glance and showing a great effect.

Take care
Jan

[Jeff]

I was off last week and am still getting caught back up....  

 

All jobs do the following:

• Poll SVN for changes
• Check out a clean copy if a build is needed.
• run 'mvn clean install deploy'
• run post-build SONAR analysis.

the locked POM file fails the builds of all my maven jobs at some point.  I ran LockHunter and all it says is that tomcat7.exe has it open (two entries in the list).

I sort of suspected this since it is in the Java process of Tomcat/Jenkins that I thought was holding onto the file. 

I still suspect that the maven plugin or something else that analyzes the pom (dependency chain, up or down stream jobs, maven version analysis, etc.), but it is getting to be a real problem for me.  Any thoughts on narrowing this down?