[JIRA] (JENKINS-52636) Gerrit triggered jobs getting delayed
Title: Message Title Marco Miller edited a comment on JENKINS-52636 Re: Gerrit triggered jobs getting delayed Thx [~scoheb]! ;)Btw, a colleague of ours noticed [1] recently, if need be, or there might be other /related PRs too:[1] [https://github.com/jenkinsci/gerrit-trigger-plugin/pull/363|https://github.com/jenkinsci/gerrit-trigger-plugin/pull/363/commits] Note: not sure how close [1] is to [~hugares]' well-detailed findings above, though (did not check myself). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-52636) Gerrit triggered jobs getting delayed
Title: Message Title Marco Miller commented on JENKINS-52636 Re: Gerrit triggered jobs getting delayed Thx Scott Hebert! Btw, a colleague of ours noticed [1] recently, if need be, or there might be other /related PRs too: [1] https://github.com/jenkinsci/gerrit-trigger-plugin/pull/363 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-23878) Add in the GUI an option to restart master (same function as /restart url)
Marco Miller started work on JENKINS-23878 Add in the GUI an option to restart master (same function as /restart url) Change By: Marco Miller (23/Jul/14 3:11 PM) Status: Open In Progress 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-23878) Add in the GUI an option to restart master (same function as /restart url)
Marco Miller assigned JENKINS-23878 to Marco Miller Add in the GUI an option to restart master (same function as /restart url) Change By: Marco Miller (23/Jul/14 3:11 PM) Assignee: Marco Miller 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-23878) Add in the GUI an option to restart master (same function as /restart url)
Marco Miller commented on JENKINS-23878 Add in the GUI an option to restart master (same function as /restart url) Big thx Daniel! -will try it out asap; then we'll see how we update this very issue accordingly. 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-23878) Add in the GUI an option to restart master (same function as /restart url)
Marco Miller commented on JENKINS-23878 Add in the GUI an option to restart master (same function as /restart url) I guess it would; you mean "simple" above right Daniel? (rather than "sample") 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-23878) Add in the GUI an option to restart master (same function as /restart url)
Marco Miller edited a comment on JENKINS-23878 Add in the GUI an option to restart master (same function as /restart url) (Working with Christian) -No; this issue is really about an admin button doing just like what the myJenkins/restart url does. So I just updated the component (set it to core); please let me know if that is still wrong though =) 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-23878) Add in the GUI an option to restart master (same function as /restart url)
Marco Miller commented on JENKINS-23878 Add in the GUI an option to restart master (same function as /restart url) (Working with Christian) -No; this issue is really about an admin button doing just like what the myJenkins/restart url does. 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-23878) Add in the GUI an option to restart master (same function as /restart url)
Marco Miller updated JENKINS-23878 Add in the GUI an option to restart master (same function as /restart url) Change By: Marco Miller (18/Jul/14 7:42 PM) Component/s: core Component/s: safe-restart Component/s: saferestart 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] [acceptance-test-harness] (JENKINS-23004) Contributing 1st Active-Directory plugin tests
Marco Miller updated JENKINS-23004 Contributing 1st Active-Directory plugin tests Change By: Marco Miller (27/May/14 7:25 PM) Description: Scenario 1 : user can log-in to Jenkins as admin after AD security configured- * Given a Jenkins instance that is of type=existing * And a pre-installed active-directory plugin version 1.34 (1.37 failed) * And an AD security configuration that is matrix-based (project) * And a user added to that matrix so she can Administer * When I save such an AD security configuration * Then that user can log-in to that Jenkins as admin. Scenario 2 : user can log-in to Jenkins as admin group member after AD security configured- * Given a Jenkins instance that is of type=existing * And a pre-installed active-directory plugin version 1.34 (1.37 failed) * And an AD security configuration that is matrix-based (project) * And a group added to that matrix so its members can Administer * And a Scenario 3: user being a member of that group * When I save such an AD security configuration * Then that user can wannabe cannot log-in to that Jenkins as admin. after AD security configured- 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] [acceptance-test-harness] (JENKINS-23004) Contributing 1st Active-Directory plugin tests
Marco Miller updated JENKINS-23004 Contributing 1st Active-Directory plugin tests Change By: Marco Miller (27/May/14 6:04 PM) Description: Scenario: user can log-in to Jenkins as admin after AD security configured- * Given a Jenkins instance that is of type=existing * And a pre-installed active-directory plugin version 1.34 (1.37 failed) * And an AD security configuration that is matrix-based (project) * And a user added to that matrix so she can Administer * When I save such an AD security configuration * Then that user can log-in to that Jenkins as admin.Scenario: TODO add user can log - ing test in to Jenkins as admin group member after AD security configured- * Given a Jenkins instance that is of type=existing * And a pre-installed active-directory plugin version 1.34 ( s 1.37 failed ) for * And an AD security configuration that is matrix-based (project) * And a group added to that matrix so its members can Administer * And a user / being a member of that group ; work * When I save such an AD security configuration * Then that user can log- in progress to that Jenkins as admin. 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] [acceptance-test-harness] (JENKINS-23004) Contributing 1st Active-Directory plugin tests
Marco Miller updated JENKINS-23004 Contributing 1st Active-Directory plugin tests Change By: Marco Miller (27/May/14 3:40 PM) Summary: Contributing 1st Active-Directory plugin test tests Description: Scenario: User user can administer log-in to Jenkins as admin after AD security configured- * Given a Jenkins instance that is of type=existing * And a pre-installed active-directory plugin version 1.34 (1.37 failed) * And an AD security configuration that is matrix-based (project or not ) * And a user added to that matrix so she can Administer * When I save such an AD security configuration * Then that Admin user can log-in to that Jenkins * And she can view her user with Administer set as admin .Scenario: TODO add-ing test(s) for user/group; work in progress 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] [acceptance-test-harness] (JENKINS-23113) It shall be possible to use a http proxy with the acceptance test harness
Marco Miller commented on JENKINS-23113 It shall be possible to use a http proxy with the acceptance test harness Test cases I used (GerritTrigger, ActiveDirectory) were successful with the fix for this issue, in both mvn and ide. https://github.com/jenkinsci/acceptance-test-harness/pull/2 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] [acceptance-test-harness] (JENKINS-23113) It shall be possible to use a http proxy with the acceptance test harness
Marco Miller commented on JENKINS-23113 It shall be possible to use a http proxy with the acceptance test harness (I'd recommend you click on "Start Progress", Scott.) 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] [acceptance-test-harness] (JENKINS-23004) Contributing 1st Active-Directory plugin test
Marco Miller updated JENKINS-23004 Contributing 1st Active-Directory plugin test Change By: Marco Miller (20/May/14 1:16 PM) Description: Scenario: User can administer Jenkins after AD security configured- * Given a Jenkins instance that is of type=existing * And a pre-installed active-directory plugin version 1.34 (1.37 failed) * And an AD security configuration that is matrix-based (project or not) * And a user added to that matrix so she can Administer * When I save such an AD security configuration * Then that Admin user can log-in to that Jenkins * And she can view her user with Administer set. Scenario: TODO add-ing test(s) for user/group; work in progress 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] [acceptance-test-harness] (JENKINS-23004) Contributing 1st Active-Directory plugin test
Marco Miller updated JENKINS-23004 Contributing 1st Active-Directory plugin test Change By: Marco Miller (20/May/14 1:15 PM) Description: /** * Scenario: User can administer Jenkins after AD security configured- * Given a Jenkins instance that is of type=existing * And a pre-installed active-directory plugin version 1.34 (1.37 failed) * And an AD security configuration that is matrix-based (project or not) * And a user added to that matrix so she can Administer * When I save such an AD security configuration * Then that Admin user can log-in to that Jenkins * And she can view her user with Administer set. * Scenario: TODO add-ing test(s) for user / group; work in progress 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] [acceptance-test-harness] (JENKINS-23004) Contributing 1st Active-Directory plugin test
Marco Miller updated JENKINS-23004 Contributing 1st Active-Directory plugin test Change By: Marco Miller (20/May/14 1:14 PM) Description: TODO /** * Scenario: User can administer Jenkins after AD security configured- * Given a Jenkins instance that is of type=existing * And a pre-installed active-directory plugin version 1.34 (1.37 failed) * And an AD security configuration that is matrix-based (project or not) * And a user added to that matrix so she can Administer * When I save such an AD security configuration * Then that Admin user can log-in to that Jenkins * And she can view her user with Administer set. */ 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] [acceptance-test-harness] (JENKINS-23004) Contributing 1st Active-Directory plugin test
Marco Miller updated JENKINS-23004 Contributing 1st Active-Directory plugin test Change By: Marco Miller (13/May/14 4:04 PM) Affects Version/s: current 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] [acceptance-test-harness] (JENKINS-23004) Contributing 1st Active-Directory plugin test
Marco Miller created JENKINS-23004 Contributing 1st Active-Directory plugin test Issue Type: New Feature Assignee: Marco Miller Components: acceptance-test-harness Created: 13/May/14 4:04 PM Description: TODO Project: Jenkins Labels: plugin Priority: Major Reporter: Marco Miller 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] [acceptance-test-harness] (JENKINS-23004) Contributing 1st Active-Directory plugin test
Marco Miller started work on JENKINS-23004 Contributing 1st Active-Directory plugin test Change By: Marco Miller (13/May/14 4:04 PM) Status: Open In Progress 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-22310) CLI slow performance investigation
Marco Miller commented on JENKINS-22310 CLI slow performance investigation Corrected now (edited above); thx! => https://github.com/jenkinsci/jenkins/commits/stable https://github.com/jenkinsci/jenkins/commit/fd9f273f3645fc670e1283bbed7967f789475c86 https://github.com/jenkinsci/jenkins/commit/705f5eb8e737d1e0770f509edb5edb3d50f60cdc 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-21579) Very slow resource loading from UberClassLoader
Marco Miller edited a comment on JENKINS-21579 Very slow resource loading from UberClassLoader fd9f273f3645fc670e1283bbed7967f789475c86 and 705f5eb8e737d1e0770f509edb5edb3d50f60cdc are the 2 commits by KK fixing this issue. -Which commits I back-ported to 1.554.1 (current 'stable’ branch). I did so after this successful testing of ours: jenkinsci /jenkins unit tests, for regression (passing ones kept passing); jenkinsci /acceptance-test-harness, incl. both parent- and plugin-1st class-loading plugins (failures looked unrelated); Ericsson-internal CLI ‘stress' tests, which used to reproduce JENKINS-22310; incl. parent/plugin-1st plugins, too; brief manual testing through quick clicking-around, exercising some parent+plugin-1st (plugins) class-loading. 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-22310) CLI slow performance investigation
Marco Miller edited a comment on JENKINS-22310 CLI slow performance investigation fd9f273f3645fc670e1283bbed7967f789475c86 and 705f5eb8e737d1e0770f509edb5edb3d50f60cdc are the 2 commits by KK fixing this issue. -Which commits I back-ported to 1.554.1 (current 'stable’ branch). I did so after this successful testing of ours: jenkinsci /jenkins unit tests, for regression (passing ones kept passing); jenkinsci /acceptance-test-harness, incl. both parent- and plugin-1st class-loading plugins (failures looked unrelated); Ericsson-internal CLI ‘stress' tests, which used to reproduce JENKINS-22310; incl. parent/plugin-1st plugins, too; brief manual testing through quick clicking-around, exercising some parent+plugin-1st (plugins) class-loading. 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-22310) CLI slow performance investigation
Marco Miller commented on JENKINS-22310 CLI slow performance investigation ed1f1435a016da86ad0321e9acf3389a3c68add3 and 5daaf168a81902d852082f3f03b47e6b78f56981 are the 2 commits by KK fixing this issue. -Which commits I back-ported to 1.554.1 (current 'stable’ branch). I did so after this successful testing of ours: jenkinsci /jenkins unit tests, for regression (passing ones kept passing); jenkinsci /acceptance-test-harness, incl. both parent- and plugin-1st class-loading plugins (failures looked unrelated); Ericsson-internal CLI ‘stress' tests, which used to reproduce JENKINS-22310; incl. parent/plugin-1st plugins, too; brief manual testing through quick clicking-around, exercising some parent+plugin-1st (plugins) class-loading. 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-21579) Very slow resource loading from UberClassLoader
Marco Miller commented on JENKINS-21579 Very slow resource loading from UberClassLoader ed1f1435a016da86ad0321e9acf3389a3c68add3 and 5daaf168a81902d852082f3f03b47e6b78f56981 are the 2 commits by KK fixing this issue. -Which commits I back-ported to 1.554.1 (current 'stable’ branch). I did so after this successful testing of ours: jenkinsci /jenkins unit tests, for regression (passing ones kept passing); jenkinsci /acceptance-test-harness, incl. both parent- and plugin-1st class-loading plugins (failures looked unrelated); Ericsson-internal CLI ‘stress' tests, which used to reproduce JENKINS-22310; incl. parent/plugin-1st plugins, too; brief manual testing through quick clicking-around, exercising some parent+plugin-1st (plugins) class-loading. 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] [cli] (JENKINS-20709) CLI client hangs
Marco Miller commented on JENKINS-20709 CLI client hangs (Please note that the above pingers-disabling hypothesis was inconclusive as we were trying it out.) 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-20217) Too many PingThread's
Marco Miller commented on JENKINS-20217 Too many PingThread's Could such many pingers negatively impact channel /socket functionality in prod, Jesse? 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] [cli] (JENKINS-20709) CLI client hangs
Marco Miller commented on JENKINS-20709 CLI client hangs Kohsuke, I also work on that issue of ours (Ericsson). -Thx for your help so far btw =) Since we disabled these pingers -below, it seems like the hanging no longer happens.. Of course I cannot guarantee that 100%, but I wanted you to be aware of that info: -Dhudson.remoting.Launcher.pingIntervalSec=0 -Dhudson.remoting.Launcher.pingTimeoutSec=0 -Dhudson.slaves.ChannelPinger.pingInterval=0 Now, we didn't try to disable only either one of those 2 pingers -yet. -All we did was to disable both of them -so far. Your thoughts on this hypothesis are welcome! =) Thx+ again!! PS: should pinger-disabling be a "solution", what could be likely consequences of doing so in prod? -we wonder.. PPS: another hypo: master waiting forever for slave to send response, while master's channel is artificially kept alive/open -thx to pinger(s). 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-20610) FileAlreadyExistsException upon "deleted" symlink while (re)creating it
Marco Miller closed JENKINS-20610 as Fixed FileAlreadyExistsException upon "deleted" symlink while (re)creating it Change By: Marco Miller (18/Nov/13 3:17 PM) Status: Resolved Closed 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] [cli] (JENKINS-18058) NegativeArraySizeException when trying to enable a job using Jenkins CLI
Marco Miller stopped work on JENKINS-18058 NegativeArraySizeException when trying to enable a job using Jenkins CLI Change By: Marco Miller (14/Nov/13 3:25 PM) Status: In Progress Open 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] [cli] (JENKINS-18058) NegativeArraySizeException when trying to enable a job using Jenkins CLI
Marco Miller assigned JENKINS-18058 to Unassigned NegativeArraySizeException when trying to enable a job using Jenkins CLI Change By: Marco Miller (14/Nov/13 3:26 PM) Assignee: Marco Miller 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] [cli] (JENKINS-18058) NegativeArraySizeException when trying to enable a job using Jenkins CLI
Marco Miller commented on JENKINS-18058 NegativeArraySizeException when trying to enable a job using Jenkins CLI I closed the pull request for reasons given in the latter. https://github.com/jenkinsci/jenkins/pull/999 Hence this not being Resolved yet; up to another contributor then, at will. Refer to the many potentially useful suggestions as comments in that pull-req, solution-wise. 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-20610) FileAlreadyExistsException upon "deleted" symlink while (re)creating it
Marco Miller
created JENKINS-20610
FileAlreadyExistsException upon "deleted" symlink while (re)creating it
Issue Type:
Bug
Assignee:
Marco Miller
Components:
core
Created:
15/Nov/13 9:30 PM
Description:
Some Jenkins instances of ours do log FileAlreadyExistsException-s from time to time:
java.nio.file.FileAlreadyExistsException: (path2onesJob)/lastSuccessful
at sun.nio.fs.UnixException.translateToIOException(UnixException.java:88)
(..) at hudson.Util.createSymlinkJava7(Util.java:1122)
(..)
-Above trace mapping to 1.509.2.
Code shows "proper" deletion of symlink prior to (re)creating it:
(..)
filesC.getMethod("deleteIfExists", pathC).invoke(null, path);
Object noAttrs = Array.newInstance(Class.forName("java.nio.file.attribute.FileAttribute"), 0);
filesC.getMethod("createSymbolicLink", pathC, pathC, noAttrs.getClass()).invoke(null, path, target, noAttrs);
-Looking at that code and around,
I suspect some occasional race condition by lack of concurrency safeness:
1. thread-A deletes any existing lastSuccessful symlink (so far so good)
2. thread-B deletes it too but that is a no-op by now, given 1.
3. thread-A (re)creates the symlink (no problem yet)
4. thread-B recreates the symlink, but that throws our hereby exception, given 3. (problematic).
-Unless such initial deletion fails because of this:
"On some operating systems it may not be possible to remove a file when it is open and in use by this Java virtual machine or other programs."
http://docs.oracle.com/javase/7/docs/api/java/nio/file/Files.html#deleteIfExists(java.nio.file.Path)
-Assuming the above threading hypothesis and solving it to be hard & risky.
Project:
Jenkins
Priority:
Major
Reporter:
Marco Miller
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-20610) FileAlreadyExistsException upon "deleted" symlink while (re)creating it
Marco Miller started work on JENKINS-20610 FileAlreadyExistsException upon "deleted" symlink while (re)creating it Change By: Marco Miller (15/Nov/13 9:31 PM) Status: Open In Progress 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] [valgrind] (JENKINS-18950) valgrind-plugin makes jenkins run out of memory under heavy use
Marco Miller commented on JENKINS-18950 valgrind-plugin makes jenkins run out of memory under heavy use Fix pull-requested => https://github.com/jenkinsci/valgrind-plugin/pull/2 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] [valgrind] (JENKINS-18950) valgrind-plugin makes jenkins run out of memory under heavy use
Marco Miller started work on JENKINS-18950 valgrind-plugin makes jenkins run out of memory under heavy use Change By: Marco Miller (26/Jul/13 3:29 PM) Status: Open In Progress 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] [valgrind] (JENKINS-18950) valgrind-plugin makes jenkins run out of memory under heavy use
Marco Miller created JENKINS-18950 valgrind-plugin makes jenkins run out of memory under heavy use Issue Type: Bug Assignee: Marco Miller Components: valgrind Created: 26/Jul/13 2:54 PM Description: valgrind-plugin makes jenkins run out of memory under heavy use. This is caused by too many (all) Report objects being retained in heap by Result objects. Fix is about making such report objects on-demand or just-in-time, rather than always and too early (and as kept forever or so). We at Ericsson have production (jenkins) instances that were recently hit by this bug, in terms of JVMs running out-of-memory. We indeed clearly saw such many large report objects retaining the most of our heap as per profiling of the latter. Project: Jenkins Priority: Major Reporter: Marco Miller 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] [build-pipeline] (JENKINS-17872) build-pipeline-plugin seems to have lost its ability to show sub-projects
Marco Miller resolved JENKINS-17872 as Fixed build-pipeline-plugin seems to have lost its ability to show sub-projects Change By: Marco Miller (22/May/13 2:20 PM) Status: Open Resolved 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] [build-pipeline] (JENKINS-17872) build-pipeline-plugin seems to have lost its ability to show sub-projects
Marco Miller commented on JENKINS-17872 build-pipeline-plugin seems to have lost its ability to show sub-projects I pushed a fix for this issue to that plugin's master (May 3-10), so it should show up in plugin's next release: https://github.com/jenkinsci/build-pipeline-plugin/commits/master 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-17970) Change-set Identity regex once broke against Swedish character
Marco Miller updated JENKINS-17970 Change-set Identity regex once broke against Swedish character Change By: Marco Miller (15/May/13 6:32 PM) Description: Change-set's Identity regex once broke against a Swedish character, for us here at Ericsson. By "broke" I mean that for some reason, our Jenkins/Java stack was running latin-1 character set/encoding, instead of utf8. So our git handled that Swedish character as utf8 (2-bytes) but Jenkins/Java read it as latin-1 (1-byte) -through that "broken" change-set Id regex. What’s too bad is that the character in that Swedish user name takes 2 bytes in utf8: \303 \205 (octal). But \205 doesn’t exist in latin-1, so the regex dot didn’t want it and the match failed.Needed then is a robustness fix so that regex (GitChangeSet IDENTITY's) does not reject such a possibly-desired match. We say so even though there is no guarantee that such a fixed regex would keep matching our mistreated Swedish name in the future. All we know is that we once needed that fix to survive an awkward - ( yet realistic - ) Jenkins/Java stack setup (in terms of default locale and/or character-set encoding). 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-17970) Change-set Identity regex once broke against Swedish character
Marco Miller updated JENKINS-17970 Change-set Identity regex once broke against Swedish character Change By: Marco Miller (15/May/13 6:31 PM) Description: Change-set's Identity regex once broke against a Swedish character, for us here at Ericsson. By "broke" I mean that for some reason, our Jenkins/Java stack was running latin-1 character set/encoding, instead of utf8. So our git handled that Swedish character as utf8 (2-bytes) but Jenkins/Java read it as latin-1 (1-byte) -through that "broken" change-set Id regex. What’s too bad is that the character in that Swedish user name takes 2 bytes in utf8: \303 \205 (octal). But \205 doesn’t exist in latin-1, so the regex dot didn’t want it and the match failed. Needed then is a robustness fix so that regex (GitChangeSet IDENTITY's) does not reject such a possibly-desired match. We say so even though there is no guarantee that such a fixed regex would keep matching our mistreated Swedish name in the future. All we know is that we once needed that fix to survive an awkward -yet realistic- Jenkins/Java stack setup (in terms of default locale and/or character-set encoding). 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-17970) Change-set Identity regex once broke against Swedish character
Marco Miller created JENKINS-17970 Change-set Identity regex once broke against Swedish character Issue Type: Bug Assignee: Marco Miller Components: git, plugin Created: 15/May/13 6:20 PM Description: Change-set's Identity regex once broke against a Swedish character, for us here at Ericsson. By "broke" I mean that for some reason, our Jenkins/Java stack was running latin-1 character set/encoding, instead of utf8. So our git handled that Swedish character as utf8 (2-bytes) but Jenkins/Java read it as latin-1 (1-byte) -through that "broken" change-set Id regex. What’s too bad is that the character in that Swedish user name takes 2 bytes in utf8: \303 \205 (octal). But \205 doesn’t exist in latin-1, so the regex dot didn’t want it and the match failed. Project: Jenkins Priority: Minor Reporter: Marco Miller 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] [build-pipeline] (JENKINS-17872) build-pipeline-plugin seems to have lost its ability to show sub-projects
Marco Miller created JENKINS-17872 build-pipeline-plugin seems to have lost its ability to show sub-projects Issue Type: Improvement Assignee: Marco Miller Components: build-pipeline Created: 06/May/13 2:52 PM Description: build-pipeline-plugin seems to have lost its ability to show sub-projects (alongside downstream jobs). Note: sub-projects (known as Subprojects in the UI) are brought by the parameterized-trigger plugin. Project: Jenkins Priority: Minor Reporter: Marco Miller 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.
