[JIRA] (JENKINS-14699) hg clone adding "@2" to end of clone destination path

Tue, 19 Feb 2013 09:50:57 -0800

mat007 commented on Bug JENKINS-14699

We're using SVN and very regularly (e.g. once a week) we experience this issue.
Sometimes it even goes to @3 or @4 before we notice.
The thing is the workspace does exist, it just seems for some reason something decides to switch to the @2 workspace.
For instance one build starts with :

Started by an SCM change
Building remotely on Slave-2 in workspace E:\workspace\<PROJECT>
Updating http://svn.<DOMAIN>/<PATH>/<PROJECT>/trunk at revision '2013-02-19T15:26:09.965 +0100'

and the next one :

Started by an SCM change
Building remotely on Slave-2 in workspace E:\workspace\<PROJECT>@2
Checking out a fresh workspace because E:\workspace\<PROJECT>@2\trunk doesn't exist
Cleaning local Directory trunk
Checking out http://svn.<DOMAIN>/<PATH>/<PROJECT>/trunk at revision '2013-02-19T17:11:09.863 +0100'


We are using matrix builds with a few slaves started via jnlp, all on windows.

Any clue how we could help debug this ?



It is quite inconvenient as some of our projects take up to 70GB disk space and duplicating them fills up the disk pretty quickly.
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Reply via email to