[JIRA] [core] (JENKINS-18578) Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable
Title: Message Title Jesse Glick assigned an issue to Oleg Nenashev Jenkins / JENKINS-18578 Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable Change By: Jesse Glick Assignee: Kohsuke Kawaguchi Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-18578) Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable
Title: Message Title Roberto Andrade commented on JENKINS-18578 Re: Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable Another workaround I've found that worked better for me both on master and slave is changing the `user.home` System property by setting the `_JAVA_OPTIONS` environment variable as described [here](http://stackoverflow.com/questions/1501235/change-user-home-system-property). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-18578) Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable
Jesse Glick updated JENKINS-18578 Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable Change By: Jesse Glick (22/Dec/14 9:38 PM) Labels: cacheconfiguration jenkins robustness slave 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] [core] (JENKINS-18578) Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable
Caleb Mayeux commented on JENKINS-18578 Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable Another workaround is to use what Mr. Kohsuke said: In the slave configuration, under the Advanced method of Launch Option, Put the following in the Suffix Start Slave Command " -jar-cache path to jar cache directory" (no quotes) Make sure there's a leading space so the parameters aren't tacked directly onto the slave.jar itself. Still, I'd much prefer if the default jar cache was in the slave FS root. I have a number of slaves using an automounted home directory, and am hitting the quota exceeded error when upgrading from 1.544 to 1.551. 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/groups/opt_out.
[JIRA] [core] (JENKINS-18578) Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable
Andréas Berg commented on JENKINS-18578 Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable This issue is not about the Jenkins working directory. It is about the default jar cache location. Yes, using the slave FS root as default should work for both environments. master is after all just another slave. 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/groups/opt_out.
[JIRA] [core] (JENKINS-18578) Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable
Felix Roethenbacher commented on JENKINS-18578 Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable Actually, it is related to the Jenkins working/home directory (see JENKINS-18459) as this is where Jenkins usually is given read/write access. In an environment where Jenkins WAR is running inside an existing Tomcat application server with user 'tomcat7', Jenkins fails as the user does not have write access to the user's home directory (usually that's '/usr/share/tomcat7') for security reasons. If the slave FS root solves this problem, that's perfect. Just make sure that the actual user running Jenkins has write access to this directory. 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/groups/opt_out.
[JIRA] [core] (JENKINS-18578) Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable
Andréas Berg commented on JENKINS-18578 Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable Good point, your case is actually even worse than ours then, as it fails due to this. We only get decreased performance and the risk of garbage filling up the home directory quota, at which point it will fail for us too. 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/groups/opt_out.
[JIRA] [core] (JENKINS-18578) Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable
Felix Roethenbacher commented on JENKINS-18578 Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable Path should consider JENKINS_HOME system variable (Jenkins running as WAR with user tomcat7). Workaround is to create a sym link from shared tomcat7 directory to Jenkins home directory: ln -s /var/lib/jenkins /usr/share/tomcat7/.jenkins 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/groups/opt_out.
[JIRA] [core] (JENKINS-18578) Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable
Andréas Berg commented on JENKINS-18578 Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable No, using JENKINS_HOME would only work for the master node. Using slave FS root as default is likely a good solution for most people. 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/groups/opt_out.
[JIRA] [core] (JENKINS-18578) Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable
Felix Roethenbacher commented on JENKINS-18578 Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable Well, according to the docs you can set the Jenkins working directory with JENKINS_HOME system variable. That's how it used to work, at least in the master only environment. Maybe there is a a solution that works for both environments, master and slave. 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/groups/opt_out.
[JIRA] [core] (JENKINS-18578) Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable
Jesse Glick commented on JENKINS-18578 Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable I think the default needs to be changed to use the slave FS root. We should default to a safe and expected configuration; in the rare case that someone runs multiple slaves on one machine, if they find the duplicated caches to consume too much space, they can decide to share them in a location of their choice. 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/groups/opt_out.
[JIRA] [core] (JENKINS-18578) Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable
Kohsuke Kawaguchi resolved JENKINS-18578 as Fixed Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable The -jar-cache option in slave.jar lets you set the location of the cache since remoting 2.24. Change By: Kohsuke Kawaguchi (26/Jul/13 6:39 PM) Status: Open Resolved Assignee: KohsukeKawaguchi Resolution: Fixed 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/groups/opt_out.
[JIRA] [core] (JENKINS-18578) Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable
cowwoc commented on JENKINS-18578 Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable I disagree with the way this was resolved, so I filed JENKINS-18956. 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/groups/opt_out.
[JIRA] [core] (JENKINS-18578) Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable
Jesse Glick reopened JENKINS-18578 Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable Did you miss my comment? IMHO the default should be to use the slave FS root. Change By: Jesse Glick (26/Jul/13 6:59 PM) Resolution: Fixed Status: Resolved Reopened 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/groups/opt_out.
[JIRA] [core] (JENKINS-18578) Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable
Andréas Berg updated JENKINS-18578 Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable Change By: Andréas Berg (04/Jul/13 7:10 AM) Description: Thedefaultjarcachelocationisnowhardcodedto~/.jenkins/cache/jarswhichisareallybadideaforabigproductionenvironmentwithnetworkedhomedirectoriesandmultipleaccountsrunningslaves.Thisbehaviourwasintroducedwiththiscommit:https://github.com/jenkinsci/remoting/commit/b5145a06876f4390ef3229d70fa5a7edf0739daeThiscachelocationneedstobeconfigurable.Abonuswouldbeifpermissionswithinitwerehandledinawaythatsupports multi multiple accountsusingit.Thatmightbethecasealreadythough. Wevetriedtoputaworkaroundinplacebydefining-Duser.hometojavabutthataffectsotherthingstooandevenwhendoneformasterandeveryslaveseperatelyIamnotsureifitsolvestheproblementirely. 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/groups/opt_out.
[JIRA] [core] (JENKINS-18578) Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable
Andréas Berg created JENKINS-18578 Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: core Created: 02/Jul/13 11:13 AM Description: The default jar cache location is now hardcoded to ~/.jenkins/cache/jars which is a really bad idea for a big production environment with networked home directories and multiple accounts running slaves. This behaviour was introduced with this commit: https://github.com/jenkinsci/remoting/commit/b5145a06876f4390ef3229d70fa5a7edf0739dae This cache location needs to be configurable. A bonus would be if permissions within it were handled in a way that supports multi accounts using it. That might be the case already though. We've put a workaround in place by defining "-Duser.home" to java but that affects other things too. It also needs to be done for master and every slave seperately so it is easy to make misstakes or forget it for some slaves. Environment: N/A Project: Jenkins Labels: jenkins configuration slave cache Priority: Minor Reporter: Andréas Berg 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/groups/opt_out.
[JIRA] [core] (JENKINS-18578) Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable
Andréas Berg updated JENKINS-18578 Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable Change By: Andréas Berg (02/Jul/13 11:26 AM) Issue Type: Improvement Bug Priority: Minor Major Description: Thedefaultjarcachelocationisnowhardcodedto~/.jenkins/cache/jarswhichisareallybadideaforabigproductionenvironmentwithnetworkedhomedirectoriesandmultipleaccountsrunningslaves.Thisbehaviourwasintroducedwiththiscommit:https://github.com/jenkinsci/remoting/commit/b5145a06876f4390ef3229d70fa5a7edf0739daeThiscachelocationneedstobeconfigurable.Abonuswouldbeifpermissionswithinitwerehandledinawaythatsupportsmultiaccountsusingit.Thatmightbethecasealreadythough.Weve triedto putaworkaroundinplacebydefining-Duser.hometojavabutthataffectsotherthingstoo .Italsoneedstobe andevenwhen doneformasterandeveryslaveseperately so it iseasytomakemisstakesorforgetitforsomeslaves doesnotgetridofthebehaviour . 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/groups/opt_out.
[JIRA] [core] (JENKINS-18578) Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable
Andréas Berg updated JENKINS-18578 Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable Change By: Andréas Berg (02/Jul/13 11:44 AM) Description: Thedefaultjarcachelocationisnowhardcodedto~/.jenkins/cache/jarswhichisareallybadideaforabigproductionenvironmentwithnetworkedhomedirectoriesandmultipleaccountsrunningslaves.Thisbehaviourwasintroducedwiththiscommit:https://github.com/jenkinsci/remoting/commit/b5145a06876f4390ef3229d70fa5a7edf0739daeThiscachelocationneedstobeconfigurable.Abonuswouldbeifpermissionswithinitwerehandledinawaythatsupportsmultiaccountsusingit.Thatmightbethecasealreadythough.Wevetriedtoputaworkaroundinplacebydefining-Duser.hometojavabutthataffectsotherthingstooandevenwhendoneformasterandeveryslaveseperately itdoes Iam not getridof sureifitsolves the behaviour problementirely . 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/groups/opt_out.
