|
||||||||
|
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 |
||||||||
- [JIRA] (JENKINS-15829) hg share always... [email protected] (JIRA)
- [JIRA] (JENKINS-15829) hg share a... [email protected] (JIRA)
- [JIRA] (JENKINS-15829) hg share a... [email protected] (JIRA)
- [JIRA] (JENKINS-15829) hg share a... [email protected] (JIRA)
- [JIRA] (JENKINS-15829) hg share a... [email protected] (JIRA)
- [JIRA] (JENKINS-15829) hg share a... [email protected] (JIRA)
- [JIRA] (JENKINS-15829) hg share a... [email protected] (JIRA)
- [JIRA] (JENKINS-15829) hg share a... [email protected] (JIRA)

I think this is because the mercurial caches on the slave don't have a default path to push and pull from.
Igor: could you, on your slave, create a .hg/hgrc file in the /app/agora/hudsonslave/hgcache/D38534FF4534AE3232A1AB292D5BA54825AE752B-AgoraLight that contains the following information:
Does the working copy get recreated every time then, after you remove your workaround?