[JIRA] [log-parser-plugin] (JENKINS-25725) Bad performance: 10 minutes for parsing 2MB of data
rggjan created JENKINS-25725 Bad performance: 10 minutes for parsing 2MB of data Issue Type: Bug Assignee: rgoren Components: log-parser-plugin Created: 21/Nov/14 10:16 AM Description: The log parser plugin has extremely bad performance for some reason. Parsing 2MB of logs takes around 10 minutes usually (on a pretty decent server) Is this normal? Can you reproduce this? Project: Jenkins Priority: Major Reporter: rggjan 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] [log-parser-plugin] (JENKINS-25725) Bad performance: more than 5 minutes for parsing 2MB of data
rggjan updated JENKINS-25725 Bad performance: more than 5 minutes for parsing 2MB of data Change By: rggjan (21/Nov/14 10:40 AM) Summary: Badperformance: 10 morethan5 minutesforparsing2MBofdata Description: Thelogparserpluginhasextremelybadperformanceforsomereason.Parsing2MBoflogstakes around10 morethan5 minutesusually(onaprettydecentserver)Isthisnormal?Canyoureproducethis? 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] [master-slave] (JENKINS-18205) Archiving Artifacts slow with Windows JNLP Slave
rggjan commented on JENKINS-18205 Archiving Artifacts slow with Windows JNLP Slave Same problem here, happens for a linux jenkins with a Mac OS X slave. Archiving ~100MB of data takes 10 minutes, while copying it manually over the network only takes around 10 econds... 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] [master-slave] (JENKINS-18205) Archiving Artifacts slow with Windows JNLP Slave
rggjan commented on JENKINS-18205 Archiving Artifacts slow with Windows JNLP Slave Might be a duplicate of https://issues.jenkins-ci.org/browse/JENKINS-18276 ? 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-18276) Archiving artifacts from a slave node is extremely slow even with 1.509.1+
rggjan commented on JENKINS-18276 Archiving artifacts from a slave node is extremely slow even with 1.509.1+ Same problem here, happens for a linux jenkins with a Mac OS X slave. Archiving ~100MB of data takes 10 minutes, while copying it manually over the network only takes around 10 econds... Jenkins ver. 1.565.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] [project-inheritance] (JENKINS-23983) shelv project does not work for inheritance projects
rggjan created JENKINS-23983 shelv project does not work for inheritance projects Issue Type: Bug Assignee: ashlux Components: project-inheritance, shelve-project-plugin Created: 25/Jul/14 9:13 AM Description: It is not possible to shelve jobs of type inheritance project. (The "shelve project" button is missing on the project pages" However, since shelving basically means zipping up the job folder and moving it to a dedicated place on disk, I think it should be easy to add support for this new type of project. Project: Jenkins Priority: Major Reporter: rggjan 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] [project-inheritance] (JENKINS-23983) shelve project does not work for inheritance projects
rggjan updated JENKINS-23983 shelve project does not work for inheritance projects Change By: rggjan (25/Jul/14 9:13 AM) Summary: shelv shelve projectdoesnotworkforinheritanceprojects 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] [claim] (JENKINS-5359) Adopting push rather than pull model for claim
rggjan commented on JENKINS-5359 Adopting push rather than pull model for claim Ah, you're right! 7824 is what I was thinking of... thanks for the correction 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] [claim] (JENKINS-5359) Adopting push rather than pull model for claim
rggjan commented on JENKINS-5359 Adopting push rather than pull model for claim @Marc: We have the following model: Every morning in daily scrum we look at jenkins, check the broken jobs and assign them to people. However, this is not possible to do with the claim plugin, since you would have to log out and log in all the time. In this case, I think a push model would be nice, so that one person can assign whoever volunteers to fix on jenkins... what do you think? 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] [cppcheck] (JENKINS-21346) Not working with cppcheck 1.63
rggjan resolved JENKINS-21346 as Fixed Not working with cppcheck 1.63 Yes, this seems to be fixed already... maybe cppcheck 1.63.1 contained some fixes. Thanks anyway. Change By: rggjan (26/Feb/14 4:45 PM) Status: InProgress 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] [cppcheck] (JENKINS-21346) Not working with cppcheck 1.63
rggjan created JENKINS-21346 Not working with cppcheck 1.63 Issue Type: Bug Assignee: Gregory Boissinot Components: cppcheck Created: 13/Jan/14 9:52 AM Description: Running the cppcheck plugin on a report generated with cppcheck 1.63 (current stable version) gives the following error: Cppcheck Starting the cppcheck analysis. Cppcheck Processing 1 files with the pattern 'cppcheck.xml'. Cppcheck Parsing throws exceptions. org.jenkinsci.plugins.cppcheck.model.Error cannot be cast to org.jenkinsci.plugins.cppcheck.model.Results Build step 'Publish Cppcheck results' changed build result to FAILURE Build step 'Publish Cppcheck results' marked build as failure It works fine with cppcheck 1.62 Project: Jenkins Priority: Blocker Reporter: rggjan 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] [email-ext] (JENKINS-21041) Impossible to keeps sending mails to people who broke the build
rggjan commented on JENKINS-21041 Impossible to keeps sending mails to people who broke the build I think thats not working because "Failed" triggers every time it fails, so "Failed" and "Still Failing" are triggered for following commits... 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] [email-ext] (JENKINS-21041) Impossible to keeps sending mails to people who broke the build
rggjan commented on JENKINS-21041 Impossible to keeps sending mails to people who broke the build I see... so any chance this can get implemented? Do you think its a lot of work? 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] [email-ext] (JENKINS-21041) Impossible to keeps sending mails to people who broke the build
rggjan commented on JENKINS-21041 Impossible to keeps sending mails to people who broke the build No, I would definitively not change the behaviour! I think it should be another option, so you can set something like: Trigger: "Failure" Send to: "Build breaker" (instead of only "Recipients", "Developers", ...) I actually thought that setting it to "Culprits" would do exactly what I proposed, but somehow this works differently. What does the "Culprits" checkbox do? Shouldn't the "Culprits" be exactly the persons who broke the build in the first place? 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] [email-ext] (JENKINS-21040) No trigger for Stable - Unstable
rggjan created JENKINS-21040 No trigger for Stable - Unstable Issue Type: Bug Assignee: Alex Earl Components: email-ext Created: 17/Dec/13 1:10 PM Description: There is no trigger for "Stable" - "Unstable" It would be nice to have a trigger when the build goes from stable to unstible. Something like "1st Unstable" (similar to "1st Failure") would be perfect. Project: Jenkins Priority: Major Reporter: rggjan 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] [email-ext] (JENKINS-21041) Impossible to keeps sending mails to people who broke the build
rggjan created JENKINS-21041 Impossible to keeps sending mails to people who broke the build Issue Type: Bug Assignee: Alex Earl Components: email-ext Created: 17/Dec/13 1:15 PM Description: It would be great if the email-extension plugin could send emails for every broken build, but only to the persons that broke the build in the first place. Lets assume that person A breaks the build with commit 1. Then person B and C push commits 2 and 3. All three commits fail because of the first commit. Right now, A gets 3 mails for broken builds and B and C get 2 and 1 mail, respectively, even though B and C didn't break anything. It would be better if A gets all three mails and B and C don't get any emails until the build is stable again. Project: Jenkins Priority: Major Reporter: rggjan 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] [email-ext] (JENKINS-21041) Impossible to keeps sending mails to people who broke the build
rggjan commented on JENKINS-21041 Impossible to keeps sending mails to people who broke the build I think this would be impossible by the plugin to determine. In this case, A will keep getting emails, and A has to tell B or C to fix the code. However, I think this would be a good incentive for people to fix their broken builds fast, before other people introduce new bugs on top The problem with the current approach is that people start ignoring jenkins mails if the build is broken for too long even though they didn't do anything wrong. With the suggested approach, only people that really broke jenkins (at least once) will get annoying mails, until they managed to get it green again. 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] [maven] (JENKINS-18922) Upgrading to 1.524 (Upgrade Automatically) breaks jenkins
rggjan created JENKINS-18922 Upgrading to 1.524 (Upgrade Automatically) breaks jenkins Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: maven, plugin Created: 25/Jul/13 8:14 AM Description: When upgrading jenkins from 1.523 to 1.545, jenkins crashes. In the web interface, all I see is the error below. Restoring the old version: mv jenkins.war jenkins.war2 cp jenkins.war.bak jenkins.war makes it work again. Any idea what the problem could be? org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:246) at jenkins.InitReactorRunner.run(InitReactorRunner.java:43) at jenkins.model.Jenkins.executeReactor(Jenkins.java:906) at jenkins.model.Jenkins.init(Jenkins.java:806) at hudson.model.Hudson.init(Hudson.java:81) at hudson.model.Hudson.init(Hudson.java:77) at hudson.WebAppMain$2.run(WebAppMain.java:214) Caused by: java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.init.InitializerFinder.invoke(InitializerFinder.java:124) at hudson.init.InitializerFinder$TaskImpl.run(InitializerFinder.java:184) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:895) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:724) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at hudson.init.InitializerFinder.invoke(InitializerFinder.java:120) ... 8 more Caused by: java.lang.NoClassDefFoundError: hudson/maven/MavenModule at hudson.plugins.jobConfigHistory.JobConfigHistory.isSaveable(JobConfigHistory.java:426) at hudson.plugins.jobConfigHistory.JobConfigHistorySaveableListener.onChange(JobConfigHistorySaveableListener.java:28) at hudson.model.listeners.SaveableListener.fireOnChange(SaveableListener.java:78) at hudson.model.UpdateCenter.save(UpdateCenter.java:519) at hudson.util.PersistedList.onModified(PersistedList.java:173) at hudson.util.PersistedList.replaceBy(PersistedList.java:85) at hudson.model.UpdateCenter.load(UpdateCenter.java:533) at hudson.model.UpdateCenter.init(UpdateCenter.java:1546) ... 13 more Caused by: java.lang.ClassNotFoundException: hudson.maven.MavenModule at java.net.URLClassLoader$1.run(URLClassLoader.java:366) at java.net.URLClassLoader$1.run(URLClassLoader.java:355) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:354) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ... 21 more Environment: Archlinux, 64-bit Project: Jenkins Priority: Major Reporter: rggjan 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
[JIRA] [maven] (JENKINS-18922) Upgrading to 1.524 (Upgrade Automatically) breaks jenkins
rggjan updated JENKINS-18922 Upgrading to 1.524 (Upgrade Automatically) breaks jenkins Change By: rggjan (25/Jul/13 8:23 AM) Description: Whenupgradingjenkinsfrom1.523to1. 545 524 ,jenkinscrashes.Inthewebinterface,allIseeistheerrorbelow.Restoringtheoldversion:mvjenkins.warjenkins.war2cpjenkins.war.bakjenkins.warmakesitworkagain.Anyideawhattheproblemcouldbe?---org.jvnet.hudson.reactor.ReactorException:java.lang.Error:java.lang.reflect.InvocationTargetException atorg.jvnet.hudson.reactor.Reactor.execute(Reactor.java:246) atjenkins.InitReactorRunner.run(InitReactorRunner.java:43) atjenkins.model.Jenkins.executeReactor(Jenkins.java:906) atjenkins.model.Jenkins.init(Jenkins.java:806) athudson.model.Hudson.init(Hudson.java:81) athudson.model.Hudson.init(Hudson.java:77) athudson.WebAppMain$2.run(WebAppMain.java:214)Causedby:java.lang.Error:java.lang.reflect.InvocationTargetException athudson.init.InitializerFinder.invoke(InitializerFinder.java:124) athudson.init.InitializerFinder$TaskImpl.run(InitializerFinder.java:184) atorg.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) atjenkins.model.Jenkins$7.runTask(Jenkins.java:895) atorg.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) atorg.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) atjava.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) atjava.lang.Thread.run(Thread.java:724)Causedby:java.lang.reflect.InvocationTargetException atsun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethod) atsun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) atsun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) atjava.lang.reflect.Method.invoke(Method.java:606) athudson.init.InitializerFinder.invoke(InitializerFinder.java:120) ...8moreCausedby:java.lang.NoClassDefFoundError:hudson/maven/MavenModule athudson.plugins.jobConfigHistory.JobConfigHistory.isSaveable(JobConfigHistory.java:426) athudson.plugins.jobConfigHistory.JobConfigHistorySaveableListener.onChange(JobConfigHistorySaveableListener.java:28) athudson.model.listeners.SaveableListener.fireOnChange(SaveableListener.java:78) athudson.model.UpdateCenter.save(UpdateCenter.java:519) athudson.util.PersistedList.onModified(PersistedList.java:173) athudson.util.PersistedList.replaceBy(PersistedList.java:85) athudson.model.UpdateCenter.load(UpdateCenter.java:533) athudson.model.UpdateCenter.init(UpdateCenter.java:1546) ...13moreCausedby:java.lang.ClassNotFoundException:hudson.maven.MavenModule atjava.net.URLClassLoader$1.run(URLClassLoader.java:366) atjava.net.URLClassLoader$1.run(URLClassLoader.java:355) atjava.security.AccessController.doPrivileged(NativeMethod) atjava.net.URLClassLoader.findClass(URLClassLoader.java:354) atjava.lang.ClassLoader.loadClass(ClassLoader.java:424) atjava.lang.ClassLoader.loadClass(ClassLoader.java:357) ...21more 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] [maven] (JENKINS-18922) Upgrading to 1.524 (Upgrade Automatically) breaks jenkins
rggjan commented on JENKINS-18922 Upgrading to 1.524 (Upgrade Automatically) breaks jenkins Doing a rm -r ~/.jenkins/plugins/maven-plugin* seems to have fixed 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.
