[JIRA] [support-core] (JENKINS-24850) Collect hot threads
recampbell created JENKINS-24850 Collect hot threads Issue Type: Improvement Assignee: Steven Christou Components: support-core Created: 24/Sep/14 6:19 PM Description: Collect thread dumps from the "hottest" threads, perhaps every n minutes. Background: https://weblogs.java.net/blog/brucechapman/archive/2008/03/hot_threads.html http://java.dzone.com/news/porting-hot-thread-detector-vi Example implementation: https://github.com/elasticsearch/elasticsearch/blob/1816951b6b0320e7a011436c7c7519ec2bfabc6e/src/main/java/org/elasticsearch/monitor/jvm/HotThreads.java Sample output: https://gist.github.com/mlamp/3852210 Project: Jenkins Priority: Minor Reporter: recampbell 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-24763) Long running OldDataMonitor.doDiscard() results in thread starvation
recampbell commented on JENKINS-24763 Long running OldDataMonitor.doDiscard() results in thread starvation Latest pull request: https://github.com/jenkinsci/jenkins/pull/1402 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-24827) maven-hpi-plugin should be upgraded to Jetty 8
recampbell created JENKINS-24827 maven-hpi-plugin should be upgraded to Jetty 8 Issue Type: Improvement Assignee: Unassigned Components: core Created: 23/Sep/14 2:57 PM Description: hpi:run currently starts Jetty 6, whereas the default container for jenkins.war is Jetty 8. So we should upgrade hpi:run to launch a Jetty 8 container. Project: Jenkins Labels: jetty Priority: Minor Reporter: recampbell 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-24827) maven-hpi-plugin should be upgraded to Jetty 8
recampbell commented on JENKINS-24827 maven-hpi-plugin should be upgraded to Jetty 8 I was able to get this partially complete here: https://github.com/jenkinsci/maven-hpi-plugin/pull/11 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-24827) maven-hpi-plugin should be upgraded to Jetty 8
recampbell commented on JENKINS-24827 maven-hpi-plugin should be upgraded to Jetty 8 Discussion: https://groups.google.com/forum/#!topic/jenkinsci-dev/QCGogzAeP4Q 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] [ec2] (JENKINS-24676) Region list not being populated when keys are entered
recampbell commented on JENKINS-24676 Region list not being populated when keys are entered @Francis the problem is that you currently get an unhelpful stacktrace when you try to test the connection. My patch does not select a default region for you, it just uses a default region for the sake of the test you still must select a region. Make sense? 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] [ec2] (JENKINS-24676) Region list not being populated when keys are entered
recampbell edited a comment on JENKINS-24676 Region list not being populated when keys are entered @Francis the problem is that you currently get an unhelpful stacktrace when you try to test the connection. My patch does not select a default region for you, it just uses a default region for the sake of the test (and does not save this anywhere) you still must select a region to complete the configuration. Make sense? 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] [credentials] (JENKINS-24662) New username/password credentials screen rendering issue
recampbell resolved JENKINS-24662 as Cannot Reproduce New username/password credentials screen rendering issue It seems this only reproduces when using hpi:run Change By: recampbell (20/Sep/14 4:11 PM) Status: Open Resolved Resolution: CannotReproduce 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-24763) Long running OldDataMonitor.doDiscard() results in thread starvation
recampbell updated JENKINS-24763 Long running OldDataMonitor.doDiscard() results in thread starvation I see Jesse's point about JobConfigHistorySaveableListener it's certainly the root cause. Nevertheless, OldDataMonitor could be more robust by reducing the scope of it's lock to better handle other poorly performing SaveableListeners. So I'll change this to an Improvement if that suits you. Change By: recampbell (20/Sep/14 4:20 PM) Issue Type: Bug Improvement 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] [promoted-builds] (JENKINS-24782) Clicking Build Now on a Promotion results in a phantom, unkillable build
recampbell created JENKINS-24782 Clicking Build Now on a Promotion results in a phantom, unkillable build Issue Type: Bug Assignee: Unassigned Components: promoted-builds Created: 19/Sep/14 5:45 PM Description: If you create a promotion for a job, and then navigate to the "Promotion Status" page, and then click on the promotion itself, you will see a "Build Now" button. If you click this button, you will see a build running in the Build History window with a "null" running and estimated time. If you try to cancel the build, nothing will happen. If you go back to the Jenkins index page, you will not see the job running on an executor. You will also see this exception in the logs: https://gist.github.com/recampbell/c00b90a6ff938198 Project: Jenkins Priority: Minor Reporter: recampbell 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] [promoted-builds] (JENKINS-24782) Clicking Build Now on a Promotion results in a phantom, unkillable build
recampbell updated JENKINS-24782 Clicking Build Now on a Promotion results in a phantom, unkillable build Screenshot of phantom build Change By: recampbell (20/Sep/14 12:32 AM) Attachment: promotion.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-24763) Long running OldDataMonitor.doDiscard() results in thread starvation
recampbell updated JENKINS-24763 Long running OldDataMonitor.doDiscard() results in thread starvation Change By: recampbell (18/Sep/14 7:21 PM) Summary: LongrunningOldDataMonitor.doDiscard()resultsin livelocks threadstarvation 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-24763) Long running OldDataMonitor.doDiscard() results in thread starvation
recampbell commented on JENKINS-24763 Long running OldDataMonitor.doDiscard() results in thread starvation Pull request: https://github.com/jenkinsci/jenkins/pull/1399 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-24763) Long running OldDataMonitor.doDiscard() results in livelocks
recampbell created JENKINS-24763 Long running OldDataMonitor.doDiscard() results in livelocks Issue Type: Bug Assignee: Unassigned Components: core Created: 18/Sep/14 6:01 PM Description: A very large set of OldData can take a long time to discard. While this is running, most Jenkins operations which save any data are blocked. https://gist.github.com/recampbell/9336d3a32270e75a9333 doDiscard is synchronized and hudson.diagnosis.OldDataMonitor#remove also wants to lock OldDataMonitor most threads eventually lock when saving something, at least until the doDiscard eventually completes. Project: Jenkins Priority: Major Reporter: recampbell 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-24763) Long running OldDataMonitor.doDiscard() results in livelocks
recampbell updated JENKINS-24763 Long running OldDataMonitor.doDiscard() results in livelocks Change By: recampbell (18/Sep/14 6:02 PM) Description: AverylargesetofOldDatacantakealongtimetodiscard.Whilethisisrunning,mostJenkinsoperationswhichsaveanydataareblocked.https://gist.github.com/recampbell/9336d3a32270e75a9333doDiscardissynchronizedandhudson.diagnosis.OldDataMonitor#removealsowantstolockOldDataMonitor most .Most threadseventuallylockwhensavingsomething,atleastuntilthedoDiscardeventuallycompletes. 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-24763) Long running OldDataMonitor.doDiscard() results in livelocks
recampbell commented on JENKINS-24763 Long running OldDataMonitor.doDiscard() results in livelocks In the meantime, no build can finish, and no slaves can come online. In the incident observed, the discard was taking more than an hour and Jenkins could not complete builds or do basically any other operation. It's unacceptable for Jenkins to be inoperable for minutes at a time, hence a higher severity. I suppose this is really just "starvation' instead of a livelock per se. Will update the description. 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] [ec2] (JENKINS-24676) Region list not being populated when keys are entered
recampbell commented on JENKINS-24676 Region list not being populated when keys are entered I can reproduce this if I enter an invalid AWS secret key. I think the bug is that the test Connection action should just provide a default region if you haven't selected one. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2] (JENKINS-24676) Region list not being populated when keys are entered
recampbell commented on JENKINS-24676 Region list not being populated when keys are entered Pull request: https://github.com/jenkinsci/ec2-plugin/pull/108 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] [credentials] (JENKINS-24662) New username/password credentials screen rendering issue
recampbell created JENKINS-24662 New username/password credentials screen rendering issue Issue Type: Bug Assignee: stephenconnolly Attachments: New_Credentials__Jenkins_.png Components: credentials Created: 10/Sep/14 8:49 PM Description: If you add a new Username/Password credential, the "OK" button obscures the fields. This happens only after you change the credentials type from something else to Username/Password. Steps: 1. Click Credentials link on left 2. Click Global Credentials 3. Click Add Credentials 4. Change the 'Kind' to "Username with Password" You can work around this by scrolling the screen (perhaps by using pageup/pagedown). The root issue seems to be that "#bottom-sticker" in hudson-behavior.js needs to attach adjustSticker() on ajax-type events, such as those triggered by changing the dropDownList. Environment: core 1.579, plain-credentials 1.0, credentials 1.8.2 Project: Jenkins Labels: gui Priority: Minor Reporter: recampbell 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] [mansion-cloud] (JENKINS-23764) MansionComputer removed before build can run
recampbell created JENKINS-23764 MansionComputer removed before build can run Issue Type: Bug Assignee: Unassigned Components: mansion-cloud Created: 11/Jul/14 4:55 PM Description: In Jenkins versions 1.532, MansionComputers are terminated immediately after coming online, before they can be assigned buildable items from the queue. This happens if the computer takes longer to connect than MansionRetentionStrategy#TIMEOUT The root cause is hudson.model.Executor#getIdleStartMilliseconds() uses Computer#getConnectTime() to determine idleness if no jobs have been run. However, Computer#connectTime is set when the computer starts connecting. The solution is to track onlineTime for a MansionComputer and to use that when calculating idleness. Project: Jenkins Priority: Major Reporter: recampbell 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] [mansion-cloud] (JENKINS-23676) Nodes go offine shortly after build starts
recampbell resolved JENKINS-23676 as Fixed Nodes go offine shortly after build starts Change By: recampbell (11/Jul/14 6:56 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/d/optout.
[JIRA] [mansion-cloud] (JENKINS-23764) MansionComputer removed before build can run
recampbell resolved JENKINS-23764 as Fixed MansionComputer removed before build can run Change By: recampbell (11/Jul/14 6:57 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/d/optout.
[JIRA] [mansion-cloud] (JENKINS-23574) Provisioning hangs with no feedback if you enter a bad password
recampbell resolved JENKINS-23574 as Fixed Provisioning hangs with no feedback if you enter a bad password Change By: recampbell (03/Jul/14 8:12 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/d/optout.
[JIRA] [mansion-cloud] (JENKINS-23676) Nodes go offine shortly after build starts
recampbell created JENKINS-23676 Nodes go offine shortly after build starts Issue Type: Bug Assignee: Unassigned Components: mansion-cloud Created: 03/Jul/14 8:17 PM Description: mansion-client seems to be removing nodes shortly after they go offline. Common stack traces include: https://gist.github.com/recampbell/fc711322922a99a7b3da and more frequently: 13:43:24 FATAL: null 13:43:24 java.lang.NullPointerException 13:43:24 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:549) 13:43:24 at hudson.model.Run.execute(Run.java:1665) 13:43:24 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) 13:43:24 at hudson.model.ResourceController.execute(ResourceController.java:88) 13:43:24 at hudson.model.Executor.run(Executor.java:246) Related to CloudBees ZD-19508 Project: Jenkins Priority: Major Reporter: recampbell 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] [mansion-cloud] (JENKINS-23676) Nodes go offine shortly after build starts
recampbell updated JENKINS-23676 Nodes go offine shortly after build starts Change By: recampbell (03/Jul/14 8:41 PM) Description: mansion-clientseemstoberemovingnodesshortlyaftertheygooffline.Commonstacktracesinclude:https://gist.github.com/recampbell/fc711322922a99a7b3daandmorefrequently:13:43:24FATAL:null13:43:24java.lang.NullPointerException13:43:24athudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:549)13:43:24athudson.model.Run.execute(Run.java:1665)13:43:24athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)13:43:24athudson.model.ResourceController.execute(ResourceController.java:88)13:43:24athudson.model.Executor.run(Executor.java:246) Thebasicproblemseemstobethathudson.model.Executor#isIdlechecksifExecutor#executableisnull.ThisisassignedinasynchronizedblockinExecutor#run:217. Fundamentally,wecantcheckforidlenessandatomicallyensurethattheidlestateholds.Anycloudpluginlikelysuffersfromthisproblem,butmansion-cloudhasauniqueexposuresinceitaddsandremovesslavessoquickly. RelatedtoCloudBeesZD-19508 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] [mansion-cloud] (JENKINS-23574) Provisioning hangs with no feedback if you enter a bad password
recampbell created JENKINS-23574 Provisioning hangs with no feedback if you enter a bad password Issue Type: Bug Assignee: recampbell Components: mansion-cloud Created: 25/Jun/14 3:45 PM Description: If you enter a bad cloudbees username/password, provisioning will hang without any feedback as to the root cause (or that there's a problem at all). Due to unhandled NPE: java.lang.NullPointerException 2014-06-25_14:01:18.71274 at com.cloudbees.jenkins.plugins.mtslavescloud.MansionCloud.createAccessToken(MansionCloud.java:209) Project: Jenkins Priority: Major Reporter: recampbell 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] [subversion] (JENKINS-23541) AbstractMethodError when migrating subversion PerJobCredentialStore from 1.54 to 2.4
recampbell updated JENKINS-23541 AbstractMethodError when migrating subversion PerJobCredentialStore from 1.54 to 2.4 Change By: recampbell (24/Jun/14 4:47 PM) Description: Uponupgradingfromsubversionplugin1.54to2.4(w/credentialsplugin1.14),IreceivethisexceptiononstartupCausedby:java.lang.AbstractMethodError:hudson.scm.SubversionSCM$DescriptorImpl$Credential.toCredentials(Lhudson/model/ModelObject;Ljava/lang/String;)Lcom/cloudbees/plugins/credentials/common/StandardCredentials; athudson.scm.SubversionSCM$DescriptorImpl.migrateCredentials(SubversionSCM.java:1676) athudson.scm.PerJobCredentialStore.migrateCredentials(PerJobCredentialStore.java:109) Fullstacktrace:https://gist.github.com/recampbell/1e4b4462ada0ca6662d4 athudson.scm.SubversionSCM$DescriptorImpl.migratePerJobCredentials(SubversionSCM.java:1657) athudson.scm.SubversionSCM.perJobCredentialsMigration(SubversionSCM.java:1589) ...13more Fullstacktrace:https://gist.github.com/recampbell/1e4b4462ada0ca6662d4 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] [subversion] (JENKINS-23541) AbstractMethodError when migrating subversion PerJobCredentialStore from 1.54 to 2.4
recampbell created JENKINS-23541 AbstractMethodError when migrating subversion PerJobCredentialStore from 1.54 to 2.4 Issue Type: Bug Assignee: Unassigned Components: subversion Created: 23/Jun/14 2:42 PM Description: Upon upgrading from subversion plugin 1.54 to 2.4 (w/ credentials plugin 1.14), I receive this exception on startup Caused by: java.lang.AbstractMethodError: hudson.scm.SubversionSCM$DescriptorImpl$Credential.toCredentials(Lhudson/model/ModelObject;Ljava/lang/String;)Lcom/cloudbees/plugins/credentials/common/StandardCredentials; at hudson.scm.SubversionSCM$DescriptorImpl.migrateCredentials(SubversionSCM.java:1676) at hudson.scm.PerJobCredentialStore.migrateCredentials(PerJobCredentialStore.java:109) Full stack trace: https://gist.github.com/recampbell/1e4b4462ada0ca6662d4 at hudson.scm.SubversionSCM$DescriptorImpl.migratePerJobCredentials(SubversionSCM.java:1657) at hudson.scm.SubversionSCM.perJobCredentialsMigration(SubversionSCM.java:1589) ... 13 more Project: Jenkins Labels: subversion Priority: Major Reporter: recampbell 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] [mansion-cloud] (JENKINS-23451) Impossible to discard snapshots if VM is running
recampbell created JENKINS-23451 Impossible to discard snapshots if VM is running Issue Type: Bug Assignee: Unassigned Components: mansion-cloud Created: 16/Jun/14 6:52 PM Description: Snapshots are recorded for running virtual machines, even after you've pressed 'discard snapshots and start clean'. It's therefore impossible to discard snapshots until all virtual machines are offline a waste of time. Instead, any VM's started before the destroy date should be ignored when taking snapshots. Project: Jenkins Priority: Major Reporter: recampbell 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] [envinject] (JENKINS-19852) NPE during submission of EnvInject JobProperty configurations
recampbell reopened JENKINS-19852 NPE during submission of EnvInject JobProperty configurations Steven, I realizes this "fixes" the NPE, but I wonder if it breaks what Nicolas was trying to accomplish in 96a52696 in the first place to prevent users without RUN_SCRIPTS from editing the groovy script. Note that the groovy script is read-only without the RUN_SCRIPTS permission, but one could trivially edit the HTML to inject whatever groovy they like. So the server side check is still needed. My point is, I think we need to re-open JENKINS-19852 and let @ndeloof fix the NPE in a way which still prevents editing of the groovy in this case as desired in 96a52696. Change By: recampbell (30/May/14 9:30 PM) Resolution: Fixed Status: Resolved Reopened Assignee: GregoryBoissinot NicolasDeLoof 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] [jobconfighistory] (JENKINS-22639) Configuration for CloudSlaves Ephemeral Nodes is persisted
recampbell created JENKINS-22639 Configuration for CloudSlaves Ephemeral Nodes is persisted Issue Type: Bug Assignee: Mirko Friedenhagen Components: jobconfighistory Created: 15/Apr/14 10:51 PM Description: The jobConfigHistory plugin tracks changes to AbstractCloudSlaves and EphemeralNodes. This can cause high load and high memory usage. These slaves should simply not be tracked. Project: Jenkins Priority: Major Reporter: recampbell 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] [jobconfighistory] (JENKINS-22639) Configuration for CloudSlaves Ephemeral Nodes is persisted
recampbell updated JENKINS-22639 Configuration for CloudSlaves Ephemeral Nodes is persisted Change By: recampbell (15/Apr/14 11:02 PM) Labels: performance 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-22421) File descriptor leak - changelog.xml
recampbell closed JENKINS-22421 as Not A Defect File descriptor leak - changelog.xml Change By: recampbell (31/Mar/14 1:40 PM) Status: Open Closed Resolution: NotADefect 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-22421) File descriptor leak - changelog.xml
recampbell commented on JENKINS-22421 File descriptor leak - changelog.xml It turns out that these were not leaks, it was just a case of a spider going through user/*/builds which was causing excessive parsing of changelogs. 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-22421) File descriptor leak - changelog.xml
recampbell created JENKINS-22421 File descriptor leak - changelog.xml Issue Type: Bug Assignee: Unassigned Components: core Created: 30/Mar/14 9:12 PM Description: Jenkins is occasionally failing to load the index page and complains about "Too many open files". Looking at the open files, I see around 7000 such as this one: //jenkins/jenkins_home/jobs//jobs/messages/builds/2012-08-16_03-38-51/changelog.xml This is a rather large public Jenkins instance which is no doubt crawled by search engines. Environment: 1.532.2 Project: Jenkins Priority: Major Reporter: recampbell 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] [artifactory] (JENKINS-22341) Failure to connect to artifactory server break configuration page
recampbell updated JENKINS-22341 Failure to connect to artifactory server break configuration page Change By: recampbell (26/Mar/14 1:07 PM) Labels: performance 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] [sauce-ondemand] (JENKINS-22245) Saucelabs.com outage causes Jenkins outage when using SauceBadgeColumn
recampbell created JENKINS-22245 Saucelabs.com outage causes Jenkins outage when using SauceBadgeColumn Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: sauce-ondemand Created: 18/Mar/14 2:22 PM Description: If your main view has the SauceBadgeColumn, a saucelabs.com outage will cause a Jenkins outage. As of Tue Mar 18 14:20:31 UTC 2014, saucelabs.com is not responding (seems well-hung). This causes Jenkins to hang. An easy fix is to add a read timeout and handle that failure gracefully. Thread dump: 2014-03-18_14:09:48.10898 "Handling GET / : http-8084-3" daemon prio=10 tid=0x7fbac404b800 nid=0x1986 runnable 0x7fbad53b 2014-03-18_14:09:48.10899java.lang.Thread.State: RUNNABLE 2014-03-18_14:09:48.10900 at java.net.SocketInputStream.socketRead0(Native Method) 2014-03-18_14:09:48.10900 at java.net.SocketInputStream.read(Unknown Source) 2014-03-18_14:09:48.10901 at java.net.SocketInputStream.read(Unknown Source) 2014-03-18_14:09:48.10902 at sun.security.ssl.InputRecord.readFully(Unknown Source) 2014-03-18_14:09:48.10902 at sun.security.ssl.InputRecord.read(Unknown Source) 2014-03-18_14:09:48.10903 at sun.security.ssl.SSLSocketImpl.readRecord(Unknown Source) 2014-03-18_14:09:48.10903 - locked 0xfcb17420 (a java.lang.Object) 2014-03-18_14:09:48.10904 at sun.security.ssl.SSLSocketImpl.readDataRecord(Unknown Source) 2014-03-18_14:09:48.10904 at sun.security.ssl.AppInputStream.read(Unknown Source) 2014-03-18_14:09:48.10905 - locked 0xfcb256a8 (a sun.security.ssl.AppInputStream) 2014-03-18_14:09:48.10905 at java.io.BufferedInputStream.fill(Unknown Source) 2014-03-18_14:09:48.10906 at java.io.BufferedInputStream.read1(Unknown Source) 2014-03-18_14:09:48.10906 at java.io.BufferedInputStream.read(Unknown Source) 2014-03-18_14:09:48.10907 - locked 0xfcba7340 (a java.io.BufferedInputStream) 2014-03-18_14:09:48.10908 at sun.net.www.http.HttpClient.parseHTTPHeader(Unknown Source) 2014-03-18_14:09:48.10909 at sun.net.www.http.HttpClient.parseHTTP(Unknown Source) 2014-03-18_14:09:48.10909 at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source) 2014-03-18_14:09:48.10910 - locked 0xfcb13910 (a sun.net.www.protocol.https.DelegateHttpsURLConnection) 2014-03-18_14:09:48.10910 at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(Unknown Source) 2014-03-18_14:09:48.10911 - locked 0xfcb13890 (a sun.net.www.protocol.https.HttpsURLConnectionImpl) 2014-03-18_14:09:48.10911 at com.saucelabs.saucerest.SauceREST.retrieveResults(SauceREST.java:140) 2014-03-18_14:09:48.10912 at com.saucelabs.saucerest.SauceREST.retrieveResults(SauceREST.java:117) 2014-03-18_14:09:48.10912 at hudson.plugins.sauce_ondemand.SauceBadgeColumn.getSauceUser(SauceBadgeColumn.java:59) 2014-03-18_14:09:48.10913 at sun.reflect.GeneratedMethodAccessor358.invoke(Unknown Source) 2014-03-18_14:09:48.10913 at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) 2014-03-18_14:09:48.10914 at java.lang.reflect.Method.invoke(Unknown Source) Project: Jenkins Priority: Critical Reporter: recampbell 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
[JIRA] [sauce-ondemand] (JENKINS-22245) Saucelabs.com outage causes Jenkins outage when using SauceBadgeColumn
recampbell commented on JENKINS-22245 Saucelabs.com outage causes Jenkins outage when using SauceBadgeColumn A related pull request which would migate this problem: https://github.com/saucelabs/saucerest-java/pull/8 Unfortunately, if saucelabs.com goes down, most people would still pin the blame on Jenkins if they didn't look at the stack trace. So I think this badge really needs to be asynchronous, perhaps loaded as an image from an action hanging off the build vs. calling saucelabs.com when rendering the html. 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] [disk-usage] (JENKINS-21003) ProjectDiskUsageAction.getBuildsDiskUsageAllSubItems breaks lazy-loading
recampbell commented on JENKINS-21003 ProjectDiskUsageAction.getBuildsDiskUsageAllSubItems breaks lazy-loading Same problem here. CPU was at 200% thanks to about 27 threads trying to calculate disk usage for the same project. Disabling the disk-usage plugin fixed the issue. I think this is critical to fix because it's problems like this that give Jenkins a bad name. 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-21881) Make X-Frame-Options configurable
recampbell created JENKINS-21881 Make X-Frame-Options configurable Issue Type: New Feature Affects Versions: current Assignee: Unassigned Components: core Created: 19/Feb/14 4:54 PM Description: Jenkins 1.532.2 sets X-Frame-Options to sameorigin |https://github.com/cloudbees/hudson/commit/16931bd7bf7560e26ef98328b8e95e803d0e90f6]. While this prevents attacks via frame embedding, it also prevents any desirable embedding of Jenkins in a frame. This should be configurable "somehow." Either via an extension point, or allowing PageDecorators to set the header property by changing the order of layout.jelly. Project: Jenkins Labels: lts-candidate Priority: Minor Reporter: recampbell 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] [rubyMetrics] (JENKINS-21614) rcov Reports Waste Memory and Hurt Performance
recampbell updated JENKINS-21614 rcov Reports Waste Memory and Hurt Performance Change By: recampbell (02/Feb/14 2:18 PM) Labels: memory 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] [rubyMetrics] (JENKINS-21614) rcov Reports Waste Memory and Hurt Performance
recampbell created JENKINS-21614 rcov Reports Waste Memory and Hurt Performance Issue Type: Bug Assignee: david_calavera Components: rubyMetrics Created: 02/Feb/14 2:17 PM Description: The rubyMetrics plugin's rcov embeds the entire source code of the project into the build.xml (hudson.plugins.rubyMetrics.rcov.RcovBuildAction.results.files) https://github.com/jenkinsci/rubymetrics-plugin/blob/master/src/main/java/hudson/plugins/rubyMetrics/rcov/model/RcovResult.java#L9 This results 1 in a 37 mb build.xml and a 576mb DOM 2. 1 For a project with 179034 LOC over 1500 files. 2 As measured from a heap dump Project: Jenkins Priority: Major Reporter: recampbell 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-20568) Failed to archive artifacts due to Unexpected end of ZLIB input stream / Failed to execute command Pipe.EOF(17)
recampbell created JENKINS-20568 Failed to archive artifacts due to Unexpected end of ZLIB input stream / Failed to execute command Pipe.EOF(17) Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 13/Nov/13 4:30 PM Description: A build consistently fails with this error: 16:04:06 Archiving artifacts 16:04:10 ERROR: Failed to archive artifacts: tmp/README.html,generated/* 16:04:10 hudson.util.IOException2: Failed to extract /scratch/jenkins/workspace/cloudbees-xxx/tmp/README.html,generated/* In the Jenkins console logs, I see this error: 2013-11-13_16:04:07.70268 SEVERE: Failed to execute command Pipe.EOF(17) (channel 5d0b8895) 2013-11-13_16:04:07.70268 java.lang.NullPointerException 2013-11-13_16:04:07.70269 at hudson.remoting.ProxyWriter$EOF.execute(ProxyWriter.java:177) 2013-11-13_16:04:07.70270 at hudson.remoting.Channel$2.handle(Channel.java:461) 2013-11-13_16:04:07.70271 at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Complete logs: https://gist.github.com/recampbell/aa8ed59bf8892bb3c68c I see some reports for this error (the "Failed to execute command Pipe.EOF") indicating that it might be a slave.jar compatibility problem, but I'm using SSH slaves and the slave.jar is copied over each time according to the logs. Project: Jenkins Priority: Major Reporter: recampbell 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] [disk-usage] (JENKINS-18872) Disk usage plugin doesn't show usage by promotions
recampbell created JENKINS-18872 Disk usage plugin doesnt show usage by promotions Issue Type: Bug Assignee: vjuranek Components: disk-usage, promoted-builds Created: 22/Jul/13 3:33 PM Description: The disk used by a job's promotions is not included in disk usage calculated for a promotion. I have a job which disk-usage reports 200MB of builds, but du -hs hudson/home/job name reports as 3.6GB. The 'promotions' folder in this plugin consumes 3GB thereof (mostly in the workspace folder). Environment: 1.509.2 Project: Jenkins Priority: Major Reporter: recampbell 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] [promoted-builds] (JENKINS-18873) No way to delete promoted-builds from GUI
recampbell created JENKINS-18873 No way to delete promoted-builds from GUI Issue Type: Bug Assignee: Unassigned Components: promoted-builds Created: 22/Jul/13 3:41 PM Description: The promoted-builds plugin creates a directory called 'promotions' in the job's root directory. There is no way to browse the list of 'builds' for a given promotion, so as to delete them. This, confounded by the inability to see disk-usage of a promotion (JENKINS-18872), makes disk management almost impossible, except from the command line. Project: Jenkins Priority: Major Reporter: recampbell 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] [promoted-builds] (JENKINS-18873) No way to delete promoted-builds from GUI
recampbell edited a comment on JENKINS-18873 No way to delete promoted-builds from GUI (removed) 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] [promoted-builds] (JENKINS-18873) No way to delete promoted-builds from GUI
recampbell commented on JENKINS-18873 No way to delete promoted-builds from GUI Likewise, you can't see how much disk a promotion's 'workspace' is using. 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] [config-file-provider] (JENKINS-15976) Provided maven settings.xml in maven builder is lost
recampbell resolved JENKINS-15976 as Fixed Provided maven settings.xml in maven builder is lost 40f3b095a claims to have fixed this issue, but was not automatically done for some reason. Change By: recampbell (17/Jul/13 7:19 PM) Status: Reopened Resolved Fix Version/s: current 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] [core] (JENKINS-7291) Flyweight jobs and zero executors
recampbell reopened JENKINS-7291 Flyweight jobs and zero executors This doesn't resolve the issue for me. I see the master computer, but it is not used for the main matrix job. Instead, a cloud slave is provisioned. Steps to repro: 1. Create a matrix job with a single configuration, no labels 2. Ensure that Jenkins.numExecutors = 0 3. Ensure that a cloud plugin can provision slaves 4. Run the matrix job The matrix job won't run on the master, but will result in a slave being provisioned. Change By: recampbell (12/Jul/13 5:04 PM) Resolution: Fixed Status: Resolved Reopened 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-7291) Flyweight jobs and zero executors
recampbell resolved JENKINS-7291 as Fixed Flyweight jobs and zero executors Sorry, my mistake in backporting. Change By: recampbell (12/Jul/13 6:17 PM) Status: Reopened 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] [core] (JENKINS-18718) It isn't clear if you should restart Jenkins after installing a plugin
recampbell created JENKINS-18718 It isnt clear if you should restart Jenkins after installing a plugin Issue Type: Bug Assignee: Unassigned Components: core Created: 11/Jul/13 5:29 PM Description: When you install a plugin, you are given two choices: "install without restart" or "Download and Install after restart"? However, it isn't clear what the right option is. It seems you must know something about Jenkins internals or the internals of plugin you're installing. Project: Jenkins Priority: Major Reporter: recampbell 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] (JENKINS-14616) Corrupted plugin updates leads to plugin uninstall and lost job configuration
recampbell commented on JENKINS-14616 Corrupted plugin updates leads to plugin uninstall and lost job configuration Could be done from an implementation of hudson.model.UpdateCenter.UpdateCenterConfiguration's postValidate(DownloadJob job, File src) 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] (JENKINS-14901) Emulator start failed on Ubuntu (SDK 20.0.3)
recampbell commented on JENKINS-14901 Emulator start failed on Ubuntu (SDK 20.0.3) We were having this precise issue. As indicated by this stackoverflow thread, we fixed the issue by setting the LD_LIBRARY_PATH as follows (using EnvInject): LD_LIBRARY_PATH=/opt/android/android-sdk-linux/tool/lib I think the fix is for the Android Emulator plugin to populate this for us? 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] (JENKINS-7291) Flyweight jobs and zero executors
recampbell commented on JENKINS-7291 Flyweight jobs and zero executors It would be nice if one could allow flyweight tasks on master even when no executors are 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/groups/opt_out.
[JIRA] (JENKINS-16936) Extension point for secure users of Api
recampbell assigned JENKINS-16936 to recampbell Extension point for secure users of Api Change By: recampbell (22/Feb/13 8:34 PM) Assignee: recampbell 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] (JENKINS-16844) Triggering a build from the context menu produces a warning when security is enabled
recampbell updated JENKINS-16844 Triggering a build from the context menu produces a warning when security is enabled My suggested patch for this. It just verifies that the referrer is the same host as what Jenkins is listening to. Change By: recampbell (21/Feb/13 10:48 PM) Attachment: allow-local-build.patch 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] (JENKINS-15632) Cache android emulator snapshots on master
recampbell created JENKINS-15632 Cache android emulator snapshots on master Issue Type: Bug Assignee: Christopher Orr Components: android-emulator Created: 25/Oct/12 8:48 PM Description: Android emulator snapshots are stored on the slave in the user's home directory. It would be nice if these could be optionally archived on to the Jenkins master so if the same emulator is required for subsequent builds, the snapshot could just be retrieved from the master, saving several minutes of time. This is especially important when slaves are short-lived, or builds move around alot. Project: Jenkins Priority: Major Reporter: recampbell 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] (JENKINS-15633) Android emulator should have a video capture option
recampbell created JENKINS-15633 Android emulator should have a video capture option Issue Type: Bug Assignee: Christopher Orr Components: android-emulator Created: 25/Oct/12 8:52 PM Description: The android emulator should allow you to retain video output from the emulator, so that you can watch it in your webbrowser after the build completes. Even cooler is an extension point which allows you to annotate events in the video (like when running a test). Project: Jenkins Priority: Major Reporter: recampbell 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] (JENKINS-15537) Target ABI field doesn't handle Token Expansion
recampbell created JENKINS-15537 Target ABI field doesnt handle Token Expansion Issue Type: Bug Assignee: Christopher Orr Attachments: android_token.png Components: android-emulator Created: 16/Oct/12 4:12 PM Description: When creating a matrix build we have a parameter called "target-abi". However, when Jenkins validates the form it shows an error for this field, even though it doesn't display an error for other parameterized emulator arguments. Furthermore, this setting is not expanded when running from the command line: android /opt/android/android-sdk-linux/tools/android create avd -f -a -c 512M -s WVGA800 -n hudson_en-US_160_WVGA_android-16 -t android-16 --abi $target-abi Error: Unable to find a 'userdata.img' file for ABI $target-abi to copy into the AVD folder. Project: Jenkins Priority: Major Reporter: recampbell 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] (JENKINS-15537) Target ABI field doesn't handle Token Expansion
recampbell updated JENKINS-15537 Target ABI field doesnt handle Token Expansion Change By: recampbell (16/Oct/12 4:13 PM) Attachment: android_token.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
[JIRA] (JENKINS-12271) Jenkins DoS's itself with ajax checks from job/*/configure with large workspace
recampbell resolved JENKINS-12271 as Duplicate Jenkins DoSs itself with ajax checks from job/*/configure with large workspace Duplicates JENKINS-7214 Change By: recampbell (09/Oct/12 10:55 PM) Status: Open Resolved Resolution: Duplicate 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] (JENKINS-15379) Emulator plugin occasionally hangs
recampbell created JENKINS-15379 Emulator plugin occasionally hangs Issue Type: Bug Assignee: Christopher Orr Components: android-emulator Created: 02/Oct/12 2:40 PM Description: We're seeing the android emulator occasionally hang trying to start up. For example: https://gist.github.com/52b5207b7b1dfe768b0c where we see: 00:08:08 $ /opt/android/android-sdk-linux/platform-tools/adb -s localhost:33298 logcat -v time 00:08:46 $ /opt/android/android-sdk-linux/platform-tools/adb connect localhost:33298 00:08:46 android Attempting to unlock emulator screen 00:08:46 $ /opt/android/android-sdk-linux/platform-tools/adb -s localhost:33298 shell input keyevent 82 08:05:15 Build timed out due to Global Timeout (after 480 minutes). Marking the build as aborted. Can the plugin attempt to send these keys again after some timeout? Environment: linux 64bit Project: Jenkins Priority: Major Reporter: recampbell 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] (JENKINS-15223) One user can overwhelm jenkins via ArtifactArchiver.doCheckArtifacts()
recampbell created JENKINS-15223 One user can overwhelm jenkins via ArtifactArchiver.doCheckArtifacts() Issue Type: Bug Assignee: Unassigned Components: core Created: 18/Sep/12 4:39 PM Description: If a job has a very large workspace, and a very permissive artifact _expression_ (like */.jar), a user can single handledly bring down a Jenkins instance by tabbing in and out of the artifact field. Each time the user tabs out of the field, Jenkins does an ajax post, resultining in a recursive search of the filesystem. Jenkins should be smart enough to cancel previous ajax requests for validating the artifact glob _expression_, or use some other approach to prevent the entire system from going down. Project: Jenkins Priority: Major Reporter: recampbell 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] (JENKINS-15097) Expecting integer when it can be a float or even a string
recampbell commented on JENKINS-15097 Expecting integer when it can be a float or even a string We are also seeing this problem after upgrading to the latest Android SDK. 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] (JENKINS-15097) Expecting integer when it can be a float or even a string
recampbell edited a comment on JENKINS-15097 Expecting integer when it can be a float or even a string We are also seeing this problem after upgrading to the latest Android SDK. The message we see is a little different, though: FATAL: Could not parse 21 rc4 java.lang.NumberFormatException: Could not parse 21 rc4 at hudson.plugins.android_emulator.util.Utils.parseRevisionString(Utils.java:607) at hudson.plugins.android_emulator.util.Utils$2.call(Utils.java:192) at hudson.plugins.android_emulator.util.Utils$2.call(Utils.java:161) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:287) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) 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] (JENKINS-15097) Expecting integer when it can be a float or even a string
recampbell
edited a comment on JENKINS-15097
Expecting integer when it can be a float or even a string
We are also seeing this problem after upgrading to the latest Android SDK. The message we see is a little different, though:
FATAL: Could not parse 21 rc4
java.lang.NumberFormatException: Could not parse 21 rc4
at hudson.plugins.android_emulator.util.Utils.parseRevisionString(Utils.java:607)
at hudson.plugins.android_emulator.util.Utils$2.call(Utils.java:192)
at hudson.plugins.android_emulator.util.Utils$2.call(Utils.java:161)
It seems like the problem is in hudson.plugins.android_emulator.util.Utils:
private static final Pattern REVISION = Pattern.compile("(\\d+)(?:\\.d+){0,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
[JIRA] (JENKINS-15097) Expecting integer when it can be a float or even a string
recampbell
edited a comment on JENKINS-15097
Expecting integer when it can be a float or even a string
We are also seeing this problem after upgrading to the latest Android SDK. We are using v2.3 of the plugin.
The message we see is a little different, though:
FATAL: Could not parse 21 rc4
java.lang.NumberFormatException: Could not parse 21 rc4
at hudson.plugins.android_emulator.util.Utils.parseRevisionString(Utils.java:607)
at hudson.plugins.android_emulator.util.Utils$2.call(Utils.java:192)
at hudson.plugins.android_emulator.util.Utils$2.call(Utils.java:161)
It seems like the problem is in hudson.plugins.android_emulator.util.Utils:
private static final Pattern REVISION = Pattern.compile("(\\d+)(?:\\.d+){0,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
[JIRA] (JENKINS-14515) Malformed PATH environment variable on Windows slave (unix syntax used)
recampbell commented on JENKINS-14515 Malformed PATH environment variable on Windows slave (unix syntax used) Is the job running on the master? If not, what is the OS of the 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
[JIRA] (JENKINS-14392) Optional Extensions are reloaded when dependencies are dynamically loaded
recampbell created JENKINS-14392 Optional Extensions are reloaded when dependencies are dynamically loaded Issue Type: Bug Assignee: Unassigned Components: core Created: 11/Jul/12 5:36 PM Description: If a plugin A has an optional dependency on plugin B, and has marked an @Extension (optional=true), Jenkins will properly fail to load that extension. However, if plugin B is then later installed, the optional dependencies from plugin A are not re-evaluated. Jenkins should keep track of optional extensions which failed to load, and retry them when new plugins are installed. Perhaps it could only due so if the plugin for that extension expressed an optional dependency on the newly installed plugin, but even that doesn't seem necessary? This is really just a usability issue (since you can restart to fix it), but may prove frustrating for novice users. Project: Jenkins Priority: Major Reporter: recampbell 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] (JENKINS-14374) Not installing promotions plugin results in empty/lost builds
recampbell created JENKINS-14374 Not installing promotions plugin results in empty/lost builds Issue Type: Bug Assignee: Unassigned Components: appaloosa Created: 10/Jul/12 4:50 PM Description: If you don't install the promotions plugin, your console log will sometimes be blank, and your the build.xml for each build will not be saved, resulting in lost data. In the logs, you will see this error: Jul 10, 2012 4:08:04 PM hudson.model.Executor run SEVERE: Executor threw an exception java.lang.NoClassDefFoundError: hudson/plugins/promoted_builds/JobPropertyImpl at org.jenkins.plugins.appaloosa.AppaloosaRunListener.onCompleted(AppaloosaRunListener.java:47) at org.jenkins.plugins.appaloosa.AppaloosaRunListener.onCompleted(AppaloosaRunListener.java:42) at hudson.model.listeners.RunListener.fireCompleted(RunListener.java:178) at hudson.model.Run.run(Run.java:1458) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) Rating this as critical since it results in data loss. Project: Jenkins Priority: Critical Reporter: recampbell 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] (JENKINS-13936) Fitnesse results parsing uses too much heap
recampbell created JENKINS-13936:
Summary: Fitnesse results parsing uses too much heap
Key: JENKINS-13936
URL: https://issues.jenkins-ci.org/browse/JENKINS-13936
Project: Jenkins
Issue Type: Bug
Components: fitnesse
Reporter: recampbell
We are seeing OOME's in Jenkins when parsing large Fitnesse results files
(35mb). For example:
{quote}
Reading results as US-ASCII from /.../fitnesse-result.xml
Parsing results...
java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Arrays.java:2882)
at
java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:100)
at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:515)
at java.lang.StringBuffer.append(StringBuffer.java:306)
at
com.sun.org.apache.xalan.internal.xsltc.runtime.StringValueHandler.characters(StringValueHandler.java:49)
at
com.sun.org.apache.xml.internal.utils.FastStringBuffer.sendSAXcharacters(FastStringBuffer.java:998)
at
com.sun.org.apache.xml.internal.dtm.ref.sax2dtm.SAX2DTM2.dispatchCharactersEvents(SAX2DTM2.java:3068)
at
com.sun.org.apache.xalan.internal.xsltc.dom.SAXImpl.characters(SAXImpl.java:1562)
at
com.sun.org.apache.xalan.internal.xsltc.dom.DOMAdapter.characters(DOMAdapter.java:330)
at GregorSamsa.template$dot$2()
at GregorSamsa.applyTemplates()
at GregorSamsa.template$dot$0()
at GregorSamsa.applyTemplates()
at GregorSamsa.applyTemplates()
at GregorSamsa.transform()
at
com.sun.org.apache.xalan.internal.xsltc.runtime.AbstractTranslet.transform(AbstractTranslet.java:603)
at
com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:709)
at
com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:313)
at
hudson.plugins.fitnesse.NativePageCountsParser.transformRawResults(NativePageCountsParser.java:25)
at
hudson.plugins.fitnesse.NativePageCountsParser.parse(NativePageCountsParser.java:17)
at
hudson.plugins.fitnesse.FitnesseResultsRecorder.getResults(FitnesseResultsRecorder.java:131)
at
hudson.plugins.fitnesse.FitnesseResultsRecorder.getResults(FitnesseResultsRecorder.java:109)
at
hudson.plugins.fitnesse.FitnesseResultsRecorder.perform(FitnesseResultsRecorder.java:73)
at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:705)
at
hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:680)
at
hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:658)
at hudson.model.Build$RunnerImpl.post2(Build.java:161)
at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:627)
at hudson.model.Run.run(Run.java:1400)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
Build step 'Publish Fitnesse results report' changed build result to FAILURE
Build step 'Publish Fitnesse results report' marked build as failure
{quote}
Perhaps it would be more efficient to use a streaming parser like SAX?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13936) Fitnesse results parsing uses too much heap
[
https://issues.jenkins-ci.org/browse/JENKINS-13936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
recampbell updated JENKINS-13936:
-
Description:
We are seeing OOME's in Jenkins when parsing large Fitnesse results files
(35mb). For example:
{quote}
Reading results as US-ASCII from /.../fitnesse-result.xml
Parsing results...
java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Arrays.java:2882)
at
java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:100)
at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:515)
at java.lang.StringBuffer.append(StringBuffer.java:306)
at
com.sun.org.apache.xalan.internal.xsltc.runtime.StringValueHandler.characters(StringValueHandler.java:49)
at
com.sun.org.apache.xml.internal.utils.FastStringBuffer.sendSAXcharacters(FastStringBuffer.java:998)
at
com.sun.org.apache.xml.internal.dtm.ref.sax2dtm.SAX2DTM2.dispatchCharactersEvents(SAX2DTM2.java:3068)
at
com.sun.org.apache.xalan.internal.xsltc.dom.SAXImpl.characters(SAXImpl.java:1562)
at
com.sun.org.apache.xalan.internal.xsltc.dom.DOMAdapter.characters(DOMAdapter.java:330)
at GregorSamsa.template$dot$2()
at GregorSamsa.applyTemplates()
at GregorSamsa.template$dot$0()
at GregorSamsa.applyTemplates()
at GregorSamsa.applyTemplates()
at GregorSamsa.transform()
at
com.sun.org.apache.xalan.internal.xsltc.runtime.AbstractTranslet.transform(AbstractTranslet.java:603)
at
com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:709)
at
com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:313)
at
hudson.plugins.fitnesse.NativePageCountsParser.transformRawResults(NativePageCountsParser.java:25)
at
hudson.plugins.fitnesse.NativePageCountsParser.parse(NativePageCountsParser.java:17)
at
hudson.plugins.fitnesse.FitnesseResultsRecorder.getResults(FitnesseResultsRecorder.java:131)
at
hudson.plugins.fitnesse.FitnesseResultsRecorder.getResults(FitnesseResultsRecorder.java:109)
at
hudson.plugins.fitnesse.FitnesseResultsRecorder.perform(FitnesseResultsRecorder.java:73)
at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:705)
at
hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:680)
at
hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:658)
at hudson.model.Build$RunnerImpl.post2(Build.java:161)
at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:627)
at hudson.model.Run.run(Run.java:1400)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
Build step 'Publish Fitnesse results report' changed build result to FAILURE
Build step 'Publish Fitnesse results report' marked build as failure
{quote}
I'm fairly certain this OOME is due to memory usage by this parsing since we
don't see OOME at any other time, and there is plenty of memory usually
available according to our monitoring.
was:
We are seeing OOME's in Jenkins when parsing large Fitnesse results files
(35mb). For example:
{quote}
Reading results as US-ASCII from /.../fitnesse-result.xml
Parsing results...
java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Arrays.java:2882)
at
java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:100)
at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:515)
at java.lang.StringBuffer.append(StringBuffer.java:306)
at
com.sun.org.apache.xalan.internal.xsltc.runtime.StringValueHandler.characters(StringValueHandler.java:49)
at
com.sun.org.apache.xml.internal.utils.FastStringBuffer.sendSAXcharacters(FastStringBuffer.java:998)
at
com.sun.org.apache.xml.internal.dtm.ref.sax2dtm.SAX2DTM2.dispatchCharactersEvents(SAX2DTM2.java:3068)
at
com.sun.org.apache.xalan.internal.xsltc.dom.SAXImpl.characters(SAXImpl.java:1562)
at
com.sun.org.apache.xalan.internal.xsltc.dom.DOMAdapter.characters(DOMAdapter.java:330)
at GregorSamsa.template$dot$2()
at GregorSamsa.applyTemplates()
at GregorSamsa.template$dot$0()
at GregorSamsa.applyTemplates()
at GregorSamsa.applyTemplates()
at GregorSamsa.transform()
at
com.sun.org.apache.xalan.internal.xsltc.runtime.AbstractTranslet.transform(AbstractTranslet.java:603)
at
com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:709)
at
com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:313)
at
hudson.plugins.fitnesse.NativePageCountsParser.transformRawResults(NativePageCountsParser.java:25)
at
hudson.plugins.fitnesse.NativePageCountsParser.parse(NativePageCountsParser.java:17)
at
[JIRA] (JENKINS-10840) Maven module shows as running after build is aborted.
[ https://issues.jenkins-ci.org/browse/JENKINS-10840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161903#comment-161903 ] recampbell commented on JENKINS-10840: -- I see this too, in 1.424.5. Maven module shows as running after build is aborted. --- Key: JENKINS-10840 URL: https://issues.jenkins-ci.org/browse/JENKINS-10840 Project: Jenkins Issue Type: Bug Components: maven2 Environment: Jenkins 1.418 Reporter: Christian Höltje I have a Maven 2 job that has a single 'module'. It is set to auto-abort if it lasts more than 15 minutes. If it does abort, then the module for that build shows still running for example, I have some that say the module has been running for days. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10840) Maven module shows as running after build is aborted.
[ https://issues.jenkins-ci.org/browse/JENKINS-10840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] recampbell reassigned JENKINS-10840: Assignee: olamy Olivier, Any thoughts on this? Maven module shows as running after build is aborted. --- Key: JENKINS-10840 URL: https://issues.jenkins-ci.org/browse/JENKINS-10840 Project: Jenkins Issue Type: Bug Components: maven2 Environment: Jenkins 1.418 Reporter: Christian Höltje Assignee: olamy I have a Maven 2 job that has a single 'module'. It is set to auto-abort if it lasts more than 15 minutes. If it does abort, then the module for that build shows still running for example, I have some that say the module has been running for days. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8666) Matrix project index page broken by axis with empty values
[ https://issues.jenkins-ci.org/browse/JENKINS-8666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] recampbell updated JENKINS-8666: Summary: Matrix project index page broken by axis with empty values (was: Can't add axis to multi-configuration project) Matrix project index page broken by axis with empty values -- Key: JENKINS-8666 URL: https://issues.jenkins-ci.org/browse/JENKINS-8666 Project: Jenkins Issue Type: Bug Components: core Affects Versions: current Environment: Windows XP Pro SP3, Java(TM) SE Runtime Environment (build 1.6.0_23-b05), Intel Pentium 4 Reporter: Dan Puza EDIT: The exception appears to be triggered by the axis Values field being left empty when saving. I didn't know what to enter for that field, in what format. Something like... var1=C:\Documents and Settings var2=C:\WINDOWS ??? EDIT: I see how this works now, something like: Axis1 - x86 x64 Axis2 - Debug Release It would be nice to include an example in the help text, and to handle an empty value gracefully rather than an unhandled exception thrown. Steps to reproduce: 1. Clean install of Jenkins 1.396 as a Windows service. 2. Create a new multi-configuration project job. 3. Don't touch any setting except name. 4. At this point, can either 4a. Save and Configure again. OR, 4b. Simply continue to step 5. 5. Add axis, enter name. 6. Save. 7. Get the following exception: Status Code: 500 Exception: Stacktrace: org.apache.commons.jelly.JellyTagException: jar:file:/C:/WINDOWS/system32/config/systemprofile/.hudson/war/WEB-INF/lib/jenkins-core-1.396.jar!/lib/hudson/project/matrix.jelly:49:52: java.util.NoSuchElementException at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:709) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:282) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.WhenTag.doTag(WhenTag.java:46) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.WhenTag.doTag(WhenTag.java:46) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:63) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:146) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at
[JIRA] (JENKINS-9041) Analysis Core / SSL Problem
[ https://issues.jenkins-ci.org/browse/JENKINS-9041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159167#comment-159167 ] recampbell commented on JENKINS-9041: - I can confirm this solves the issue for me as well. Analysis Core / SSL Problem --- Key: JENKINS-9041 URL: https://issues.jenkins-ci.org/browse/JENKINS-9041 Project: Jenkins Issue Type: Bug Components: analysis-core, checkstyle, findbugs Reporter: Felix Gliesche Assignee: Ulli Hafner When using SSL with Hudson, the plugins based on the Analysis Core (such as Findbugs, Checkstyle, etc.) do show the trend but details under the tabs remain empty. It seems that AJAX calls do not use the Hudson URL set under Hudson's system configuration (in our case starting with https://...) . URL rewriting (from http to https) does not fix this problem. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
