[JIRA] (JENKINS-36726) Plugin comments on subsequent successful builds
Title: Message Title Johno Crawford resolved as Fixed Jenkins / JENKINS-36726 Plugin comments on subsequent successful builds Change By: Johno Crawford Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36726) Plugin comments on subsequent successful builds
Title: Message Title Johno Crawford commented on JENKINS-36726 Re: Plugin comments on subsequent successful builds This was implemented as part of https://github.com/jenkinsci/jira-plugin/pull/112 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31164) Issue Type must be selectable from fetched dropdown
Title: Message Title Johno Crawford resolved as Fixed Implemented with pull request https://github.com/jenkinsci/jira-plugin/pull/112 . Pending plugin release! Jenkins / JENKINS-31164 Issue Type must be selectable from fetched dropdown Change By: Johno Crawford Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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
[JIRA] (JENKINS-31164) Issue Type must be selectable from fetched dropdown
Title: Message Title Johno Crawford assigned an issue to Radek Antoniuk Jenkins / JENKINS-31164 Issue Type must be selectable from fetched dropdown Change By: Johno Crawford Assignee: Radek Antoniuk Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-21766) Jenkins create jira issue plugin does not allow configurable jira issue type: defaults to 'bug'
Title: Message Title Johno Crawford closed an issue as Duplicate Jenkins / JENKINS-21766 Jenkins create jira issue plugin does not allow configurable jira issue type: defaults to 'bug' Change By: Johno Crawford Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38026) Error while creating jira issue
Title: Message Title Johno Crawford closed an issue as Duplicate Jenkins / JENKINS-38026 Error while creating jira issue Change By: Johno Crawford Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] [instant-messaging-plugin] (JENKINS-27359) [PATCH] instant-messaging-plugin prevents JVM from shutting down
Johno Crawford commented on JENKINS-27359 [PATCH] instant-messaging-plugin prevents JVM from shutting down Thanks for the merge, when do you think you might release the next version of instant-messaging-plugin? 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] [instant-messaging-plugin] (JENKINS-27359) [PATCH] instant-messaging-plugin prevents JVM from shutting down
Johno Crawford created JENKINS-27359 [PATCH] instant-messaging-plugin prevents JVM from shutting down Issue Type: Bug Assignee: kutzi Components: instant-messaging-plugin Created: 11/Mar/15 1:26 PM Description: ScheduledExecutorService prevents graceful shutdown as it creates a user thread and stops the JVM from shutting down. Can be reproduced with latest Tomcat 7.x. Pull request with fix here https://github.com/jenkinsci/instant-messaging-plugin/pull/13 Project: Jenkins Priority: Critical Reporter: Johno Crawford 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] [instant-messaging-plugin] (JENKINS-27359) [PATCH] instant-messaging-plugin prevents JVM from shutting down
Johno Crawford updated JENKINS-27359 [PATCH] instant-messaging-plugin prevents JVM from shutting down Change By: Johno Crawford (11/Mar/15 1:27 PM) Description: ScheduledExecutorService inHudsonIsBusyListener preventsgracefulshutdownasitcreatesauserthread andstopstheJVMfromshuttingdown .CanbereproducedwithlatestTomcat7.x.Pullrequestwithfixherehttps://github.com/jenkinsci/instant-messaging-plugin/pull/13 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-27178) Execute shell is terminated randomly
Johno Crawford commented on JENKINS-27178 Execute shell is terminated randomly Pull request here https://github.com/jenkinsci/jenkins/pull/1590 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-22032) Node credentials ignored when job credentials set to none
Johno Crawford updated JENKINS-22032 Node credentials ignored when job credentials set to none As a work-around we are able to specify credentials per job, however, there is still the case where a job may be bound to multiple nodes (which may require different credentials). Change By: Johno Crawford (04/Mar/14 5:45 PM) Priority: Blocker Critical 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] [ivy] (JENKINS-18848) Ivy-Projects ends up with a NPE on build after update Jenkins and Ivy-Plugin
Johno Crawford closed JENKINS-18848 as Fixed Ivy-Projects ends up with a NPE on build after update Jenkins and Ivy-Plugin Change By: Johno Crawford (29/Jul/13 8:26 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ivy] (JENKINS-18848) Ivy-Projects ends up with a NPE on build after update Jenkins and Ivy-Plugin
Johno Crawford resolved JENKINS-18848 as Fixed Ivy-Projects ends up with a NPE on build after update Jenkins and Ivy-Plugin Change By: Johno Crawford (29/Jul/13 8:26 PM) Status: Open 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] [ivy] (JENKINS-18848) Ivy-Projects ends up with a NPE on build after update Jenkins and Ivy-Plugin
Johno Crawford edited a comment on JENKINS-18848 Ivy-Projects ends up with a NPE on build after update Jenkins and Ivy-Plugin @Jerome @Ronald please try 1.23.2 and let me know if the above mentioned issues are now resolved. 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] [ivy] (JENKINS-18848) Ivy-Projects ends up with a NPE on build after update Jenkins and Ivy-Plugin
Johno Crawford commented on JENKINS-18848 Ivy-Projects ends up with a NPE on build after update Jenkins and Ivy-Plugin @Jerome would you please confirm if it works if you specify a dummy file (which exists)? I can investigate this issue after work today. 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] [ivy] (JENKINS-18848) Ivy-Projects ends up with a NPE on build after update Jenkins and Ivy-Plugin
Johno Crawford commented on JENKINS-18848 Ivy-Projects ends up with a NPE on build after update Jenkins and Ivy-Plugin Please try 1.23.2 and let me know if the above mentioned issues are now resolved. 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] [ivy] (JENKINS-18848) Ivy-Projects ends up with a NPE on build after update Jenkins and Ivy-Plugin
Johno Crawford assigned JENKINS-18848 to Nicolas De Loof Ivy-Projects ends up with a NPE on build after update Jenkins and Ivy-Plugin This looks like it might be related to your remote ivy settings file changes, would you have a minute to investigate? Change By: Johno Crawford (20/Jul/13 8:56 AM) Assignee: TimothyBingaman 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/groups/opt_out.
[JIRA] [ivy] (JENKINS-18059) support for environment parsing ivy settings
Johno Crawford resolved JENKINS-18059 as Duplicate support for environment parsing ivy settings Change By: Johno Crawford (20/Jul/13 8:57 AM) 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 -- 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] [ivy] (JENKINS-18059) support for environment parsing ivy settings
Johno Crawford closed JENKINS-18059 as Duplicate support for environment parsing ivy settings Change By: Johno Crawford (20/Jul/13 8:57 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ivy] (JENKINS-18848) Ivy-Projects ends up with a NPE on build after update Jenkins and Ivy-Plugin
Johno Crawford commented on JENKINS-18848 Ivy-Projects ends up with a NPE on build after update Jenkins and Ivy-Plugin What have you configured "ivy settings file" as? 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-18589) Deadlock
Johno Crawford commented on JENKINS-18589 Deadlock @kohsuke any ideas on how to maintain backward compatibility for ivy-plugin? or should we bump required core to 1.5xx? for (Trigger? trigger : getTriggers().values()) might be an option albeit ugly.. 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] [other] (JENKINS-10675) Jenkins redirecting from https to http
Johno Crawford commented on JENKINS-10675 Jenkins redirecting from https to http What SSL proxy are you running? If you have Apache try enabling ProxyPreserveHost. 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-15156) Builds disappear from build history after completion
Johno Crawford commented on JENKINS-15156 Builds disappear from build history after completion Current build stability is STABLE, see https://ci.jenkins-ci.org/job/jenkins_main_trunk/ . 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-16492) Upgrade from 0.12 to 0.13 breaks server
Johno Crawford commented on JENKINS-16492 Upgrade from 0.12 to 0.13 breaks server Until I have time to look into the problem I have reverted my last commit and created a new 0.13.1 release, please accept my apologies. 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-15156) Builds disappear from build history after completion
Johno Crawford commented on JENKINS-15156 Builds disappear from build history after completion @jglick can you confirm whether or not the fix will make it for 1.501? 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-16492) Upgrade from 0.12 to 0.13 breaks server
Johno Crawford commented on JENKINS-16492 Upgrade from 0.12 to 0.13 breaks server Are you using GitHub Enterprise? 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-16472) Add IBM XL C parser to Warnings plugin
Johno Crawford closed JENKINS-16472 as Fixed Add IBM XL C parser to Warnings plugin warnings-plugin 4.20 should be available soon. Change By: Johno Crawford (24/Jan/13 10:44 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
Johno Crawford
commented on JENKINS-15779
Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
Where is custom.ivy.settings-${ENV.JAVA_VERSION}.xml defined? Have you set it in "Ivy settings property files"?
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-13726) Github plugin should work with Github enterprise by allowing for overriding the github URL
Johno Crawford closed JENKINS-13726 as Fixed Github plugin should work with Github enterprise by allowing for overriding the github URL Change By: Johno Crawford (19/Jan/13 1:40 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15774) Add ability to specify custom ivy settings file in global configuration for ivy job type
Johno Crawford commented on JENKINS-15774 Add ability to specify custom ivy settings file in global configuration for ivy job type This requires more thought and planning.. global ivy settings file must be an absolute path since it is not tied to the actual job and comes from the master, additionally since the ivy parser is created on the slave the current implementation will fail as the file is loaded from the slave. I will concentrate on JENKINS-15779 and then return to this. 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-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
Johno Crawford commented on JENKINS-15779 Parsing ivy descriptors step fails on a slave when custom ivy settings file is used I am feeling good about this patch! https://github.com/jenkinsci/ivy-plugin/commit/d7e77eec8959b70afc44e94bb38468ac8aca46d2.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
[JIRA] (JENKINS-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
Johno Crawford updated JENKINS-15779 Parsing ivy descriptors step fails on a slave when custom ivy settings file is used Change By: Johno Crawford (19/Jan/13 2:22 PM) Attachment: ivy.hpi 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-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
Johno Crawford edited a comment on JENKINS-15779 Parsing ivy descriptors step fails on a slave when custom ivy settings file is used I am feeling good about this snapshot ( https://issues.jenkins-ci.org/secure/attachment/23081/ivy.hpi ).. Patch available at https://github.com/jenkinsci/ivy-plugin/commit/d7e77eec8959b70afc44e94bb38468ac8aca46d2.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
[JIRA] (JENKINS-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
Johno Crawford edited a comment on JENKINS-15779 Parsing ivy descriptors step fails on a slave when custom ivy settings file is used I am feeling good about this snapshot ( https://issues.jenkins-ci.org/secure/attachment/23081/ivy.hpi ).. Patch available at https://github.com/jenkinsci/ivy-plugin/commit/d7e77eec8959b70afc44e94bb38468ac8aca46d2.patch (do not apply the patch from JENKINS-15774). 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-13726) Github plugin should work with Github enterprise by allowing for overriding the github URL
Johno Crawford reopened JENKINS-13726 Github plugin should work with Github enterprise by allowing for overriding the github URL Change By: Johno Crawford (19/Jan/13 2:35 PM) Resolution: Fixed Status: Closed 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
[JIRA] (JENKINS-13726) Github plugin should work with Github enterprise by allowing for overriding the github URL
Johno Crawford edited a comment on JENKINS-13726 Github plugin should work with Github enterprise by allowing for overriding the github URL Fixed in latest plugin release, let me know how it goes Tom! 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-13726) Github plugin should work with Github enterprise by allowing for overriding the github URL
Johno Crawford resolved JENKINS-13726 as Fixed Github plugin should work with Github enterprise by allowing for overriding the github URL Change By: Johno Crawford (19/Jan/13 2:36 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
[JIRA] (JENKINS-13726) Github plugin should work with Github enterprise by allowing for overriding the github URL
Johno Crawford closed JENKINS-13726 as Fixed Github plugin should work with Github enterprise by allowing for overriding the github URL Change By: Johno Crawford (19/Jan/13 2:36 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15562) Support setting the client version
Johno Crawford edited a comment on JENKINS-15562 Support setting the client version What are your thoughts David? 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-14893) scm sync configuration causes memory leak
Johno Crawford commented on JENKINS-14893 scm sync configuration causes memory leak Perhaps a bit late for the FreedomSponsors offer, however, would you consider uploading the heap dump for analysis? 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-15774) Add ability to specify custom ivy settings file in global configuration for ivy job type
Johno Crawford commented on JENKINS-15774 Add ability to specify custom ivy settings file in global configuration for ivy job type I still think it is a bit strange to have slave specific configuration in system configuration so I will see about changing it to read the file from 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-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
Johno Crawford commented on JENKINS-15779 Parsing ivy descriptors step fails on a slave when custom ivy settings file is used So you have Java 1.6.0_37 installed but Maven is using Java 1.6.0_14. Is your JAVA_HOME environment variable correct? 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-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
Johno Crawford edited a comment on JENKINS-15779 Parsing ivy descriptors step fails on a slave when custom ivy settings file is used So you have Java 1.6.0_37 installed but Maven is using Java 1.6.0_14. Is your JAVA_HOME environment variable correct? Regardless I have added the Object workaround. 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-15774) Add ability to specify custom ivy settings file in global configuration for ivy job type
Johno Crawford commented on JENKINS-15774 Add ability to specify custom ivy settings file in global configuration for ivy job type Feel free to try the snapshot which contains the changes ( https://issues.jenkins-ci.org/secure/attachment/23049/ivy.hpi ). As for my last comment, the path which is set in system configuration is the path which will be loaded from the slave ie. the ivy settings file must be present on the slave. Is this the desired behaviour? 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-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
Johno Crawford updated JENKINS-15779 Parsing ivy descriptors step fails on a slave when custom ivy settings file is used Change By: Johno Crawford (15/Jan/13 12:39 AM) Attachment: ivy.hpi 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-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
Johno Crawford commented on JENKINS-15779 Parsing ivy descriptors step fails on a slave when custom ivy settings file is used Would you please try the latest snapshot ( https://issues.jenkins-ci.org/secure/attachment/23055/ivy.hpi ). I have added logging to spit out the Java home and changed IvyXmlParser to load EnvVars. Changeset available at https://github.com/jenkinsci/ivy-plugin/commit/cdf08c9adde721f5ad93b9d0e79f4c0c013c4e0d.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
[JIRA] (JENKINS-15774) Add ability to specify custom ivy settings file in global configuration for ivy job type
Johno Crawford commented on JENKINS-15774 Add ability to specify custom ivy settings file in global configuration for ivy job type So you're basically asking for a custom ivy settings option for Ivy Project Configuration in the system configuration? 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-15774) Add ability to specify custom ivy settings file in global configuration for ivy job type
Johno Crawford commented on JENKINS-15774 Add ability to specify custom ivy settings file in global configuration for ivy job type Something along the lines of this? https://github.com/jenkinsci/ivy-plugin/commit/4e03055f204801081c01a496b950f348a1279c89.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
[JIRA] (JENKINS-15774) Add ability to specify custom ivy settings file in global configuration for ivy job type
Johno Crawford updated JENKINS-15774 Add ability to specify custom ivy settings file in global configuration for ivy job type Change By: Johno Crawford (13/Jan/13 5:16 PM) Attachment: ivy.hpi 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-15774) Add ability to specify custom ivy settings file in global configuration for ivy job type
Johno Crawford commented on JENKINS-15774 Add ability to specify custom ivy settings file in global configuration for ivy job type One thing to note in the current implementation is that the path in the global ivy settings refers to the slave environment. 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-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
Johno Crawford commented on JENKINS-15779 Parsing ivy descriptors step fails on a slave when custom ivy settings file is used What JDK are you using? Latest 1.6? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
Johno Crawford commented on JENKINS-15779 Parsing ivy descriptors step fails on a slave when custom ivy settings file is used I also committed a change ( https://github.com/jenkinsci/ivy-plugin/commit/708cc3e1c1bb66fe1a7415e305f2f8b7eefa6d06 ) to the IvyBuild file which hopefully fixes the compile bug. 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-13617) 64-bit java.lang.OutOfMemoryError: PermGen space
Johno Crawford resolved JENKINS-13617 as Fixed 64-bit java.lang.OutOfMemoryError: PermGen space Change By: Johno Crawford (09/Jan/13 8:13 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
[JIRA] (JENKINS-13617) 64-bit java.lang.OutOfMemoryError: PermGen space
Johno Crawford closed JENKINS-13617 as Fixed 64-bit java.lang.OutOfMemoryError: PermGen space Change By: Johno Crawford (09/Jan/13 8:13 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
Johno Crawford edited a comment on JENKINS-15779 Parsing ivy descriptors step fails on a slave when custom ivy settings file is used I don't mind at all, here it is https://github.com/johnou/ivy-plugin/commit/16f68088e6c3c0485a3f056c08ece1610e6f3cd3.patch . I am using master too. I assume there must be something wrong with your development environment, you could try moving your local ~/.m2/repository folder and then "mvn compile". I have found that sometimes I run into conflicts because of artifacts which were downloaded from another repo. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13617) 64-bit java.lang.OutOfMemoryError: PermGen space
Johno Crawford assigned JENKINS-13617 to Johno Crawford 64-bit java.lang.OutOfMemoryError: PermGen space Change By: Johno Crawford (08/Jan/13 7:52 PM) Assignee: JohnoCrawford 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-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
Johno Crawford commented on JENKINS-15779 Parsing ivy descriptors step fails on a slave when custom ivy settings file is used I don't mind at all, here it is https://github.com/johnou/ivy-plugin/commit/16f68088e6c3c0485a3f056c08ece1610e6f3cd3.patch . I am using master too. I assume there must be something wrong with your development environment, you could try moving your local ~/.m2/repository folder then resolving dependencies of the project. 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-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
Johno Crawford edited a comment on JENKINS-15779 Parsing ivy descriptors step fails on a slave when custom ivy settings file is used I don't mind at all, here it is https://github.com/johnou/ivy-plugin/commit/16f68088e6c3c0485a3f056c08ece1610e6f3cd3.patch . I am using master too. I assume there must be something wrong with your development environment, you could try moving your local ~/.m2/repository folder and then mvn compile 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-13726) Github plugin should work with Github enterprise by allowing for overriding the github URL
Johno Crawford updated JENKINS-13726 Github plugin should work with Github enterprise by allowing for overriding the github URL Change By: Johno Crawford (07/Jan/13 7:23 PM) Summary: Githubpluginshouldworkwith Guthub Github enterprisebyallowingforoverridingthegithubURL 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-13726) Github plugin should work with Github enterprise by allowing for overriding the github URL
Johno Crawford commented on JENKINS-13726 Github plugin should work with Github enterprise by allowing for overriding the github URL github-plugin and github-api-plugin (1.34) dependencies now support connecting to an enterprise server. Once there is feedback on my snapshot I will see about merging the changes into the plugin and creating a new release. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
Johno Crawford edited a comment on JENKINS-15779 Parsing ivy descriptors step fails on a slave when custom ivy settings file is used To get a better understanding of what is going on I have created a snapshot with verbose logging enabled ( https://issues.jenkins-ci.org/secure/attachment/23031/ivy.hpi ). Would you please try it out and look for log messages which differ from master and slave? Log messages starting with the following might be interesting.. Configured Ivy using custom settings Configured Ivy using default 2.1 settings Error while reading the default Ivy 2.1 settings 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-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
Johno Crawford updated JENKINS-15779 Parsing ivy descriptors step fails on a slave when custom ivy settings file is used To get a better understanding of what is going on I have created a snapshot with verbose logging enabled. Would you please try it out and look for log messages which differ from master and slave? Log messages starting with the following might be interesting.. Configured Ivy using custom settings Configured Ivy using default 2.1 settings Error while reading the default Ivy 2.1 settings Change By: Johno Crawford (08/Jan/13 12:25 AM) Attachment: ivy.hpi 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-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
Johno Crawford updated JENKINS-15779 Parsing ivy descriptors step fails on a slave when custom ivy settings file is used Change By: Johno Crawford (08/Jan/13 12:57 AM) Attachment: ivy.hpi 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-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
Johno Crawford edited a comment on JENKINS-15779 Parsing ivy descriptors step fails on a slave when custom ivy settings file is used To get a better understanding of what is going on I have created a snapshot with verbose logging enabled ( https://issues.jenkins-ci.org/secure/attachment/23032/ivy.hpi ). Would you please try it out and look for log messages which differ from master and slave? Log messages starting with the following might be interesting.. Configured Ivy using custom settings Configured Ivy using default 2.1 settings Error while reading the default Ivy 2.1 settings 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-13726) Github plugin should work with Guthub enterprise by allowing for overriding the github URL
Johno Crawford commented on JENKINS-13726 Github plugin should work with Guthub enterprise by allowing for overriding the github URL My PR has been merged, I will follow up with having the version for org.jenkins-ci.plugins github-api bumped. 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-13726) Github plugin should work with Guthub enterprise by allowing for overriding the github URL
Johno Crawford edited a comment on JENKINS-13726 Github plugin should work with Guthub enterprise by allowing for overriding the github URL Attaching snapshot of my work in progress ( https://issues.jenkins-ci.org/secure/attachment/23028/github.hpi ). If anyone with GitHub Enterprise is willing to try it out and give feedback I would greatly appreciate it, unfortunately I do not have access to an instance to test it myself. You will need to configure the API URL and API key in GitHub Web Hook. Source code changes available at https://github.com/johnou/github-plugin/commit/947f6e29dd44a982603435ab58852794c43710a9 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-13617) 64-bit java.lang.OutOfMemoryError: PermGen space
Johno Crawford commented on JENKINS-13617 64-bit java.lang.OutOfMemoryError: PermGen space Niklaus, if there are no memory dumps in that time I think we can rule PeriodicBackup plugin as the culprit and there is no need to move Jenkins to run under Tomcat. I have merged the fixes to the PeriodicBackup plugin repo (1.2+ contains the fixes in my snapshot) which should now be available from your plugin manager (you may need to click "Check now" in the advanced tab). The exception java.lang.OutOfMemoryError: PermGen space is generic, depends on how Jenkins is used, what plugins you have installed etc. there is no way to avoid it if there is a class loader memory leak, increasing the max permsize, enabling other switches which modify the JVM GC behaviour will (most of the time) prolong the ticking time bomb. For those interested in knowing more about PermGen check out this article: http://frankkieviet.blogspot.ca/2006/10/classloader-leaks-dreaded-permgen-space.html If there are others receiving this error after increasing both -XX:MaxPermSize and -Xmx to reasonable values it might be caused by plugin(s) you have installed or the way you use Jenkins, however without a heap dump to analyse it is practically impossible to debug. 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-13617) 64-bit java.lang.OutOfMemoryError: PermGen space
Johno Crawford edited a comment on JENKINS-13617 64-bit java.lang.OutOfMemoryError: PermGen space Niklaus, if there are no memory dumps in that time I think we can rule PeriodicBackup plugin as the culprit and there is no need to move Jenkins to run under Tomcat. I have merged the fixes to the PeriodicBackup plugin repo (1.2+ contains the fixes in my snapshot) which should now be available from your plugin manager (you may need to click "Check now" in the advanced tab). The exception java.lang.OutOfMemoryError: PermGen space is generic, depends on how Jenkins is used, what plugins you have installed etc. there is no way to avoid it if there is a class loader memory leak, increasing the max permsize, enabling other switches which modify the JVM GC behaviour will (most of the time) prolong the ticking time bomb. For those interested in knowing more about PermGen check out this article: http://frankkieviet.blogspot.ca/2006/10/classloader-leaks-dreaded-permgen-space.html If there are others receiving this error after increasing both -XX:MaxPermSize and -Xmx to reasonable values it might be caused by plugin(s) you have installed or the way you use Jenkins (there might be undiscovered memory leaks in core), however without a heap dump to analyse it is practically impossible to debug due to the size of the code base and large amount of plugins. 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-13617) 64-bit java.lang.OutOfMemoryError: PermGen space
Johno Crawford edited a comment on JENKINS-13617 64-bit java.lang.OutOfMemoryError: PermGen space Niklaus, if there are no memory dumps in that time I think we can rule PeriodicBackup plugin as the culprit and there is no need to move Jenkins to run under Tomcat. I have merged the fixes to the PeriodicBackup plugin repo JENKINS-16223 (1.2+ contains the fixes in my snapshot) which should now be available from your plugin manager (you may need to click "Check now" in the advanced tab). The exception java.lang.OutOfMemoryError: PermGen space is generic, depends on how Jenkins is configured, used, what plugins you have installed etc. there is no way to avoid it if there is a class loader memory leak, increasing the max permsize, enabling other switches which modify the JVM GC behaviour will (most of the time) prolong the ticking time bomb. For those interested in knowing more about PermGen check out this article: http://frankkieviet.blogspot.ca/2006/10/classloader-leaks-dreaded-permgen-space.html If there are others receiving this error after increasing both -XX:MaxPermSize and -Xmx to reasonable values the OOM might be caused by plugin(s) you have installed or the way you use Jenkins (there might be undiscovered memory leaks in core), however without a heap dump to analyse it is practically impossible to debug due to the size of the code base and amount of plugins. Adam, instead of using the switch -XX:PermSize you should be using -XX:MaxPermSize, in addition, 64bit JVM will use almost double the amount of memory for object pointers ( https://wikis.oracle.com/display/HotSpotInternals/CompressedOops ). You can try adding -XX:+UseCompressedOops to your JVM args to help, however you may have ran into a memory leak like Niklaus (in which case a heap dump is required). 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-13617) 64-bit java.lang.OutOfMemoryError: PermGen space
Johno Crawford edited a comment on JENKINS-13617 64-bit java.lang.OutOfMemoryError: PermGen space Niklaus, if there are no memory dumps in that time I think we can rule PeriodicBackup plugin as the culprit and there is no need to move Jenkins to run under Tomcat. I have merged the fixes to the PeriodicBackup plugin repo JENKINS-16223 (1.2+ contains the fixes in my snapshot) which should now be available from your plugin manager (you may need to click "Check now" in the advanced tab). The exception java.lang.OutOfMemoryError: PermGen space is generic, there is no way to avoid it if there is a class loader memory leak, increasing the max permsize, enabling other switches which modify the JVM GC behaviour will (most of the time) prolong the ticking time bomb. For those interested in knowing more about PermGen check out this article: http://frankkieviet.blogspot.ca/2006/10/classloader-leaks-dreaded-permgen-space.html If there are others receiving this error after increasing both -XX:MaxPermSize and -Xmx to reasonable values the OOM might be caused by plugin(s) you have installed or the way you use Jenkins (there might be undiscovered memory leaks in core), however without a heap dump to analyse it is practically impossible to debug due to the size of the code base and amount of plugins. Adam, instead of using the switch -XX:PermSize you should be using -XX:MaxPermSize, in addition, 64bit JVM will use almost double the amount of memory for object pointers ( https://wikis.oracle.com/display/HotSpotInternals/CompressedOops ). You can try adding -XX:+UseCompressedOops to your JVM args to help, however you may have ran into a memory leak like Niklaus (in which case a heap dump is required). 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-13726) Github plugin should work with Guthub enterprise by allowing for overriding the github URL
Johno Crawford commented on JENKINS-13726 Github plugin should work with Guthub enterprise by allowing for overriding the github URL Before working on the actual Jenkins plugin source it requires changes to the api dependency to support custom github servers. I have created a PR at https://github.com/kohsuke/github-api/pull/24/files . 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-13726) Github plugin should work with Guthub enterprise by allowing for overriding the github URL
Johno Crawford assigned JENKINS-13726 to Johno Crawford Github plugin should work with Guthub enterprise by allowing for overriding the github URL Change By: Johno Crawford (06/Jan/13 4:01 AM) Assignee: JohnoCrawford 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-13617) 64-bit java.lang.OutOfMemoryError: PermGen space
Johno Crawford commented on JENKINS-13617 64-bit java.lang.OutOfMemoryError: PermGen space Heap dump looks better than before. This time it blew up at "Pipe writer thread: Jenkins-win7" prio=5 tid=16893 RUNNABLE at java.lang.OutOfMemoryError.init(OutOfMemoryError.java:25) at java.lang.Class.getDeclaredConstructors0(Native Method) at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389) at java.lang.Class.getConstructor0(Class.java:2699) at java.lang.Class.newInstance0(Class.java:326) Local Variable: java.lang.Class[]#7844 at java.lang.Class.newInstance(Class.java:308) Local Variable: class sun.reflect.GeneratedSerializationConstructorAccessor6164 at sun.reflect.MethodAccessorGenerator$1.run(MethodAccessorGenerator.java:381) Local Variable: sun.reflect.MethodAccessorGenerator$1#1 at java.security.AccessController.doPrivileged(Native Method) at sun.reflect.MethodAccessorGenerator.generate(MethodAccessorGenerator.java:377) Local Variable: java.lang.String#60850 Local Variable: sun.reflect.ByteVectorImpl#1 Local Variable: java.lang.Class#9 .. winstone.classLoader.WebappClassLoader seems to be holding on to quite a lot of classes, but this might as well be normal behaviour. What are your current memory settings for the JVM? If they have been omitted please try restarting the JVM with the following flags "-XX:MaxPermSize=256m -Xmx768m -XX:+CMSClassUnloadingEnabled -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/log/jenkins/memory.dump". To rule out memory leaks with the Winstone container you could also try running Jenkins on Tomcat to see if it helps or not. 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-13617) 64-bit java.lang.OutOfMemoryError: PermGen space
Johno Crawford edited a comment on JENKINS-13617 64-bit java.lang.OutOfMemoryError: PermGen space Heap dump looks better than before. This time it blew up at "Pipe writer thread: Jenkins-win7" prio=5 tid=16893 RUNNABLE at java.lang.OutOfMemoryError.init(OutOfMemoryError.java:25) at java.lang.Class.getDeclaredConstructors0(Native Method) at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389) at java.lang.Class.getConstructor0(Class.java:2699) at java.lang.Class.newInstance0(Class.java:326) Local Variable: java.lang.Class[]#7844 at java.lang.Class.newInstance(Class.java:308) Local Variable: class sun.reflect.GeneratedSerializationConstructorAccessor6164 at sun.reflect.MethodAccessorGenerator$1.run(MethodAccessorGenerator.java:381) Local Variable: sun.reflect.MethodAccessorGenerator$1#1 at java.security.AccessController.doPrivileged(Native Method) at sun.reflect.MethodAccessorGenerator.generate(MethodAccessorGenerator.java:377) Local Variable: java.lang.String#60850 Local Variable: sun.reflect.ByteVectorImpl#1 Local Variable: java.lang.Class#9 .. What are your current memory settings for the JVM? If they have been omitted please try restarting the JVM with the following flags "-XX:MaxPermSize=256m -Xmx768m -XX:+CMSClassUnloadingEnabled -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/log/jenkins/memory.dump". winstone.classLoader.WebappClassLoader seems to be holding on to quite a lot of classes, but this might as well be normal behaviour. To rule out memory leaks with the Winstone container you could also try running Jenkins on Tomcat to see if it helps. 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-16223) Update periodicbackup-plugin dependency plexus-archiver to 2.2.
Johno Crawford assigned JENKINS-16223 to Johno Crawford Update periodicbackup-plugin dependency plexus-archiver to 2.2. Change By: Johno Crawford (03/Jan/13 9:46 PM) Assignee: emanuelez JohnoCrawford 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-13635) Backup warnings when performing tar.gz
Johno Crawford commented on JENKINS-13635 Backup warnings when performing tar.gz What OS is your platform? 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-13635) Backup warnings when performing tar.gz
Johno Crawford commented on JENKINS-13635 Backup warnings when performing tar.gz duh, Ubuntu Linux. 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-13635) Backup warnings when performing tar.gz
Johno Crawford commented on JENKINS-13635 Backup warnings when performing tar.gz http://www.delorie.com/gnu/docs/tar/tar_114.html GNU tar was based on an early draft of the POSIX 1003.1 ustar standard. GNU extensions to tar, such as the support for file names longer than 100 characters, use portions of the tar header record which were specified in that POSIX draft as unused. Subsequent changes in POSIX have allocated the same parts of the header record for other purposes. As a result, GNU tar is incompatible with the current POSIX spec, and with tar programs that follow it. POSIX mandates that, when a file name cannot fit within 100 to 256 characters (the variance comes from the fact a / is ideally needed as the 156'th character), or a link name cannot fit within 100 characters, a warning should be issued and the file not be stored. Unless some --posix option is given (or POSIXLY_CORRECT is set), I suspect that GNU tar should disobey this specification, and automatically switch to using GNU extensions to overcome file name or link name length limitations. 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-13635) Backup warnings when performing tar.gz
Johno Crawford resolved JENKINS-13635 as Fixed Backup warnings when performing tar.gz Fixed next build, archiver now creates GNU tars. Change By: Johno Crawford (03/Jan/13 10:12 PM) Status: Open Resolved Assignee: JohnoCrawford 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
[JIRA] (JENKINS-13050) No feedback when invalid configuration refuses to save
Johno Crawford assigned JENKINS-13050 to Johno Crawford No feedback when invalid configuration refuses to save Change By: Johno Crawford (03/Jan/13 10:13 PM) Assignee: JohnoCrawford 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-13635) Backup warnings when performing tar.gz
Johno Crawford commented on JENKINS-13635 Backup warnings when performing tar.gz https://github.com/jenkinsci/periodicbackup-plugin/commit/4bf5a1269b2ba39f6a1eb6fefc57f6230aea9c48 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-13635) Backup warnings when performing tar.gz
Johno Crawford edited a comment on JENKINS-13635 Backup warnings when performing tar.gz For clarity sake, the new limit is now 256 characters. 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-12846) config files under users directory not backed up
Johno Crawford assigned JENKINS-12846 to Johno Crawford config files under users directory not backed up Change By: Johno Crawford (03/Jan/13 10:25 PM) Assignee: JohnoCrawford 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-13050) No feedback when invalid configuration refuses to save
Johno Crawford commented on JENKINS-13050 No feedback when invalid configuration refuses to save What browser are you 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
[JIRA] (JENKINS-12846) config files under users directory not backed up
Johno Crawford resolved JENKINS-12846 as Fixed config files under users directory not backed up users directory will be backed up in the next build. Change By: Johno Crawford (03/Jan/13 11:36 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
[JIRA] (JENKINS-12846) config files under users directory not backed up
Johno Crawford edited a comment on JENKINS-12846 config files under users directory not backed up users directory will be backed up in the next build (1.3). 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-13617) 64-bit java.lang.OutOfMemoryError: PermGen space
Johno Crawford edited a comment on JENKINS-13617 64-bit java.lang.OutOfMemoryError: PermGen space Looks like a version conflict, try shutting down your Jenkins instance, removing all files beginning with periodicbackup in /var/lib/jenkins/plugins (folder named periodicbackup, periodicbackup.jpi etc.), place a fresh copy of 23010/periodicbackup.hpi to /var/lib/jenkins/plugins/periodicbackup.hpi and then start Jenkins / verify you are running the SNAPSHOT version from plugin manager. 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-13617) 64-bit java.lang.OutOfMemoryError: PermGen space
Johno Crawford commented on JENKINS-13617 64-bit java.lang.OutOfMemoryError: PermGen space Try shutting down your Jenkins instance, removing all files in /var/lib/jenkins/plugins beginning with periodicbackup (folder, periodicbackup.jpi etc.), place a fresh copy of 23010/periodicbackup.hpi to /var/lib/jenkins/plugins/periodicbackup.hpi as you previously did and then start Jenkins. 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-13617) 64-bit java.lang.OutOfMemoryError: PermGen space
Johno Crawford edited a comment on JENKINS-13617 64-bit java.lang.OutOfMemoryError: PermGen space Looks like a version conflict, try shutting down your Jenkins instance, removing all files in /var/lib/jenkins/plugins beginning with periodicbackup (folder, periodicbackup.jpi etc.), place a fresh copy of 23010/periodicbackup.hpi to /var/lib/jenkins/plugins/periodicbackup.hpi as you previously did and then start Jenkins. 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-13617) 64-bit java.lang.OutOfMemoryError: PermGen space
Johno Crawford edited a comment on JENKINS-13617 64-bit java.lang.OutOfMemoryError: PermGen space Looks like a version conflict, try shutting down your Jenkins instance, removing all files beginning with periodicbackup in /var/lib/jenkins/plugins (folder named periodicbackup, periodicbackup.jpi etc.), place a fresh copy of 23010/periodicbackup.hpi to /var/lib/jenkins/plugins/periodicbackup.hpi as you previously did and then start Jenkins / verify you are running the SNAPSHOT version from plugin manager. 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-16223) Update periodicbackup-plugin dependency plexus-archiver to 2.2.
Johno Crawford updated JENKINS-16223 Update periodicbackup-plugin dependency plexus-archiver to 2.2. Change By: Johno Crawford (30/Dec/12 10:24 PM) Description: Lotsofbugfixeseg.http://jira.codehaus.org/browse/PLXCOMP- 194,http://jira.codehaus.org/browse/PLXCOMP- 149.Suspectedcauseforhttps://issues.jenkins-ci.org/browse/JENKINS-13617.Ibuiltthepluginlocally,worksaspernormalonmydevenvironment.Pullrequest@https://github.com/jenkinsci/periodicbackup-plugin/pull/4 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-16223) Update periodicbackup-plugin dependency plexus-archiver to 2.2.
Johno Crawford assigned JENKINS-16223 to emanuelez Update periodicbackup-plugin dependency plexus-archiver to 2.2. Change By: Johno Crawford (30/Dec/12 10:29 PM) Assignee: emanuelez 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-16223) Update periodicbackup-plugin dependency plexus-archiver to 2.2.
johno created JENKINS-16223 Update periodicbackup-plugin dependency plexus-archiver to 2.2. Issue Type: Patch Assignee: Unassigned Components: periodicbackup Created: 29/Dec/12 1:54 PM Description: Lots of bug fixes eg. http://jira.codehaus.org/browse/PLXCOMP-149 . Suspected cause for https://issues.jenkins-ci.org/browse/JENKINS-13617 . I built the plugin locally, works as per normal on my dev environment. Pull request @ https://github.com/jenkinsci/periodicbackup-plugin/pull/4 Project: Jenkins Priority: Major Reporter: johno 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-13617) 64-bit java.lang.OutOfMemoryError: PermGen space
johno edited a comment on JENKINS-13617 64-bit java.lang.OutOfMemoryError: PermGen space No need for jenkins.log at the moment. Heap dump looks okish, top instance count is java.lang.Class, I would recommend adding the switch -XX:+CMSClassUnloadingEnabled . Looking at the thread dump I see it OOMd in the PeriodicBackup ( https://wiki.jenkins-ci.org/display/JENKINS/PeriodicBackup+Plugin ) thread. Would you please try installing my snapshot with updated libraries ( https://issues.jenkins-ci.org/secure/attachment/23009/periodicbackup.hpi ) or disabling the plugin temporarily to see if it helps. "PeriodicBackup thread" prio=5 tid=3023 RUNNABLE at java.lang.OutOfMemoryError.init(OutOfMemoryError.java:25) at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631) .. 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-13617) 64-bit java.lang.OutOfMemoryError: PermGen space
johno updated JENKINS-13617 64-bit java.lang.OutOfMemoryError: PermGen space Change By: johno (29/Dec/12 3:17 PM) Attachment: periodicbackup.hpi 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-13617) 64-bit java.lang.OutOfMemoryError: PermGen space
johno edited a comment on JENKINS-13617 64-bit java.lang.OutOfMemoryError: PermGen space I have created a new build of the periodicbackup plugin ( https://issues.jenkins-ci.org/secure/attachment/23010/periodicbackup.hpi ) with the latest plexus-archiver, let me know if it helps! 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-13617) 64-bit java.lang.OutOfMemoryError: PermGen space
johno edited a comment on JENKINS-13617 64-bit java.lang.OutOfMemoryError: PermGen space No need for jenkins.log at the moment. Heap dump looks okish, top instance count is java.lang.Class, I would recommend adding the switch -XX:+CMSClassUnloadingEnabled . Looking at the thread dump I see it OOMd in the PeriodicBackup ( https://wiki.jenkins-ci.org/display/JENKINS/PeriodicBackup+Plugin ) thread. Would you please try installing my snapshot with updated libraries ( https://issues.jenkins-ci.org/secure/attachment/23010/periodicbackup.hpi ) or disabling the plugin temporarily to see if it helps. "PeriodicBackup thread" prio=5 tid=3023 RUNNABLE at java.lang.OutOfMemoryError.init(OutOfMemoryError.java:25) at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631) .. 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-13617) 64-bit java.lang.OutOfMemoryError: PermGen space
johno commented on JENKINS-13617 64-bit java.lang.OutOfMemoryError: PermGen space Updated periodbackup snapshot to include fix for http://jira.codehaus.org/browse/PLXCOMP-194 . 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-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
johno commented on JENKINS-15779 Parsing ivy descriptors step fails on a slave when custom ivy settings file is used Would you be willing to create a small testcase project which demonstrates the bug? 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-13617) 64-bit java.lang.OutOfMemoryError: PermGen space
johno edited a comment on JENKINS-13617 64-bit java.lang.OutOfMemoryError: PermGen space Should be in the logs directory, java_pidactual pid.hprof . If you can still not locate the dump you may consider configuring the path with the -XX:HeapDumpPath switch eg. -XX:HeapDumpPath=/usr/share/jenkins 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
