[JIRA] [mercurial] (JENKINS-23571) Option to control repos cache path directory

2014-06-26 Thread jer...@bodycad.com (JIRA)














































Jerome Godbout
 commented on  JENKINS-23571


Option to control repos cache path directory















I agree for the slave, it would not be necessary. As for the workaround, if I was on Unix system I would have done that a long time ago, but sadly I'm stuck under Windows and symlink under Windows for different drives at boot is a mess. Which make me think, could have the path on the master configurable and fallback to the actual if path is not found. 



























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/d/optout.


[JIRA] [mercurial] (JENKINS-23571) Option to control repos cache path directory

2014-06-26 Thread jgl...@cloudbees.com (JIRA)














































Jesse Glick
 commented on  JENKINS-23571


Option to control repos cache path directory















Would be useful to have it be possible to configure the master cache location much as you do for master workspace locations. The workaround would be to use a symlink.

Not necessary for slaves, since the slave FS root (including workspaces, tools, HG caches, and so on) can just be tossed out and recreated at any time.



























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/d/optout.


[JIRA] [mercurial] (JENKINS-23571) Option to control repos cache path directory

2014-06-25 Thread jer...@bodycad.com (JIRA)














































Jerome Godbout
 created  JENKINS-23571


Option to control repos cache path directory















Issue Type:


Improvement



Affects Versions:


current



Assignee:


Jesse Glick



Components:


mercurial



Created:


25/Jun/14 1:15 PM



Description:


I would like to see an option to change the hgcache folder path location. Having this on another drive then the jenkins installation path would be useful, just like I can change the workspace directory. Normally I install the OS on a drive, jenkins and custom service on different partition and have a separated physical drive for scratch (workspace). I would like to include the hgcache onto the scratch drive (this way my setup have very little writing on the OS/application drive/partition (which is backuped) and write a lot on a non backuped drive that can be swap without impact (drive is dead just replace it and mount it at the same place).

I took a look at the source code of the plugin, I guess the following line should be modified to use a variable instead:

Cache.java:

FilePath masterCaches = master.getRootPath().child("hgcache");
FilePath localCaches = node.getRootPath().child("hgcache");
104: FilePath masterCaches = master.getRootPath().child("hgcache");

158: FilePath localCaches = node.getRootPath().child("hgcache");

There's also some log trace that would need to be changed.

This is a quick feature request that could enchance the configuration of this plugin. Thanks




Environment:


N.A.




Project:


Jenkins



Labels:


plugin
scm
mercurial
cache




Priority:


Minor



Reporter:


Jerome Godbout

























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/d/optout.