[JIRA] [git-client-plugin] (JENKINS-27461) Git polling shows exception when job is currently running
Michael Niestegge closed JENKINS-27461 as Postponed Git polling shows exception when job is currently running The exception is caused by the artifactory plugin. Created a new issue in their Jira: https://www.jfrog.com/jira/browse/HAP-583 Change By: Michael Niestegge (17/Mar/15 3:45 PM) Status: Open Closed Resolution: Postponed 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-client-plugin] (JENKINS-27461) Git polling shows exception when job is currently running
Michael Niestegge
updated JENKINS-27461
Git polling shows exception when job is currently running
Change By:
Michael Niestegge
(17/Mar/15 2:47 PM)
Description:
Iusegitpollingtotriggermyjobs.IrecognizedaExceptionwithintheGitPollingLog:{code}Startedon17.03.201515:40:08Usingstrategy:Default[poll]LastBuiltRevision:Revisionae505d729d3b76e43782b351d7628024e065db61(refs/remotes/origin/master)ERROR:FailedtorecordSCMpollingforhudson.maven.MavenModuleSet@42caa9c4[(BUILD)mp-modulesmasterunit]java.lang.RuntimeException:UnabletodetermineMavenversion atorg.jfrog.hudson.maven3.extractor.MavenExtractorEnvironment.isMavenVersionValid(MavenExtractorEnvironment.java:151) atorg.jfrog.hudson.maven3.extractor.MavenExtractorEnvironment.buildEnvVars(MavenExtractorEnvironment.java:106) athudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:914) athudson.maven.AbstractMavenBuild.getEnvironment(AbstractMavenBuild.java:56) athudson.maven.MavenModuleSetBuild.getEnvironment(MavenModuleSetBuild.java:167) athudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:564) athudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:526) athudson.scm.SCM.compareRemoteRevisionWith(SCM.java:380) athudson.scm.SCM.poll(SCM.java:397) athudson.model.AbstractProject._poll(AbstractProject.java:1446) athudson.model.AbstractProject.poll(AbstractProject.java:1349) atjenkins.triggers.SCMTriggerItem$SCMTriggerItems$Bridge.poll(SCMTriggerItem.java:119) athudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:515) athudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:544) athudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) atjava.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) atjava.util.concurrent.FutureTask.run(FutureTask.java:266) atjava.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) atjava.lang.Thread.run(Thread.java:745)Causedby:java.lang.NullPointerException atorg.jfrog.hudson.util.MavenVersionHelper.getMavenInstallation(MavenVersionHelper.java:105) atorg.jfrog.hudson.util.MavenVersionHelper.isAtLeastVersion(MavenVersionHelper.java:81) atorg.jfrog.hudson.util.MavenVersionHelper.isAtLeastResolutionCapableVersion(MavenVersionHelper.java:72) atorg.jfrog.hudson.maven3.extractor.MavenExtractorEnvironment.isMavenVersionValid(MavenExtractorEnvironment.java:149) ...19more{code}Theexceptionoccurswhenthethegitpollingistriggeredwhilethejobisalreadyinprogress.
Thechangeswillnotbepolledagain.Ifthereisanotherchangeafterthejobhasfinishedalsothechangesintheabortedpollwillbebuild.
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-client-plugin] (JENKINS-27461) Git polling shows exception when job is currently running
Michael Niestegge created JENKINS-27461 Git polling shows exception when job is currently running Issue Type: Bug Assignee: Nicolas De Loof Components: git-client-plugin Created: 17/Mar/15 2:45 PM Description: I use git polling to trigger my jobs. I recognized a Exception within the "Git Polling Log": Started on 17.03.2015 15:40:08 Using strategy: Default [poll] Last Built Revision: Revision ae505d729d3b76e43782b351d7628024e065db61 (refs/remotes/origin/master) ERROR: Failed to record SCM polling for hudson.maven.MavenModuleSet@42caa9c4[(BUILD) mp-modules master unit] java.lang.RuntimeException: Unable to determine Maven version at org.jfrog.hudson.maven3.extractor.MavenExtractorEnvironment.isMavenVersionValid(MavenExtractorEnvironment.java:151) at org.jfrog.hudson.maven3.extractor.MavenExtractorEnvironment.buildEnvVars(MavenExtractorEnvironment.java:106) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:914) at hudson.maven.AbstractMavenBuild.getEnvironment(AbstractMavenBuild.java:56) at hudson.maven.MavenModuleSetBuild.getEnvironment(MavenModuleSetBuild.java:167) at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:564) at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:526) at hudson.scm.SCM.compareRemoteRevisionWith(SCM.java:380) at hudson.scm.SCM.poll(SCM.java:397) at hudson.model.AbstractProject._poll(AbstractProject.java:1446) at hudson.model.AbstractProject.poll(AbstractProject.java:1349) at jenkins.triggers.SCMTriggerItem$SCMTriggerItems$Bridge.poll(SCMTriggerItem.java:119) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:515) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:544) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.NullPointerException at org.jfrog.hudson.util.MavenVersionHelper.getMavenInstallation(MavenVersionHelper.java:105) at org.jfrog.hudson.util.MavenVersionHelper.isAtLeastVersion(MavenVersionHelper.java:81) at org.jfrog.hudson.util.MavenVersionHelper.isAtLeastResolutionCapableVersion(MavenVersionHelper.java:72) at org.jfrog.hudson.maven3.extractor.MavenExtractorEnvironment.isMavenVersionValid(MavenExtractorEnvironment.java:149) ... 19 more The exception occurs when the the git polling is triggered while the job is already in progress. Environment: Jenkins 1.596.1 LTS git-client-plugin 1.16.1 (also tested 1.15) git-plugin 1.6 (also tested 1.5) running on Ubuntu 14.04 LTS with local git installation 1.9.1 Project: Jenkins Labels: maven git polling pollscm exception Priority: Critical Reporter: Michael Niestegge 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
[JIRA] [performance-plugin] (JENKINS-22011) Performance plugin report not failing build based on relative thresholds.
Michael Niestegge edited a comment on JENKINS-22011 Performance plugin report not failing build based on relative thresholds. I guess I misunderstood some of the settings of the plugin. It was not clear to me that I can only use either relative threshold or the total error threshold. After I recognized my fault I switched back to the 1.11 official release. The relative threshold is working there in my environment now. Sorry for the circumstances. 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] [performance-plugin] (JENKINS-22011) Performance plugin report not failing build based on relative thresholds.
Michael Niestegge edited a comment on JENKINS-22011 Performance plugin report not failing build based on relative thresholds. @Markom: Relative thresholds works now. Thanks! Would be nice to include the patch into a release! 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] [performance-plugin] (JENKINS-22011) Performance plugin report not failing build based on relative thresholds.
Michael Niestegge edited a comment on JENKINS-22011 Performance plugin report not failing build based on relative thresholds. @Markom: I tried your patch. The relative threshold still doesn't break the build. Looking forward for a fix 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] [performance-plugin] (JENKINS-22011) Performance plugin report not failing build based on relative thresholds.
Michael Niestegge edited a comment on JENKINS-22011 Performance plugin report not failing build based on relative thresholds. @Marcom: I tried your patch. The relative threshold still doesn't break the build. Looking forward for a fix 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] [performance-plugin] (JENKINS-22011) Performance plugin report not failing build based on relative thresholds.
Michael Niestegge commented on JENKINS-22011 Performance plugin report not failing build based on relative thresholds. ~marcom I tried your patch. The relative threshold still doesn't break the build. Looking forward for a fix 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] [performance-plugin] (JENKINS-22011) Performance plugin report not failing build based on relative thresholds.
Michael Niestegge commented on JENKINS-22011 Performance plugin report not failing build based on relative thresholds. Still facing this problem Jenkins ver. 1.580.1 LTS 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] [performance-plugin] (JENKINS-22011) Performance plugin report not failing build based on relative thresholds.
Michael Niestegge commented on JENKINS-22011 Performance plugin report not failing build based on relative thresholds. I cannot build the performance plugin by myself. Maven tells me: ERROR Failed to execute goal on project performance: Could not resolve dependencies for project org.jenkins-ci.plugins:performance:hpi:1.12-SNAPSHOT: Could not find artifact org.jenkins-ci.main:jenkins-core:jar:1.480 in artifactory (http://artifactory/repo) 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] [performance-plugin] (JENKINS-22011) Performance plugin report not failing build based on relative thresholds.
Michael Niestegge edited a comment on JENKINS-22011 Performance plugin report not failing build based on relative thresholds. trying to build it myself...will report back 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] [performance-plugin] (JENKINS-22011) Performance plugin report not failing build based on relative thresholds.
Michael Niestegge edited a comment on JENKINS-22011 Performance plugin report not failing build based on relative thresholds. ...never mind _ 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] [repository-connector-plugin] (JENKINS-25395) org.apache.maven.wagon.authorization.AuthorizationException when requesting maven-metadata.xml
Michael Niestegge updated JENKINS-25395 org.apache.maven.wagon.authorization.AuthorizationException when requesting maven-metadata.xml Change By: Michael Niestegge (03/Nov/14 12:25 PM) Environment: Jenkins1.585RepositoryConnectorPlugin1.0.1 Artifactory2.6.6 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-7844) A Filter to sort jobs by last run time.
Michael Niestegge commented on JENKINS-7844 A Filter to sort jobs by last run time. I am missing this feature, 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/d/optout.
[JIRA] [core] (JENKINS-7844) A Filter to sort jobs by last run time.
Michael Niestegge edited a comment on JENKINS-7844 A Filter to sort jobs by last run time. I am missing this feature, too . As a workaround I installed Compact Columns and order the view by the last state. 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-7844) A Filter to sort jobs by last run time.
Michael Niestegge updated JENKINS-7844 A Filter to sort jobs by last run time. Change By: Michael Niestegge (31/Oct/14 8:35 AM) Attachment: view.png Attachment: settings.png 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-7844) A Filter to sort jobs by last run time.
Michael Niestegge edited a comment on JENKINS-7844 A Filter to sort jobs by last run time. I am missing this feature, too . As a workaround I installed Compact Columns and order the view by the last state. 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-7844) A Filter to sort jobs by last run time.
Michael Niestegge updated JENKINS-7844 A Filter to sort jobs by last run time. Change By: Michael Niestegge (31/Oct/14 10:29 AM) Attachment: view.png 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] [repository-connector-plugin] (JENKINS-25395) org.apache.maven.wagon.authorization.AuthorizationException when requesting maven-metadata.xml
Michael Niestegge created JENKINS-25395 org.apache.maven.wagon.authorization.AuthorizationException when requesting maven-metadata.xml Issue Type: Bug Assignee: Unassigned Attachments: AuthExcpetion.png Components: repository-connector-plugin Created: 31/Oct/14 3:14 PM Description: I installed an update on our jenkins installation and also updated several plugins. After the update several jobs were not able to retrieve the latest release version from my maven repository. Investigating the console output showed me the mentioned exception when trying to download the maven-metadata.xml. For further details please see I downgraded the Repository Connector Plugin to 0.8.2 an everything works again. So the bug seems to be part of the 1.0.1 release of the plugin. Environment: Jenkins 1.585 Repository Connector Plugin 1.0.1 Project: Jenkins Labels: jenkins exception plugin Priority: Minor Reporter: Michael Niestegge 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] [repository-connector-plugin] (JENKINS-25395) org.apache.maven.wagon.authorization.AuthorizationException when requesting maven-metadata.xml
Michael Niestegge updated JENKINS-25395 org.apache.maven.wagon.authorization.AuthorizationException when requesting maven-metadata.xml Change By: Michael Niestegge (31/Oct/14 3:28 PM) Priority: Minor Major 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] [htmlpublisher] (JENKINS-11689) HTMLPublisher does not publish latest report to project page if build fails
Michael Niestegge commented on JENKINS-11689 HTMLPublisher does not publish latest report to project page if build fails I am also facing this "misbehavior". A fix would be nice. 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-20607) GIT Plugin 2.0: Polling ignores commit from certain users not working
Michael Niestegge commented on JENKINS-20607 GIT Plugin 2.0: Polling ignores commit from certain users not working Same here. Workaround does not work for me. Does it matter what order the additional behaviors have? 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-20607) GIT Plugin 2.0: Polling ignores commit from certain users not working
Michael Niestegge edited a comment on JENKINS-20607 GIT Plugin 2.0: Polling ignores commit from certain users not working Same here. Workaround does not work for me. Does it matter what order the additional behaviors have? My concrete problem: 2 branches: A and B Job is parameterized so I can tell which branch to build. Job scans both branches (by origin/**) every hour to check for changes. Jenkins raises the build number within the pom files. Commits by Jenkins user should be ignored and not cause the job to run. When the last build was in branch A and changes in branch B (by scanning origin/**) are detected, the build for branch B gets kicked off correctly. Unfortunately also changes in branch A (raised build number by jenkins)are detected an d another build gets scheduled, leaving this message in the log: Multiple candidate revisions Scheduling another build to catch up with (BUILD) my faulty job From that point on, the job switches between branch A and B every time and is scheduling the other branch to get build every time causing an endless loop. 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-19544) OutOfMemory due to unbounded storage in OldDataMonitor
Michael Niestegge commented on JENKINS-19544 OutOfMemory due to unbounded storage in OldDataMonitor I am running into the same problem with Jenkins 1.552 on Debian 5.0. The error shows up when the FingerprintCleanupThread starts running (usually during the night). The process fills the heap memory with one very large object: "hudson.diagnosis.OldDataMonitor". The object is never deleted out of the heap memory. I increased memory for Jenkins and triggered the process manually (FingerprintCleanupThread.invoke() in the script console). Each run stacks on the memory until no more memory is available causing the UI to crash and the jenkins.log filling up with errors of "Process leaked file discriptor". The "Manage Old Data" screen (reachable via Manage Jenkins) shows a lot of “failed to locate class: com.thoughtworks.xstream.mapper.CannotResolveClassException: hudson.plugins.disk_usage.BuildDiskUsageAction" errors. I was able to discard them using the button at the bottom of the screen. After I discarded the errors i started the FingerprintCleanupThread again and it used far less memory. There are new errors showing up in the "Manage Old Data" screen during the day, so I have to check them every day. Is there any possibility for a complete removal of the DiskUsagePlugin? 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] [throttle-concurrents] (JENKINS-21044) Throttle Concurrent Builds blocking Jenkins queue
Michael Niestegge edited a comment on JENKINS-21044 Throttle Concurrent Builds blocking Jenkins queue I ran into the same problems now: I use Jenkins 1.547 on Debian 5.0.10 with Throttle Concurrent Builds 1.8.1 At midnight several jobs are triggered which are in the same group causing Jenkins webinterface to freeze (process at ~100% cpu). The only solution is to kill the process. After removing the plugin everything runs fine again. In my opinion the plugin is not usable as long as the error is not fixed. Switching back to 1.8 solved the issue for me. 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] [selenium] (JENKINS-18638) Selenium Plugin New Configuration error: 'config.jelly' for class hudson.plugins.selenium.configuration.browser.selenium.IEBrowser
Michael Niestegge commented on JENKINS-18638 Selenium Plugin New Configuration error: config.jelly for class hudson.plugins.selenium.configuration.browser.selenium.IEBrowser I encountered the same problem. I am using Jenkins 1.521. 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.
