[JIRA] (JENKINS-18578) Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable
Title: Message Title Andréas Berg commented on JENKINS-18578 Re: Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable Will this also affect the Jenkins master or only the slaves? What will the new default be? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] [git] (JENKINS-9016) Git creates usernames based on 'name' not the email.
Andréas Berg commented on JENKINS-9016 Git creates usernames based on name not the email. The unique identifier in git is the e-mail address so matching towards a Jenkins account on user name is really bad. In some cases, like for example push-review tests with Gerrit, you do not need to match to a Jenkins account at all, just use the e-mail address in the commit when sending feedback. Option #1 (Try looking up a user's email and comparing that.) is definitely the way this should be implemented. Option #3 (Looking up the user's email in LDAP, if LDAP is being used.) would be a great bonus. Option #2 (Using the user portion from the email (e.g. someu...@example.com becomes someuser).) is just as bad is matching on user name and solves nothing. We are a big company and with a lot of people, some do have the exact same names so now we have users getting e-mail feedback on git commits they are not the author of. 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] [git] (JENKINS-9016) Git creates usernames based on 'name' not the email.
Andréas Berg edited a comment on JENKINS-9016 Git creates usernames based on name not the email. The unique identifier in git is the e-mail address so matching towards a Jenkins account on user name is really bad. In some cases, like for example push-review tests with Gerrit, you do not need to match to a Jenkins account at all, just use the e-mail address in the commit when sending feedback. Option #1 (Try looking up a user's email and comparing that.) is definitely the way this should be implemented. Option #3 (Looking up the user's email in LDAP, if LDAP is being used.) would be a great bonus. Option #2 (Using the user portion from the email (e.g. someu...@example.com becomes someuser).) is just as bad is matching on user name and solves nothing. We are a big company with a lot of people, some do have the exact same names so now we have users getting e-mail feedback on git commits they are not the author of. 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] [gui] (JENKINS-13978) Add posibility to copy view
Andréas Berg commented on JENKINS-13978 Add posibility to copy view I can confirm too. I see no trace of this functionality after upgrading to 1.546. Was really looking forward to this one. 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
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
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] [git] (JENKINS-20231) Wipe out repository force clone option is broken since GIT plugin version 2.0
Andréas Berg commented on JENKINS-20231 Wipe out repository force clone option is broken since GIT plugin version 2.0 The update to GIT plugin 2.0 broke the functionality. The Gerrit Trigger plugin remains untouched. Our workaround to use clean instead of wipe has since I wrote the initial issue also stopped working. Currently we can no longer use the GIT client plugin and have replaced it with a shell script build step that issues the proper Git commands. Since our build step works and uses the environment variables delivered by the Gerrit Trigger plugin, I remain confident that the Gerrit Trigger plugin works fine, and the GIT client plugin is broken as it no longer respects the variables as input. 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-18671) Clock Difference broken on Manage Nodes page
Andréas Berg created JENKINS-18671 Clock Difference broken on Manage Nodes page Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: jenkins_node_clock_difference.png Components: core Created: 09/Jul/13 12:54 PM Description: Since we upgraded from Jenkins 1.520 to 1.522 the Clock Difference is broken on the Manage Nodes page. Master and all slaves are in sync but Jenkins reports something completely different. Master and any slave running on the same server as master is reported correctly. Environment: Jenkins 1.522 on Ubuntu 13.04, nodes on solaris sparc, solaris x86 and redhat linux. Project: Jenkins Priority: Major 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-18671) Clock Difference broken on Manage Nodes page
Andréas Berg updated JENKINS-18671 Clock Difference broken on Manage Nodes page Change By: Andréas Berg (09/Jul/13 3:03 PM) Description: SinceweupgradedfromJenkins1.520to1.522theClockDifferenceisbrokenontheManageNodespage.MasterandallslavesareinsyncbutJenkinsreportssomethingcompletelydifferent.Masterandanyslaverunningonthesameserverasmasterisreportedcorrectly. Wehave3Jenkinsserversdisplayingthesamesymptoms. 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-18671) Clock Difference broken on Manage Nodes page
Andréas Berg commented on JENKINS-18671 Clock Difference broken on Manage Nodes page This issue appeared for us after upgrading from 1.520 to 1.522. I've never seen this behaviour before so I doubt its realted to #10771 as that issue has existed for almost two years. 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-18614) Config screen loading dialog permanently blocks config
Andréas Berg commented on JENKINS-18614 Config screen loading dialog permanently blocks config I encountered this as well and narrowed it down a bit. Disabling the envinject plugin fixes the problem. 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-18614) Config screen loading dialog permanently blocks config
Andréas Berg updated JENKINS-18614 Config screen loading dialog permanently blocks config Change By: Andréas Berg (04/Jul/13 7:23 AM) Component/s: envinject 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-18614) Config screen loading dialog permanently blocks config
Andréas Berg commented on JENKINS-18614 Config screen loading dialog permanently blocks config In my case, yes, its a duplicate of that issue. 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] [compact-columns] (JENKINS-18622) Broken description tool-tip display in Job Name w/ Options
Andréas Berg created JENKINS-18622 Broken description tool-tip display in Job Name w/ Options Issue Type: Bug Affects Versions: current Assignee: Jacob Robertson Components: compact-columns Created: 04/Jul/13 2:22 PM Description: When description is not set for a job and Job Name w/ Options is used with a description tool-tip, the description of previously moused over job is re-used. Environment: Windows 7 with Chrome browser Project: Jenkins 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 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.
