-
Bug
-
Resolution: Fixed
-
Major
-
Development
I configured the java project for the automated build and initiated the build. The result was awesome successfully generated the artifact. I did change in my program and SCM initiated the build which resulted in below error.
I thought it could be problem with the configuration so wanted to delete the project and configure again. Jenkins in not allowing me to delete the project and i am getting same error.
I configured other project again by renaming. First build works find but after i am done with the changes and commit to SVN, SCM initiates build which is fine but it again fails with below error. Could you please help or let me know what can i do to fix it?
Interesting observation:
1. I am getting this error on latest version of Jenkins installed on my local i.e 1.612.
2. Same configuration works properly on Jenkins 1.59x. I am not sure what could be a cause only difference between two version is that i have tried installing Subversion Feature on 1.6 on my local but i ended up with below error hence i am confident enough to install this plugin in production as its failing on my local.
java.nio.file.FileSystemException: <http://localhost:8080/job/Dev_75_YTFeature01/ws/src>: The process cannot access the file because it is being used by another process.
at sun.nio.fs.WindowsException.translateToIOException(Unknown Source)
at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)
at sun.nio.fs.AbstractFileSystemProvider.delete(Unknown Source)
at java.nio.file.Files.delete(Unknown Source)
at sun.reflect.GeneratedMethodAccessor903.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at hudson.Util.deleteFile(Util.java:247)
at hudson.Util.deleteRecursive(Util.java:310)
at hudson.Util.deleteContentsRecursive(Util.java:212)
at hudson.scm.SubversionReleaseSCM$CheckOutTask.invoke(SubversionReleaseSCM.java:479)
at hudson.scm.SubversionReleaseSCM$CheckOutTask.invoke(SubversionReleaseSCM.java:414)
at hudson.FilePath.act(FilePath.java:991)
at hudson.FilePath.act(FilePath.java:969)
at hudson.scm.SubversionReleaseSCM.checkout(SubversionReleaseSCM.java:407)
at hudson.scm.SubversionReleaseSCM.checkout(SubversionReleaseSCM.java:356)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1276)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:610)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:532)
at hudson.model.Run.execute(Run.java:1744)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:374)
[JENKINS-28299] Build Started by an SCM Change is Failing
Bob Balli
added a comment - Build is Triggered through poll SCM. I am using SVN 1.7. Bob Balli
added a comment - Hello All,
I have resolved this issue.
Problem: This was an issue with Job Configuration. I configured the job with fairly long name in order to follow conventions and recognize the job in our environment.
Resolution: I renamed the job to less than 20 Characters and build executed Successfully without any issue.
Conclusion: We need to be careful while deciding the name for the jobs on Jenkins. It looks like if you exceed certain limit for the job name it will tend to fail. I am curious to know the limit Character for the job name in Jenkins if anyone knows.
Thanks for your help and hope this helps to users facing similar issue.
Bob Balli
added a comment - Hello All,
I have resolved this issue.
Problem : This was an issue with Job Configuration. I configured the job with fairly long name in order to follow conventions and recognize the job in our environment.
Resolution : I renamed the job to less than 20 Characters and build executed Successfully without any issue.
Conclusion : We need to be careful while deciding the name for the jobs on Jenkins. It looks like if you exceed certain limit for the job name it will tend to fail. I am curious to know the limit Character for the job name in Jenkins if anyone knows.
Thanks for your help and hope this helps to users facing similar issue. 
Please find out which process has a file handle open unexpectedly.
Please provide more information about your setup, e.g. the kind of SCM used.
https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue