|
||||||||
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... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-15829) hg share a... willem.verstrae...@gmail.com (JIRA)
- [JIRA] (JENKINS-15829) hg share a... isan...@gmail.com (JIRA)
- [JIRA] (JENKINS-15829) hg share a... isan...@gmail.com (JIRA)
- [JIRA] (JENKINS-15829) hg share a... isan...@gmail.com (JIRA)
- [JIRA] (JENKINS-15829) hg share a... isan...@gmail.com (JIRA)
- [JIRA] (JENKINS-15829) hg share a... willem.verstrae...@gmail.com (JIRA)
- [JIRA] (JENKINS-15829) hg share a... jgl...@cloudbees.com (JIRA)
> what do you mean with the 'fake working copy' option
It's not an option - we just specifying Directory parameter of mercurial plugin as fake and not using this directory - we did to for having changes information on build's page.
It's not related to current bug, and we are using directory created by plugin now, since enabling Use Repository Sharing option.
> Also, are there any other builds (of other jobs) running between the first build on the slave and the second build ?
Nothing is running between first and second builds and I see the same behavior on linux, solaris and windows slaves - only master (on linux) is fine.