[JIRA] [build-keeper-plugin] (JENKINS-25293) Build Keeper Plugin functionality does not appear
Stuart Strickland commented on JENKINS-25293 Build Keeper Plugin functionality does not appear Now at 1.598, the functionality suddenly appears in every job. I was configuring a new job from scratch, and there it was, right above the "Build" section. Seems to work fine. I installed it again on the old system, and it started working right away there, too. Speculating, maybe something in the system config.xml blocked it from appearing, but creating the new job tickled the XML in some way to make it finally appear? Or some other fix between 1.585 and 1.598 cleared the blocking bug? I think I'm more upset that nobody commented on this or on the thread or two I posted on the Google group, and I still think the feature could use better documentation. 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] [build-keeper-plugin] (JENKINS-25293) Build Keeper Plugin functionality does not appear
Stuart Strickland commented on JENKINS-25293 Build Keeper Plugin functionality does not appear No comments in a month? Please tell me someone at least looked at this. Meanwhile, I have confirmed on Firefox v33.1 that this occurs there, too. I still see no way to invoke any aspect of this plugin not in a job config, not in system config, not anywhere else under Manage Jenkins, not in workspaces, dashboard, views. Am I missing something obvious? What should I expect to see, and where? I do have Token Macro 1.10 and Run Condition 1.0 plugins installed. Now Jenkins 1.590. 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-21414) PermGen space OOME triggered on use of Jenkins GUI
Stuart Strickland commented on JENKINS-21414 PermGen space OOME triggered on use of Jenkins GUI I may have resolved this myself. Initially I set my memory limits to extremely high levels: ... -Xms8192m -Xmx8192m -XX:MaxPermSize=16384m ... This allowed me to gain some stability. Upon further examination, I found I had one plugin that was misconfigured, was throwing errors, and was probably not being used, the LDAP Email Plugin. I removed that, consolidated redundant environment variables on the JVM call, and ceased using the "-XX:NewSize=128m" parameter. Those were the only substantive changes. I attempted to trigger a dump by calling the FindBugs Warnings chart, and found I could still obtain the report with memory requests much smaller. The following is now working for me, as I have gone five days without a crash for the first time in weeks. jenkins@build-machine-2:~ java -Xms1024m -Xmx1024m \ -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/Users/jenkins/dumps \ -XX:MaxPermSize=1024m -jar jenkins.war --httpPort=8070 I would feel better knowing which of the changes above resolved the problem, though I am happy enough right now not to have to watch for Jenkins failures every 10 minutes. 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-21414) PermGen space OOME triggered on use of Jenkins GUI
Stuart Strickland commented on JENKINS-21414 PermGen space OOME triggered on use of Jenkins GUI In this URL https://www.dropbox.com/s/rdv1a69t2nau7ep/java_pid79986.hprof is a second heap dump of about 148 MB, this one triggered by attempting to view a large (6.8 MB) FindBugs warnings output. The PermGen values were set very high, 2048 MB in the creating job, 8192 MB in the JVM. Viewing a companion FindBugs warning output of about 800 KB did not trigger the heap dump. This can be triggered on demand, on an idle system that has just been restarted. I suspect some sort of memory leak in either the FindBugs plugin or Jenkins itself. I have further verified that I have installed all supporting plugins, and they are up to date. Jenkins itself was just upgraded today to 1.549, with the same result. As this screen capture shows, a large amount of this memory seems to be consumed by FindBugs. https://www.dropbox.com/s/1uc6nz2vda6ouae/HeapDump79986_memory_analysis_1.png If there is something I am doing wrong, please let me know. If there is something wrong with Jenkins or the FindBugs plugin, I hope this shines some light on it. 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.
