[JIRA] (JENKINS-15829) hg share always recreating working copy on slave (on master it's working fine)

2012-12-10 Thread jgl...@cloudbees.com (JIRA)














































Jesse Glick
 commented on  JENKINS-15829


hg share always recreating working copy on slave (on master its working fine)















It is true that when caching is enabled, slave repos have no paths.default: changeset bundles are transferred over the Jenkins remoting channel instead.



























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 recreating working copy on slave (on master it's working fine)

2012-12-08 Thread willem.verstrae...@gmail.com (JIRA)














































Willem Verstraeten
 commented on  JENKINS-15829


hg share always recreating working copy on slave (on master its working fine)















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:

[paths]
default=__URL_OF_YOUR_MASTER_REPO__



Does the working copy get recreated every time then, after you remove your workaround?



























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 recreating working copy on slave (on master it's working fine)

2012-11-26 Thread isan...@gmail.com (JIRA)














































Igor Kostenko
 commented on  JENKINS-15829


hg share always recreating working copy on slave (on master its working fine)















If somebody else have the same issue, here the workaround which I'm using on slaves:
In Source Code Management / Mercurial / Advanced / Subdirectory I'm specifying directory fake and adding at the beginning of build
Unix:

if [ -d MyRepo ]; then
hg -R MyRepo update
else
hg --config extensions.share= share fake MyRepo
fi

Windows:

if exist MyRepo\nul (hg -R MyRepo update) else (hg --config extensions.share= share fake MyRepo)




























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 recreating working copy on slave (on master it's working fine)

2012-11-15 Thread willem.verstrae...@gmail.com (JIRA)














































Willem Verstraeten
 commented on  JENKINS-15829


hg share always recreating working copy on slave (on master its working fine)















Igor: what do you mean with the 'fake working copy' option? I can find a 'custom workspace' option, is that it ?

Also, are there any other builds (of other jobs) running between the first build on the slave and the second build ?



























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 recreating working copy on slave (on master it's working fine)

2012-11-15 Thread isan...@gmail.com (JIRA)














































Igor Kostenko
 commented on  JENKINS-15829


hg share always recreating working copy on slave (on master its working fine)















 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



























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 recreating working copy on slave (on master it's working fine)

2012-11-15 Thread isan...@gmail.com (JIRA)












































 
Igor Kostenko
 edited a comment on  JENKINS-15829


hg share always recreating working copy on slave (on master its working fine)
















 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.



























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 recreating working copy on slave (on master it's working fine)

2012-11-15 Thread isan...@gmail.com (JIRA)












































 
Igor Kostenko
 edited a comment on  JENKINS-15829


hg share always recreating working copy on slave (on master its working fine)
















 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 it 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.



























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 recreating working copy on slave (on master it's working fine)

2012-11-14 Thread jgl...@cloudbees.com (JIRA)















































Jesse Glick
 assigned  JENKINS-15829 to Willem Verstraeten



hg share always recreating working copy on slave (on master its working fine)
















Afraid I do not know much about the share mode.





Change By:


Jesse Glick
(15/Nov/12 1:15 AM)




Assignee:


JesseGlick
WillemVerstraeten



























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