|
||||||||
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
We are encountering a similar problem that I originally attributed to some kind of weird conflict between
Use private Maven repository
and
SCM / Subversion / Check-out Strategy / Always checkout a fresh copy
Not sure why a Maven repo entry local to the workspace would be locked before the code is even checked out. Maven shouldn't even be running and no process other than the Jenkins job which uses this workspace should be referencing a workspace private maven repo entry.
Environment:
Jenkins Server
Jenkins 1.517
Maven 3.4 (-Xmx1536m -XX:MaxPermSize=256m)
Java 1.7.0_15-b03 Oracle JVM 64-bit
Windows 2008 Server 64-bit