[JIRA] [scm-sync-configuration] (JENKINS-17946) Include a list of plugins installed
Samu Wikstedt commented on JENKINS-17946 Include a list of plugins installed You are right about the plugin versions issue; Following LTS jenkins update cycle, is nicely working solution for us. But true, that might not be the case in all users. 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] [scm-sync-configuration] (JENKINS-17946) Include a list of plugins installed
Samu Wikstedt resolved JENKINS-17946 as Not A Defect Include a list of plugins installed BAcking up running jenkins is highly dependent on the matter how jenkins maintainer want's to back it up. --- It's better to leave needed plugin list generation to one own solution(s) that meets ones requirements. Change By: Samu Wikstedt (21/May/13 6:49 AM) Status: Open Resolved 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/groups/opt_out.
[JIRA] [subversion] (JENKINS-16343) Access to the Subversion repository doesn't work via the subversion plugin - Always get a E200015: No credential to try. Authentication failed error.
ily naf commented on JENKINS-16343 Access to the Subversion repository doesnt work via the subversion plugin - Always get a E200015: No credential to try. Authentication failed error. They could be related because we also apply the workaround "-Dsvnkit.http.sslProtocols=SSLv3" here. 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] [publish-over-ftp] (JENKINS-17165) Publish over FTP plugin with version 1.9 does'nt work after Jenkins upgrade to Version 1.504
Ramakrishna Bejawar commented on JENKINS-17165 Publish over FTP plugin with version 1.9 doesnt work after Jenkins upgrade to Version 1.504 Hi Alexander, Thanks for the Fix. Now Surprisingly We face the same issue with CIFS Plug-in too. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [publish-over-ftp] (JENKINS-17165) Publish over FTP plugin with version 1.9 does'nt work after Jenkins upgrade to Version 1.504
Ramakrishna Bejawar edited a comment on JENKINS-17165 Publish over FTP plugin with version 1.9 doesnt work after Jenkins upgrade to Version 1.504 Hi Alexander/bap, Thanks for the Fix. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ws-cleanup] (JENKINS-12783) Delete workspace before build starts ignores Exlude patterns (for directories)
Rando Õispuu commented on JENKINS-12783 Delete workspace before build starts ignores Exlude patterns (for directories) When "Apply pattern also on directories" everything gets deleted regardless of the Exclude pattern. I use **/DIR/DIR/ it works when "Apply pattern also on directories" is not checked. 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-18020) Publisher hudson.tasks.Mailer aborted due to exception randomly appearing
Linards L created JENKINS-18020 Publisher hudson.tasks.Mailer aborted due to exception randomly appearing Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 21/May/13 7:49 AM Description: I am having periodic expereince with this: 06:17:59 BUILD FAILED 06:17:59 E:\Hudson\jobs\trunk-Horizon-nightly\workspace\Source\build.xml:973: The following error occurred while executing this line: 06:17:59 E:\Hudson\jobs\trunk-Horizon-nightly\workspace\Source\build.xml:975: The following error occurred while executing this line: 06:17:59 E:\Hudson\jobs\trunk-Horizon-nightly\workspace\Source\build.xml:323: The following error occurred while executing this line: 06:17:59 E:\Hudson\jobs\trunk-Horizon-nightly\workspace\Source\build.xml:274: The following error occurred while executing this line: 06:17:59 E:\Hudson\jobs\trunk-Horizon-nightly\workspace\Source\build.xml:286: The following error occurred while executing this line: 06:17:59 E:\Hudson\jobs\trunk-Horizon-nightly\workspace\Source\build.xml:140: exec returned: 1 06:17:59 06:17:59 Total time: 60 minutes 10 seconds 06:18:00 Build step 'Invoke Ant' marked build as failure 06:18:00 WARNINGS Skipping publisher since build result is FAILURE 06:18:00 Archiving artifacts 06:18:51 Recording test results 06:18:51 Recording fingerprints 06:21:44 ERROR: Publisher hudson.tasks.Mailer aborted due to exception 06:21:44 java.lang.ArrayIndexOutOfBoundsException: Assertion error: failing to load #1 DESC: lo=3,hi=1,size=175,size2=175 06:21:44 at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:442) 06:21:44 at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:222) 06:21:44 at hudson.tasks.Fingerprinter$FingerprintAction.onLoad(Fingerprinter.java:357) 06:21:44 at hudson.model.Run.onLoad(Run.java:319) 06:21:44 at hudson.model.RunMap.retrieve(RunMap.java:226) 06:21:44 at hudson.model.RunMap.retrieve(RunMap.java:59) 06:21:44 at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:667) 06:21:44 at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:650) 06:21:44 at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:456) 06:21:44 at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:222) 06:21:44 at hudson.model.AbstractProject.hasParticipant(AbstractProject.java:1580) 06:21:44 at hudson.model.User.getProjects(User.java:449) 06:21:44 at hudson.scm.SubversionMailAddressResolverImpl.findMailAddressFor(SubversionMailAddressResolverImpl.java:25) 06:21:44 at hudson.tasks.MailAddressResolver.resolve(MailAddressResolver.java:101) 06:21:44 at hudson.tasks.Mailer$UserProperty.getAddress(Mailer.java:532) 06:21:44 at hudson.tasks.MailSender.buildCulpritList(MailSender.java:408) 06:21:44 at hudson.tasks.MailSender.createEmptyMail(MailSender.java:368) 06:21:44 at hudson.tasks.MailSender.createFailureMail(MailSender.java:227) 06:21:44 at hudson.tasks.MailSender.getMail(MailSender.java:154) 06:21:44 at hudson.tasks.MailSender.execute(MailSender.java:100) 06:21:44 at hudson.tasks.Mailer.perform(Mailer.java:117) 06:21:44 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) 06:21:44 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) 06:21:44 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776) 06:21:44 at hudson.model.Build$BuildExecution.post2(Build.java:183) 06:21:44 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726) 06:21:44 at hudson.model.Run.execute(Run.java:1600) 06:21:44 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) 06:21:44 at hudson.model.ResourceController.execute(ResourceController.java:88) 06:21:44 at hudson.model.Executor.run(Executor.java:241) 06:21:44 Finished: FAILURE I cannot produce any pattern to make intended resulf of this, but mainly we are having these issues after we started to have few junit unit tests failing constantly. Please
[JIRA] [core] (JENKINS-18020) Publisher hudson.tasks.Mailer aborted due to exception randomly appearing
Linards L updated JENKINS-18020 Publisher hudson.tasks.Mailer aborted due to exception randomly appearing Change By: Linards L (21/May/13 7:51 AM) Description: Iamhavingperiodicexpereincewiththis:06:17:59BUILDFAILED06:17:59 E: job \ Hudson\jobs\trunk-Horizon-nightly\workspace\Source\ build.xml:973:Thefollowingerroroccurredwhileexecutingthisline:06:17:59 E: job \ Hudson\jobs\trunk-Horizon-nightly\workspace\Source\ build.xml:975:Thefollowingerroroccurredwhileexecutingthisline:06:17:59 E: job \ Hudson\jobs\trunk-Horizon-nightly\workspace\Source\ build.xml:323:Thefollowingerroroccurredwhileexecutingthisline:06:17:59 E: job \ Hudson\jobs\trunk-Horizon-nightly\workspace\Source\ build.xml:274:Thefollowingerroroccurredwhileexecutingthisline:06:17:59 E: job \ Hudson\jobs\trunk-Horizon-nightly\workspace\Source\ build.xml:286:Thefollowingerroroccurredwhileexecutingthisline:06:17:59 E: job \ Hudson\jobs\trunk-Horizon-nightly\workspace\Source\ build.xml:140:execreturned:106:17:5906:17:59Totaltime:60minutes10seconds06:18:00BuildstepInvokeAntmarkedbuildasfailure06:18:00[WARNINGS]SkippingpublishersincebuildresultisFAILURE06:18:00Archivingartifacts06:18:51Recordingtestresults06:18:51Recordingfingerprints06:21:44ERROR:Publisherhudson.tasks.Mailerabortedduetoexception06:21:44java.lang.ArrayIndexOutOfBoundsException:Assertionerror:failingtoload#1DESC:lo=3,hi=1,size=175,size2=17506:21:44 atjenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:442)06:21:44 athudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:222)06:21:44 athudson.tasks.Fingerprinter$FingerprintAction.onLoad(Fingerprinter.java:357)06:21:44 athudson.model.Run.onLoad(Run.java:319)06:21:44 athudson.model.RunMap.retrieve(RunMap.java:226)06:21:44 athudson.model.RunMap.retrieve(RunMap.java:59)06:21:44 atjenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:667)06:21:44 atjenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:650)06:21:44 atjenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:456)06:21:44 athudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:222)06:21:44 athudson.model.AbstractProject.hasParticipant(AbstractProject.java:1580)06:21:44 athudson.model.User.getProjects(User.java:449)06:21:44 athudson.scm.SubversionMailAddressResolverImpl.findMailAddressFor(SubversionMailAddressResolverImpl.java:25)06:21:44 athudson.tasks.MailAddressResolver.resolve(MailAddressResolver.java:101)06:21:44 athudson.tasks.Mailer$UserProperty.getAddress(Mailer.java:532)06:21:44 athudson.tasks.MailSender.buildCulpritList(MailSender.java:408)06:21:44 athudson.tasks.MailSender.createEmptyMail(MailSender.java:368)06:21:44 athudson.tasks.MailSender.createFailureMail(MailSender.java:227)06:21:44 athudson.tasks.MailSender.getMail(MailSender.java:154)06:21:44 athudson.tasks.MailSender.execute(MailSender.java:100)06:21:44 athudson.tasks.Mailer.perform(Mailer.java:117)06:21:44 athudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)06:21:44 athudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804)06:21:44 athudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776)06:21:44 athudson.model.Build$BuildExecution.post2(Build.java:183)06:21:44 athudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726)06:21:44 athudson.model.Run.execute(Run.java:1600)06:21:44 athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)06:21:44 athudson.model.ResourceController.execute(ResourceController.java:88)06:21:44 athudson.model.Executor.run(Executor.java:241)06:21:44Finished:FAILUREIcannotproduceanypatterntomakeintendedresulfofthis,butmainlywearehavingtheseissuesafterwestartedtohavefewjunitunittestsfailingconstantly.Pleaseinformifanylogsneeded.Andinthenoobtermimology,please.;) 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] [core] (JENKINS-18020) Publisher hudson.tasks.Mailer aborted due to exception randomly appearing
Linards L commented on JENKINS-18020 Publisher hudson.tasks.Mailer aborted due to exception randomly appearing What is interesting are tghese lines: 06:18:00 Build step 'Invoke Ant' marked build as failure 06:18:00 WARNINGS Skipping publisher since build result is FAILURE and - 06:21:44 ERROR: Publisher hudson.tasks.Mailer aborted due to exception 06:21:44 java.lang.ArrayIndexOutOfBoundsException: Assertion error: failing to load #1 DESC: lo=3,hi=1,size=175,size2=175 06:21:44 at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:442) 06:21:44 at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:222) ... Seems like Warnings plugin somehow manages this "jenkins.model.lazy.AbstractLazyLoadRunMap.search" better that internal Mailer ... 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] [prqa] (JENKINS-18018) Graph incorrectly scales max to all messages (our case 9317)
Mads Nielsen updated JENKINS-18018 Graph incorrectly scales max to all messages (our case 9317) Change By: Mads Nielsen (21/May/13 7:57 AM) Summary: Graphincorrectlyscalesmaxtoallmessages (ourcase9317) 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-4354) Make Hudson user names case insensitive
cforce commented on JENKINS-4354 Make Hudson user names case insensitive Please fix, thaz really suxx! 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] [ldap] (JENKINS-3218) Hudson LDAP authentification is Case Sensitive
cforce commented on JENKINS-3218 Hudson LDAP authentification is Case Sensitive Please fix, there so many different requests! Related/Dupe to https://issues.jenkins-ci.org/browse/JENKINS-3218 https://issues.jenkins-ci.org/browse/JENKINS-6377 https://issues.jenkins-ci.org/browse/JENKINS-4354 https://issues.jenkins-ci.org/browse/JENKINS-4354 https://issues.jenkins-ci.org/browse/JENKINS-4550 https://issues.jenkins-ci.org/browse/JENKINS-5436 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] [security] (JENKINS-6377) Hudson Enforcing Unusual Case-Sensitivity for Login
cforce commented on JENKINS-6377 Hudson Enforcing Unusual Case-Sensitivity for Login Please fix, there so many different requests! Related/Dupe to https://issues.jenkins-ci.org/browse/JENKINS-3218 https://issues.jenkins-ci.org/browse/JENKINS-6377 https://issues.jenkins-ci.org/browse/JENKINS-4354 https://issues.jenkins-ci.org/browse/JENKINS-4354 https://issues.jenkins-ci.org/browse/JENKINS-4550 https://issues.jenkins-ci.org/browse/JENKINS-5436 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-4354) Make Hudson user names case insensitive
cforce edited a comment on JENKINS-4354 Make Hudson user names case insensitive Please fix, there so many different requests! Related/Dupe to https://issues.jenkins-ci.org/browse/JENKINS-3218 https://issues.jenkins-ci.org/browse/JENKINS-6377 https://issues.jenkins-ci.org/browse/JENKINS-4354 https://issues.jenkins-ci.org/browse/JENKINS-4354 https://issues.jenkins-ci.org/browse/JENKINS-4550 https://issues.jenkins-ci.org/browse/JENKINS-5436 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] [active-directory] (JENKINS-4550) User ID in Security is case sensitive
cforce commented on JENKINS-4550 User ID in Security is case sensitive Please fix, there so many different requests! Related/Dupe to https://issues.jenkins-ci.org/browse/JENKINS-3218 https://issues.jenkins-ci.org/browse/JENKINS-6377 https://issues.jenkins-ci.org/browse/JENKINS-4354 https://issues.jenkins-ci.org/browse/JENKINS-4354 https://issues.jenkins-ci.org/browse/JENKINS-4550 https://issues.jenkins-ci.org/browse/JENKINS-5436 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] [redmine] (JENKINS-18021) redmine user authorization
cforce created JENKINS-18021 redmine user authorization Issue Type: New Feature Assignee: gaooh Components: redmine Created: 21/May/13 8:18 AM Description: The redmine plugin already allows mapping of job to redmine projects. If this plugin would allow mapping of redmine roles to jekins roles (Role based strategy), than user of redmine project with speical roles can autoamtcially get access to nmapped jobs and mapped roles in jenkins This would mean single authentification (already implemeneted) and single authorization (this feature request)! See also https://github.com/mattshep2000/jenkins-redmine-auth/issues/4 Project: Jenkins Priority: Major Reporter: cforce 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-13806) View update deadlock freezes the UI for all users
evernat resolved JENKINS-13806 as Fixed View update deadlock freezes the UI for all users The pull request is merged, so resolving as fixed. Change By: evernat (21/May/13 8:24 AM) 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/groups/opt_out.
[JIRA] [envinject] (JENKINS-16882) Job-B ${WORKSPACE} has value of Job-A WORKSPACE
Sven Appenrodt commented on JENKINS-16882 Job-B ${WORKSPACE} has value of Job-A WORKSPACE Seems the problem can be reproduced only after the second run (but i'm not sure) The biggest problem is, the workspace of each job triggered by the fsp will be overwritten permanently. Example: Job A (fstrigger) - Job B - Job C Job 1 (normal time trigger) - Job 2 - Job C It doesnt matter if Job C is triggered by Job A or 1 - the WORKSPACE variable is set to "workspace\Job A" everytime. 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] [role-strategy] (JENKINS-17482) Support folders
cforce commented on JENKINS-17482 Support folders Then the "Role-based Access Control plugin" shall also support authorization on folders levels instead of job name regexpressions. 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] [role-strategy] (JENKINS-15031) Use view tabs to assign roles to projects
cforce commented on JENKINS-15031 Use view tabs to assign roles to projects The project-role mapping and the views-projects mapping shall stay data, but reusing the mapping in views makes 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/groups/opt_out.
[JIRA] [jobconfighistory] (JENKINS-18022) Matrix jobs fail when Config History is installed
Stefan Brausch assigned JENKINS-18022 to Stefan Brausch Matrix jobs fail when Config History is installed Change By: Stefan Brausch (21/May/13 8:44 AM) Assignee: MirkoFriedenhagen StefanBrausch 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] [jobconfighistory] (JENKINS-18022) Matrix jobs fail when Config History is installed
Stefan Brausch assigned JENKINS-18022 to Kathi Stutz Matrix jobs fail when Config History is installed @Kathi: please try to reproduce this issue Change By: Stefan Brausch (21/May/13 8:48 AM) Assignee: StefanBrausch KathiStutz 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] [jobconfighistory] (JENKINS-18022) Matrix jobs fail when Config History is installed
Stefan Brausch commented on JENKINS-18022 Matrix jobs fail when Config History is installed @James: Do you have some more information in your jenkins instance log file? 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] [dashboard-view] (JENKINS-18023) dashboard -view does not honour the prefix commandline parameter
Bob Verbrugge created JENKINS-18023 dashboard -view does not honour the prefix commandline parameter Issue Type: Bug Affects Versions: current Assignee: Peter Hayes Components: dashboard-view Created: 21/May/13 8:57 AM Description: Wrong URLs are used to access the buid stability images, looks like the --prefix commandline setting is not honoured. For example the following URL is used: http://server/static/0eb6924c/images/16x16/health-80plus.png instead of http://server/jenkins/static/0eb6924c/images/16x16/health-80plus.png --prefix=/jenkins is set in jenkins.xml Environment: jenkins 1.514 behind Apache , dashboard-view 2.6 Project: Jenkins Labels: jenkins plugin Priority: Major Reporter: Bob Verbrugge 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] [matrix] (JENKINS-18024) NPE running matrix job
Chris Withers created JENKINS-18024 NPE running matrix job Issue Type: Bug Assignee: Unassigned Components: matrix Created: 21/May/13 8:58 AM Description: Got this from one run of one of our matrix builds: FATAL: null java.lang.NullPointerException at hudson.matrix.DefaultMatrixExecutionStrategyImpl.waitForCompletion(DefaultMatrixExecutionStrategyImpl.java:241) at hudson.matrix.DefaultMatrixExecutionStrategyImpl.run(DefaultMatrixExecutionStrategyImpl.java:163) at hudson.matrix.MatrixBuild$MatrixBuildExecution.doRun(MatrixBuild.java:340) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:500) at hudson.model.Run.execute(Run.java:1502) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:289) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) at hudson.model.OneOffExecutor.run(OneOffExecutor.java:66) Environment: Jenkins 1.480.3 Project: Jenkins Priority: Major Reporter: Chris Withers 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-17684) Dashboard web pages don't render correctly in Chrome because of bad cache/session
Kevin Cross updated JENKINS-17684 Dashboard web pages dont render correctly in Chrome because of bad cache/session Seeing the same issue with Jenkins 1.509.1 running as a native package on CentOS release 6.4. Ctrl-shift-R seems to fix the issue. Attaching jenkins_css_3.PNG. Chrome Version 26.0.1410.64 m. Change By: Kevin Cross (21/May/13 8:58 AM) Attachment: jenkins_css_3.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/groups/opt_out.
[JIRA] [git] (JENKINS-17700) Windows: Git clone fails on computer with multiple executors or slaves
Tomas Hellberg resolved JENKINS-17700 as Not A Defect Windows: Git clone fails on computer with multiple executors or slaves After more debugging, we observe the same problem while executing git directly outside the plugin, so it is not a Git plugin issue. Closing as Not A Defect. Change By: Tomas Hellberg (21/May/13 9:07 AM) Status: Open Resolved 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/groups/opt_out.
[JIRA] [matrix] (JENKINS-18024) NPE running matrix job
Chris Withers commented on JENKINS-18024 NPE running matrix job As an obvservation, the queue length in our Jenkins cluster was fairly long when this occurred. Could that be related? 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] [matrix] (JENKINS-18024) NPE running matrix job
Chris Withers edited a comment on JENKINS-18024 NPE running matrix job As an observation, the queue length in our Jenkins cluster was fairly long when this occurred. Could that be related? 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] [subversion] (JENKINS-14550) Checksum mismatch while updating with Subversion Plugin 1.42
Nicola Tarbet commented on JENKINS-14550 Checksum mismatch while updating with Subversion Plugin 1.42 We can reliably reproduce the issue by renaming and then modifying the file. On Jenkins ver. 1.514, Subversion plugin 1.45, svnkit 1.7.6 check out strategy: Use 'svn update' as much as possible We had to downgrade to Subversion plugin 1.39. For those wondering how to get their downgrade to stick you need to "pin" the downgraded plugin https://wiki.jenkins-ci.org/display/JENKINS/Pinned+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 -- 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] [cvs] (JENKINS-17656) CVS symbolic name parameter
Nicolas Martin commented on JENKINS-17656 CVS symbolic name parameter Hello, "I'm probably going to perform a release of the CVS plugin at the end of the month" Any update regarding this release ? thanks a lot 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] [testflight] (JENKINS-17592) Testflight uploader plugin doesn't allow to upload multiple files
lacostej commented on JENKINS-17592 Testflight uploader plugin doesnt allow to upload multiple files I've implemented some wildcard support here: https://github.com/lacostej/testflight-plugin/commit/289c25c05b4bcc130d5b45da4d9b032b40c04d51 https://github.com/lacostej/testflight-plugin/tree/jl_wildcards I need to test it a bit more. 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] [all-changes] (JENKINS-17349) CPU on master node keeps increasing and never come down
Daniel Pinyol commented on JENKINS-17349 CPU on master node keeps increasing and never come down We have this issue too with 1.514 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] [android-emulator] (JENKINS-17997) Installation of Android SDK gives up after not confirming the License query 100 times.
Christopher Orr commented on JENKINS-17997 Installation of Android SDK gives up after not confirming the License query 100 times. Related: https://github.com/jenkinsci/android-emulator-plugin/pull/22 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-17553) Archived artifacts of Maven Modules are no longer cleaned up
Henrik Horneber commented on JENKINS-17553 Archived artifacts of Maven Modules are no longer cleaned up Still broken in 1.509.1 LTS. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18011) Deadlock issue remote slaves
Marcus Jacobsson updated JENKINS-18011 Deadlock issue remote slaves Change By: Marcus Jacobsson (21/May/13 10:50 AM) Description: JenkinsslavesrunningonWindowshaveatendencytodeadlockwhenprogramsaresendingalotofdatasimultaneously.ReadingthethreaddumpfromVisualVMwecanseethatproc.javatriestowritetodeadlockstreamresultinginhangingbuildsStringmsg=Processleakedfiledescriptors.Seehttp://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+buildformoreinformation;Throwablee=newException().fillInStackTrace();LOGGER.log(Level.WARNING,msg,e); {code} pool-1-thread-833-Threadt@1926010java.lang.Thread.State:BLOCKED atjava.util.logging.StreamHandler.publish(UnknownSource) -waitingtolock1502546(ajava.util.logging.ConsoleHandler)ownedbypool-1-thread-927t@1926604 atjava.util.logging.ConsoleHandler.publish(UnknownSource) atjava.util.logging.Logger.log(UnknownSource) atjava.util.logging.Logger.doLog(UnknownSource) atjava.util.logging.Logger.log(UnknownSource) athudson.Proc$LocalProc.join(Proc.java:330) athudson.Launcher$RemoteLaunchCallable$1.join(Launcher.java:993) atsun.reflect.GeneratedMethodAccessor127.invoke(UnknownSource) atsun.reflect.DelegatingMethodAccessorImpl.invoke(UnknownSource) atjava.lang.reflect.Method.invoke(UnknownSource) athudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:275) athudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:256) athudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:215) athudson.remoting.UserRequest.perform(UserRequest.java:118) athudson.remoting.UserRequest.perform(UserRequest.java:48) athudson.remoting.Request$2.run(Request.java:326) athudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) atjava.util.concurrent.FutureTask$Sync.innerRun(UnknownSource) atjava.util.concurrent.FutureTask.run(UnknownSource) atjava.util.concurrent.ThreadPoolExecutor.runWorker(UnknownSource) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(UnknownSource) athudson.remoting.Engine$1$1.run(Engine.java:58) atjava.lang.Thread.run(UnknownSource) {code} 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-18011) Deadlock issue remote slaves
Marcus Jacobsson updated JENKINS-18011 Deadlock issue remote slaves Change By: Marcus Jacobsson (21/May/13 10:51 AM) Description: JenkinsslavesrunningonWindowshaveatendencytodeadlockwhenprogramsaresendingalotofdatasimultaneously.ReadingthethreaddumpfromVisualVMwecanseethatproc.javatriestowritetodeadlockstreamresultinginhangingbuilds {code} Stringmsg=Processleakedfiledescriptors.Seehttp://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+buildformoreinformation;Throwablee=newException().fillInStackTrace();LOGGER.log(Level.WARNING,msg,e); {code} {code}pool-1-thread-833-Threadt@1926010java.lang.Thread.State:BLOCKED atjava.util.logging.StreamHandler.publish(UnknownSource) -waitingtolock1502546(ajava.util.logging.ConsoleHandler)ownedbypool-1-thread-927t@1926604 atjava.util.logging.ConsoleHandler.publish(UnknownSource) atjava.util.logging.Logger.log(UnknownSource) atjava.util.logging.Logger.doLog(UnknownSource) atjava.util.logging.Logger.log(UnknownSource) athudson.Proc$LocalProc.join(Proc.java:330) athudson.Launcher$RemoteLaunchCallable$1.join(Launcher.java:993) atsun.reflect.GeneratedMethodAccessor127.invoke(UnknownSource) atsun.reflect.DelegatingMethodAccessorImpl.invoke(UnknownSource) atjava.lang.reflect.Method.invoke(UnknownSource) athudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:275) athudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:256) athudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:215) athudson.remoting.UserRequest.perform(UserRequest.java:118) athudson.remoting.UserRequest.perform(UserRequest.java:48) athudson.remoting.Request$2.run(Request.java:326) athudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) atjava.util.concurrent.FutureTask$Sync.innerRun(UnknownSource) atjava.util.concurrent.FutureTask.run(UnknownSource) atjava.util.concurrent.ThreadPoolExecutor.runWorker(UnknownSource) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(UnknownSource) athudson.remoting.Engine$1$1.run(Engine.java:58) atjava.lang.Thread.run(UnknownSource){code} 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-18011) Deadlock issue remote slaves
Marcus Jacobsson edited a comment on JENKINS-18011 Deadlock issue remote slaves Full thread dump Java HotSpot(TM) Client VM (23.7-b01 mixed mode): "RMI TCP Connection(7)-10.158.226.24" - Thread t@1933099 java.lang.Thread.State: RUNNABLE at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(Unknown Source) at java.net.SocketInputStream.read(Unknown Source) at java.io.BufferedInputStream.fill(Unknown Source) at java.io.BufferedInputStream.read(Unknown Source) - locked 9adbe1 (a java.io.BufferedInputStream) at java.io.FilterInputStream.read(Unknown Source) at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown Source) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Locked ownable synchronizers: - locked 1647392 (a java.util.concurrent.ThreadPoolExecutor$Worker) "pool-1-thread-1016" - Thread t@1933098 java.lang.Thread.State: TIMED_WAITING at sun.misc.Unsafe.park(Native Method) - parking to wait for 9aa718 (a java.util.concurrent.SynchronousQueue$TransferStack) at java.util.concurrent.locks.LockSupport.parkNanos(Unknown Source) at java.util.concurrent.SynchronousQueue$TransferStack.awaitFulfill(Unknown Source) at java.util.concurrent.SynchronousQueue$TransferStack.transfer(Unknown Source) at java.util.concurrent.SynchronousQueue.poll(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.getTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:58) at java.lang.Thread.run(Unknown Source) Locked ownable synchronizers: - None "RMI TCP Connection(6)-10.158.226.24" - Thread t@1933097 java.lang.Thread.State: RUNNABLE at sun.management.ThreadImpl.dumpThreads0(Native Method) at sun.management.ThreadImpl.dumpAllThreads(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.sun.jmx.mbeanserver.ConvertingMethod.invokeWithOpenReturn(Unknown Source) at com.sun.jmx.mbeanserver.ConvertingMethod.invokeWithOpenReturn(Unknown Source) at com.sun.jmx.mbeanserver.MXBeanIntrospector.invokeM2(Unknown Source) at com.sun.jmx.mbeanserver.MXBeanIntrospector.invokeM2(Unknown Source) at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(Unknown Source) at com.sun.jmx.mbeanserver.PerInterface.invoke(Unknown Source) at com.sun.jmx.mbeanserver.MBeanSupport.invoke(Unknown Source) at javax.management.StandardMBean.invoke(Unknown Source) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(Unknown Source) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl.doOperation(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl.access$300(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl.invoke(Unknown Source) at sun.reflect.GeneratedMethodAccessor174.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source) at sun.rmi.transport.Transport$1.run(Unknown Source) at sun.rmi.transport.Transport$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Unknown Source) at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown Source) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Locked ownable synchronizers: - locked 7d7a7c (a
[JIRA] [postbuild-task] (JENKINS-16428) no 'delete' button on some post-built actions sometimes
aj2 commented on JENKINS-16428 no delete button on some post-built actions sometimes I observed this issue when moving Jenkins to another server while upgrading from 1.479 to 1.509.1. It was fixed by installing a missing plugin (parametrized trigger 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/groups/opt_out.
[JIRA] [jobconfighistory] (JENKINS-18022) Matrix jobs fail when Config History is installed
Kathi Stutz commented on JENKINS-18022 Matrix jobs fail when Config History is installed This is a duplicate of Jenkins 16601, which was caused by a bug in the Jenkins core. You can either use a newer version of Jenkins or version 2.2 or 2.3 of the JobConfigHistory plugin, which still contain a workaround for the core 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 -- 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] [jobconfighistory] (JENKINS-18022) Matrix jobs fail when Config History is installed
Kathi Stutz resolved JENKINS-18022 as Duplicate Matrix jobs fail when Config History is installed Change By: Kathi Stutz (21/May/13 11:37 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] [dashboard-view] (JENKINS-18025) View: when Recurse in subfolders is true, view is empty and logs full of java.lang.ClassCastException: hudson.maven.MavenModule cannot be cast to hudson.model
Reynald Borer created JENKINS-18025 View: when Recurse in subfolders is true, view is empty and logs full of java.lang.ClassCastException: hudson.maven.MavenModule cannot be cast to hudson.model.TopLevelItem Issue Type: Bug Assignee: Peter Hayes Components: dashboard-view Created: 21/May/13 11:49 AM Description: One of my dashboard view is defined like the following hudson.plugins.view.dashboard.Dashboard plugin="dashboard-view@2.5" owner class="hudson" reference="../../.."/ name+Continuous Integration/name filterExecutorsfalse/filterExecutors filterQueuefalse/filterQueue properties class="hudson.model.View$PropertyList"/ jobNames comparator class="hudson.util.CaseInsensitiveComparator"/ /jobNames jobFilters/ columns hudson.views.StatusColumn/ hudson.views.WeatherColumn/ hudson.views.JobColumn/ hudson.views.LastSuccessColumn/ hudson.views.LastFailureColumn/ hudson.views.LastDurationColumn/ hudson.views.BuildButtonColumn/ de.fspengler.hudson.pview.ConsoleViewColumn plugin="hudson-pview-plugin@1.8"/ hudson.plugins.projectstats.column.NumBuildsColumn plugin="project-stats-plugin@0.4"/ /columns includeRegex(?!(_env_.*|.*single_selenium_test.*|stx2|apache|check|nexus|ocs)).*/includeRegex recursetrue/recurse useCssStylefalse/useCssStyle includeStdJobListfalse/includeStdJobList leftPortletWidth50%/leftPortletWidth rightPortletWidth50%/rightPortletWidth leftPortlets/ rightPortlets/ topPortlets hudson.plugins.view.dashboard.core.JobsPortlet iddashboard_portlet_6828/id nameJobs Grid/name /hudson.plugins.view.dashboard.core.JobsPortlet /topPortlets bottomPortlets/ /hudson.plugins.view.dashboard.Dashboard When I try to load this view, the job list is empty. The logs are full of the following exception: WARNING: Caught exception evaluating: it.allViewJobNamesAsJson in /jenkins/. Reason: java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly.parser.EscapingExpression.evaluate(EscapingExpression.java:24) at org.apache.commons.jelly.impl.ExpressionScript.run(ExpressionScript.java:66) 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.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:146) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at
[JIRA] [clearcase-ucm] (JENKINS-18026) Baseline not loaded when paramerized, 9320
Christian Wolfgang created JENKINS-18026 Baseline not loaded when paramerized, 9320 Issue Type: Bug Assignee: Praqma Support Components: clearcase-ucm Created: 21/May/13 11:57 AM Project: Jenkins Priority: Major Reporter: Christian Wolfgang 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] [matrix] (JENKINS-18024) NPE running matrix job
Jesse Glick started work on JENKINS-18024 NPE running matrix job Change By: Jesse Glick (21/May/13 11:58 AM) Status: Open InProgress 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] [matrix] (JENKINS-18024) NPE running matrix job
Jesse Glick updated JENKINS-18024 NPE running matrix job Change By: Jesse Glick (21/May/13 11:58 AM) URL: https://github.com/jenkinsci/jenkins/pull/785 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] [role-strategy] (JENKINS-17482) Support folders
Jesse Glick commented on JENKINS-17482 Support folders PR #1 does allow it to do that, since the match is against the job fullName. 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] [junit] (JENKINS-13709) ClassCast Exception when parsing JUnit surefire reports during website generation
Brett Delle Grazie commented on JENKINS-13709 ClassCast Exception when parsing JUnit surefire reports during website generation I'm experiencing this too on Windows XP slave, Windows 2008 sp2 server, java 7, maven 3.0.4 Similar stack trace: hudson.util.IOException2: Failed to read redacted-file-path\target\surefire-reports\TEST-redacted-testclass-name.xml at hudson.tasks.junit.TestResult.parse(TestResult.java:284) at hudson.tasks.junit.TestResult.parsePossiblyEmpty(TestResult.java:223) at hudson.tasks.junit.TestResult.parse(TestResult.java:192) at hudson.maven.reporters.SurefireArchiver.postExecute(SurefireArchiver.java:148) at hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoEnded(Maven3Builder.java:453) at hudson.maven.Maven3Builder$MavenExecutionListener.mojoSucceeded(Maven3Builder.java:435) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:87) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:228) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.MojoExecutor.executeForkedExecutions(MojoExecutor.java:365) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeForkedExecutions(DefaultLifecycleExecutor.java:173) at org.apache.maven.reporting.exec.DefaultMavenReportExecutor.buildReportPlugin(DefaultMavenReportExecutor.java:273) at org.apache.maven.reporting.exec.DefaultMavenReportExecutor.buildMavenReports(DefaultMavenReportExecutor.java:154) at org.apache.maven.plugins.site.AbstractSiteRenderingMojo.getReports(AbstractSiteRenderingMojo.java:235) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:121) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239) at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158) at hudson.maven.Maven3Builder.call(Maven3Builder.java:100) at hudson.maven.Maven3Builder.call(Maven3Builder.java:66) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) 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:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:662) Caused by: org.dom4j.DocumentException: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory Nested exception: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory at org.dom4j.io.SAXReader.read(SAXReader.java:484) at org.dom4j.io.SAXReader.read(SAXReader.java:264) at
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-18027) HP Application Automation Tools no longer works with latest Jenkins update
Hwa Truong created JENKINS-18027 HP Application Automation Tools no longer works with latest Jenkins update Issue Type: Bug Affects Versions: current Assignee: Ofir Shaked Components: hp-application-automation-tools-plugin Created: 21/May/13 2:20 PM Description: This plugin stopped working with the last two latest versions of Jenkins. I get and old data error for the existing tests, and if I attempt to create a new job with this HP step in the build, I get just a black screen when I save. Due Date: 26/May/13 12:00 AM Environment: Linux x86_64 Project: Jenkins Priority: Critical Reporter: Hwa Truong 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] [publish-over-ssh] (JENKINS-17058) Publish over SSH plugin XML configuration cannot be read on jenkins start up.
Preston Gilchrist commented on JENKINS-17058 Publish over SSH plugin XML configuration cannot be read on jenkins start up. This continues to be a painful issue. Are the code fixes mentioned in the thread not candidates for release? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-17884) Support CTest XML format
Gregoire AUJAY closed JENKINS-17884 as Fixed Support CTest XML format Closing this issue as it seems to work fine. Change By: Gregoire AUJAY (21/May/13 2:41 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] [cppcheck] (JENKINS-18029) In CppCheck plugin desired line with static analysis violation is hidden because breadcrumb covers it
Jan Magur created JENKINS-18029 In CppCheck plugin desired line with static analysis violation is hidden because breadcrumb covers it Issue Type: Bug Assignee: Gregory Boissinot Attachments: 1_select_violation.png, 2_desired_line_is_hidden.png, 3_after_scrolling_line_is_visible.png Components: cppcheck Created: 21/May/13 2:58 PM Description: see self-explained screenshots Project: Jenkins Priority: Major Reporter: Jan Magur 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] [envinject] (JENKINS-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
Jesse Glick commented on JENKINS-15779 Parsing ivy descriptors step fails on a slave when custom ivy settings file is used https://github.com/jenkinsci/ivy-plugin/compare/ivy-descriptors is the more useful link by the way. 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-16499) NPE when new job by copy from existing one
James Monroe updated JENKINS-16499 NPE when new job by copy from existing one Change By: James Monroe (21/May/13 3:16 PM) Component/s: jobconfighistory 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] [jobconfighistory] (JENKINS-18022) Matrix jobs fail when Config History is installed
James Monroe closed JENKINS-18022 as Duplicate Matrix jobs fail when Config History is installed Change By: James Monroe (21/May/13 3:23 PM) Status: Resolved Closed Assignee: KathiStutz JamesMonroe 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] [jobconfighistory] (JENKINS-18022) Matrix jobs fail when Config History is installed
James Monroe commented on JENKINS-18022 Matrix jobs fail when Config History is installed thanks! 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] [ircbot] (JENKINS-17419) Added configuration option to disallow bot commands from private chat.
SCM/JIRA link daemon commented on JENKINS-17419 Added configuration option to disallow bot commands from private chat. Code changed in jenkins User: Christoph Kutzinski Path: src/main/java/hudson/plugins/ircbot/IrcPublisher.java src/main/java/hudson/plugins/ircbot/v2/IRCConnection.java src/main/resources/hudson/plugins/ircbot/IrcPublisher/global.jelly http://jenkins-ci.org/commit/ircbot-plugin/15141254748d8bfb074a0978afde1d15ccad92af Log: Merge pull request #6 from askeing/disallowPrivateChatCommands JENKINS-17419 Added new configuration option to disallow bot commands from private chat. Compare: https://github.com/jenkinsci/ircbot-plugin/compare/323ab68fc572...15141254748d 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] [ircbot] (JENKINS-17419) Added configuration option to disallow bot commands from private chat.
kutzi resolved JENKINS-17419 as Fixed Added configuration option to disallow bot commands from private chat. Change By: kutzi (21/May/13 3:44 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/groups/opt_out.
[JIRA] [subversion] (JENKINS-10771) hudson.util.IOException2: remote file operation failed
Jesse Glick updated JENKINS-10771 hudson.util.IOException2: remote file operation failed Change By: Jesse Glick (21/May/13 4:38 PM) Component/s: subversion Component/s: master-slave 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-17684) Dashboard web pages don't render correctly in Chrome because of bad cache/session
Tomonari Nakamura commented on JENKINS-17684 Dashboard web pages dont render correctly in Chrome because of bad cache/session I think that a problem may be sending content-type header when http response is 304 in winstone. Looking a capture http://imgur.com/9Y11bqz, css files are interpreted as 'text/html', but should be 'text/css'. According to RFC, the 304 response should not include non-releated header. If the conditional GET used a strong cache validator (see section 13.3.3), the response SHOULD NOT include other entity-headers. Otherwise (i.e., the conditional GET used a weak validator), the response MUST NOT include other entity-headers; this prevents inconsistencies between cached entity-bodies and updated headers. For example, Plack ( which is web app framework by Perl ) excludes Content-Type / Content-Length / Content-Disposition headers. https://metacpan.org/source/MIYAGAWA/Plack-1.0024/lib/Plack/Middleware/ConditionalGET.pm#L19 So, I fix a source code to exclude content-type when 304, and trying it in my using Jenkins server. https://github.com/ikikko/winstone/commit/1fedebd8095de85a378640f71c3de4bce2e25cae If no problem for a week, I'll send a pull request this. Currently, content-type header is normal and no problem occurs for three days. https://cacoo.com/diagrams/J5lvJfdIi8t9UCof It's ok that you fix in main repository source code before sending my pull request. At which time, consider about other headers (Content-length, content-disposition, and so on), please. 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-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
Gregory Boissinot updated JENKINS-15779 Parsing ivy descriptors step fails on a slave when custom ivy settings file is used Change By: Gregory Boissinot (21/May/13 4:48 PM) Component/s: envinject This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cppcheck] (JENKINS-18029) In CppCheck plugin desired line with static analysis violation is hidden because breadcrumb covers it
Gregory Boissinot commented on JENKINS-18029 In CppCheck plugin desired line with static analysis violation is hidden because breadcrumb covers it I'm sorry I don't understand the issue. 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-17684) Dashboard web pages don't render correctly in Chrome because of bad cache/session
Christopher Orr commented on JENKINS-17684 Dashboard web pages dont render correctly in Chrome because of bad cache/session Nice! That sounds like a plausible explanation, and other people are having similar problems with Chrome: http://productforums.google.com/forum/#!msg/chrome/zID6uQQfKH8/AOUiKiAp8fwJ https://code.google.com/p/chromium/issues/detail?id=176430 I guess everybody here seeing this issue is running Winstone? 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] [subversion] (JENKINS-10771) hudson.util.IOException2: remote file operation failed
Robert Clark commented on JENKINS-10771 hudson.util.IOException2: remote file operation failed @Jesse Glick: I think "component=subversion" is incorrect. The original report happened to be during a Subversion checkout, but many follow up reports show this problem occurring all over the code base. I know I've see it during checkouts, builds, archiving, general file transfer, unit tests, etc. 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-17910) groovy.lang.MissingMethodException in sidepanel.jelly
Steven Deal commented on JENKINS-17910 groovy.lang.MissingMethodException in sidepanel.jelly I'm not familiar with groovy; but, why would this work immediately after a restart and then break at a later time? 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] [maven2] (JENKINS-18030) Unable to parameterized Maven module build
Adrien Vercoutere created JENKINS-18030 Unable to parameterized Maven module build Issue Type: Bug Affects Versions: current Assignee: huybrechts Attachments: Parameterized-Module-Build.png Components: maven2, parameterized-trigger, parameters Created: 21/May/13 5:02 PM Description: I'm able to configure some parameters for a Maven module build (with the "Jenkins Parameterized Trigger plugin") but when trying to execute a maven module directly, parameters are not passed. Here's the Console Output : Executing Maven: -N -B -f /var/lib/jenkins/customWorkspaces/SOAPUI/Google/Divers/pom.xml clean integration-test -P $Environnement "$Environnement" should be replaced by the parameter value. Project: Jenkins Labels: build plugins parameterized Priority: Major Reporter: Adrien Vercoutere 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-17910) groovy.lang.MissingMethodException in sidepanel.jelly
Geoff Cummings commented on JENKINS-17910 groovy.lang.MissingMethodException in sidepanel.jelly My errors dont always mention sidepanel, see above for 2 examples... But posting this in the chance they may be related: They only seem to happen with Email Ext plugin version 2.29 installed, and only after one of my jobs triggers an email using this plugin. I have it configured to use a custom groovy template. Initial testing suggests the error doesnt happen if it sends a blank email instead of using the template.. I do not see the error if I downgrade the plugin to 2.28 Does anyone else have a similar setup? Do you use this 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/groups/opt_out.
[JIRA] [core] (JENKINS-17684) Dashboard web pages don't render correctly in Chrome because of bad cache/session
Justin Patrin commented on JENKINS-17684 Dashboard web pages dont render correctly in Chrome because of bad cache/session I can confirm that we are using jenkins "standalone" (jenkins.war), which apparently uses Winstone. Are you saying that if we used something else, like Tomcat, this problem would go away? 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-17910) groovy.lang.MissingMethodException in sidepanel.jelly
Steven Deal commented on JENKINS-17910 groovy.lang.MissingMethodException in sidepanel.jelly I use Email Ext and did upgrade to 2.29. I cannot say with confidence if this issue started with that upgrade. I noticed email-ext in a thread dump of another issue I'm currently having and did try to downgrade. However, I just noticed that my jenkins instance still appears to be running 2.29 and I no longer have the 'downgrade' option on the plugins screen. Guess I'll have to search around for the older email-ext.jpi. I'll certainly update this thread if a down grade resolves 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 -- 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-17910) groovy.lang.MissingMethodException in sidepanel.jelly
Alex Earl commented on JENKINS-17910 groovy.lang.MissingMethodException in sidepanel.jelly Intriguing, I develop the email-ext plugin, I'll double check what changed from 2.28 to 2.29 in regards to groovy stuff. 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-17910) groovy.lang.MissingMethodException in sidepanel.jelly
Alex Earl commented on JENKINS-17910 groovy.lang.MissingMethodException in sidepanel.jelly Can you try this version of email-ext 2.29 with a reference to groovy removed from the pom.xml? http://earl-of-code.com/jenkins-dev/email-ext.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 -- 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] [configurationslicing] (JENKINS-15934) NPE when trying to open Delete workspace when build is done
Laurent Denanot commented on JENKINS-15934 NPE when trying to open Delete workspace when build is done Hi, I had the same problem and found an easy cure: Looks like it simply is a case of bad dependency qualification: the NPE is due to the fact that the 'Delete workspace' features depend on the 'ws-cleanup' plugin (https://wiki.jenkins-ci.org/display/JENKINS/Workspace+Cleanup+Plugin) that is listed as an optional dependency of the Configuration Slicing plugin, whereas it really should be listed as a required one... The alternative being adding logic to the Configuration Slicing plugin that automatically detects whether the 'ws-cleanup' plugin is installed and enables or disables the associated 'delete workspace... ' options accordingly. Anyways: Without the 'ws-cleanup' installed : clicking on any of the 'Delete workspace...' links in Configuraiton slicing triggers an NPE. With the 'ws-cleanup' installed: no more NPEs, the configuration pages for the 'Delete workspace...' options get displayed as expected... Hope this helps, Laurent 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] [configurationslicing] (JENKINS-15934) NPE when trying to open Delete workspace when build is done
Laurent Denanot edited a comment on JENKINS-15934 NPE when trying to open Delete workspace when build is done Hi, I had the same problem and found an easy cure: Looks like it simply is a case of bad dependency qualification: the NPE is due to the fact that the 'Delete workspace' features depend on the 'ws-cleanup' plugin (https://wiki.jenkins-ci.org/display/JENKINS/Workspace+Cleanup+Plugin) that is listed as an optional dependency of the Configuration Slicing plugin, whereas it really should be listed as a required one... The alternative being adding logic to the Configuration Slicing plugin that automatically detects whether the 'ws-cleanup' plugin is installed and enables or disables the associated 'delete workspace... ' options accordingly. Anyways: Without the 'ws-cleanup' installed : clicking on any of the 'Delete workspace...' links in Configuraiton slicing triggers an NPE. With the 'ws-cleanup' installed: no more NPEs, the configuration pages for the 'Delete workspace...' options get displayed as expected... Hope this helps, Laurent PS: I'm running Jenkins v 1.512 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] [configurationslicing] (JENKINS-15934) NPE when trying to open Delete workspace when build is done
Laurent Denanot edited a comment on JENKINS-15934 NPE when trying to open Delete workspace when build is done Hi, I had the same problem and found an easy cure: Looks like it simply is a case of bad dependency qualification: the NPE is due to the fact that the 'Delete workspace' features depend on the 'ws-cleanup' plugin (https://wiki.jenkins-ci.org/display/JENKINS/Workspace+Cleanup+Plugin) that is listed as an optional dependency of the Configuration Slicing plugin, whereas it really should be listed as a required one... The alternative being adding logic to the Configuration Slicing plugin that automatically detects whether the 'ws-cleanup' plugin is installed and enables or disables the associated 'delete workspace... ' options accordingly. Anyways: Without the 'ws-cleanup' plugin installed : clicking on any of the 'Delete workspace...' links in Configuraiton slicing triggers an NPE. With the 'ws-cleanup' plugin installed: no more NPEs, the configuration pages for the 'Delete workspace...' options work as expected... Hope this helps, Laurent PS: I'm running Jenkins v 1.512 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] [configurationslicing] (JENKINS-15934) NPE when trying to open Delete workspace when build is done
Laurent Denanot edited a comment on JENKINS-15934 NPE when trying to open Delete workspace when build is done Hi, I had the same problem and found an easy cure: Looks like it simply is a case of bad dependency qualification: the NPE is due to the fact that the 'Delete workspace' features depend on the 'ws-cleanup' (Workspace Cleanup) plugin (https://wiki.jenkins-ci.org/display/JENKINS/Workspace+Cleanup+Plugin) that is listed as an optional dependency of the Configuration Slicing plugin, whereas it really should be listed as a required one... The alternative being adding logic to the Configuration Slicing plugin that automatically detects whether the 'ws-cleanup' plugin is installed and enables or disables the associated 'delete workspace... ' options accordingly. Anyways: Without the 'ws-cleanup' plugin installed : clicking on any of the 'Delete workspace...' links in Configuration slicing triggers an NPE. With the 'ws-cleanup' plugin installed: no more NPEs, the configuration pages for the 'Delete workspace...' options work as expected... Hope this helps, Laurent PS: I'm running Jenkins v 1.512 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] [configurationslicing] (JENKINS-15934) NPE when trying to open Delete workspace when build is done
Laurent Denanot edited a comment on JENKINS-15934 NPE when trying to open Delete workspace when build is done Hi, I had the same problem and found an easy cure: Looks like it simply is a case of bad dependency qualification: the NPE is due to the fact that the 'Delete workspace' features depend on the 'ws-cleanup' (Workspace Cleanup) plugin (see https://wiki.jenkins-ci.org/display/JENKINS/Workspace+Cleanup+Plugin) that is listed as an optional dependency of the Configuration Slicing plugin, whereas it really should be listed as a required one... The alternative being adding logic to the Configuration Slicing plugin that automatically detects whether the 'ws-cleanup' plugin is installed and enables or disables the associated 'delete workspace... ' options accordingly. Anyways: Without the 'ws-cleanup' plugin installed : clicking on any of the 'Delete workspace...' links in Configuration slicing triggers an NPE. With the 'ws-cleanup' plugin installed: no more NPEs, the configuration pages for the 'Delete workspace...' options work as expected... Hope this helps, Laurent PS: I'm running Jenkins v 1.512 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-17910) groovy.lang.MissingMethodException in sidepanel.jelly
Alex Earl edited a comment on JENKINS-17910 groovy.lang.MissingMethodException in sidepanel.jelly Can you try this version of email-ext 2.29.1 with a reference to groovy removed from the pom.xml? http://earl-of-code.com/jenkins-dev/email-ext.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 -- 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-17030) Display long job names without breaking Jenkins layout
SCM/JIRA link daemon commented on JENKINS-17030 Display long job names without breaking Jenkins layout Code changed in jenkins User: Oliver Gondža Path: core/src/main/java/hudson/Functions.java core/src/main/resources/hudson/matrix/MatrixProject/index.jelly core/src/main/resources/hudson/model/Job/index.jelly core/src/main/resources/hudson/views/JobColumn/column.jelly core/src/main/resources/lib/hudson/buildListTable.jelly core/src/main/resources/lib/hudson/executors.jelly core/src/main/resources/lib/hudson/jobLink.jelly core/src/main/resources/lib/hudson/queue.jelly core/src/main/resources/lib/layout/breakable.jelly core/src/test/java/hudson/FunctionsTest.java http://jenkins-ci.org/commit/jenkins/2c240bdc876e74fe7a4a1ebeb5e3707e2d8f7bf3 Log: FIXED JENKINS-17030 Enable word breaking for job names 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-17030) Display long job names without breaking Jenkins layout
SCM/JIRA link daemon resolved JENKINS-17030 as Fixed Display long job names without breaking Jenkins layout Change By: SCM/JIRA link daemon (21/May/13 6:05 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/groups/opt_out.
[JIRA] [core] (JENKINS-17030) Display long job names without breaking Jenkins layout
SCM/JIRA link daemon commented on JENKINS-17030 Display long job names without breaking Jenkins layout Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/Functions.java core/src/main/resources/lib/layout/breakable.jelly core/src/test/java/hudson/FunctionsTest.java http://jenkins-ci.org/commit/jenkins/b5d96e27dd8c0aa5f5c50aa2260f3369d1d758a4 Log: JENKINS-17030 Noting, fixing/adding @since, adding @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 -- 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-17030) Display long job names without breaking Jenkins layout
SCM/JIRA link daemon commented on JENKINS-17030 Display long job names without breaking Jenkins layout Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/Functions.java core/src/main/resources/hudson/matrix/MatrixProject/index.jelly core/src/main/resources/hudson/model/Job/index.jelly core/src/main/resources/hudson/views/JobColumn/column.jelly core/src/main/resources/lib/hudson/buildListTable.jelly core/src/main/resources/lib/hudson/executors.jelly core/src/main/resources/lib/hudson/jobLink.jelly core/src/main/resources/lib/hudson/queue.jelly core/src/main/resources/lib/layout/breakable.jelly core/src/test/java/hudson/FunctionsTest.java http://jenkins-ci.org/commit/jenkins/e31b750c58407df9f819bbe6ac8c87d62e100e64 Log: Merge pull request #767 from olivergondza/wbr_layout FIXED JENKINS-17030 Enable word breaking for job names. Compare: https://github.com/jenkinsci/jenkins/compare/c3ee6220ee20...e31b750c5840 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cppcheck] (JENKINS-18029) In CppCheck plugin selected line with static analysis violation is hidden because breadcrumb covers it
Jan Magur updated JENKINS-18029 In CppCheck plugin selected line with static analysis violation is hidden because breadcrumb covers it Change By: Jan Magur (21/May/13 6:14 PM) Summary: InCppCheckplugin desired selected linewithstaticanalysisviolationishiddenbecausebreadcrumbcoversit Priority: Major Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cppcheck] (JENKINS-18029) In CppCheck plugin selected line with static analysis violation is hidden because breadcrumb covers it
Jan Magur commented on JENKINS-18029 In CppCheck plugin selected line with static analysis violation is hidden because breadcrumb covers it Did you check attached screenshots and their names? 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-17910) groovy.lang.MissingMethodException in sidepanel.jelly
Geoff Cummings commented on JENKINS-17910 groovy.lang.MissingMethodException in sidepanel.jelly Still got an error. Status Code: 500 Exception: org.apache.commons.jelly.JellyTagException: jar:file:/tr/j/jh/war/WEB-INF/lib/jenkins-core-1.515.jar!/hudson/PluginManager/table.jelly:49:41: st:include No signature of method: java.lang.String.header() is applicable for argument types: () values: [] Possible solutions: center(java.lang.Number), center(java.lang.Number), center(java.lang.Number, java.lang.String), center(java.lang.Number, java.lang.CharSequence), every(), every(groovy.lang.Closure) Stacktrace: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/tr/j/jh/war/WEB-INF/lib/jenkins-core-1.515.jar!/hudson/PluginManager/table.jelly:49:41: st:include No signature of method: java.lang.String.header() is applicable for argument types: () values: [] Possible solutions: center(java.lang.Number), center(java.lang.Number), center(java.lang.Number, java.lang.String), center(java.lang.Number, java.lang.CharSequence), every(), every(groovy.lang.Closure) at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:666) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$3.doDispatch(MetaClass.java:175) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) Exception: org.apache.commons.jelly.JellyTagException: jar:file:/tr/j/jh/war/WEB-INF/lib/jenkins-core-1.515.jar!/lib/form/descriptorList.jelly:84:76: st:include No signature of method: java.lang.String.optionalBlock() is applicable for argument types: (java.util.LinkedHashMap) values: [[name:svnmerge_integratable, title:Accept Integration from Subversion feature branches, ...]] Stacktrace: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/tr/j/jh/war/WEB-INF/lib/jenkins-core-1.515.jar!/lib/form/descriptorList.jelly:84:76: st:include No signature of method: java.lang.String.optionalBlock() is applicable for argument types: (java.util.LinkedHashMap) values: [[name:svnmerge_integratable, title:Accept Integration from Subversion feature branches, ...]] at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) Jenkins Email Extension Plugin This plugin is a replacement for Jenkins's email publisher 2.29.1 Downgrade to 2.28 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cppcheck] (JENKINS-18029) In CppCheck plugin selected line with static analysis violation is hidden because breadcrumb covers it
Jan Magur edited a comment on JENKINS-18029 In CppCheck plugin selected line with static analysis violation is hidden because breadcrumb covers it Did you check attached screenshots and their names? Breadcrumb is new navigation menu on top of page. 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-17910) groovy.lang.MissingMethodException in sidepanel.jelly
Geoff Cummings commented on JENKINS-17910 groovy.lang.MissingMethodException in sidepanel.jelly I'm wondering why its always java.lang.String. java.lang.String.header() java.lang.String.optionalBlock() java.lang.String.queue() java.lang.String.entry() 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] [junit] (JENKINS-17478) Add extension point to rewrite test names
SCM/JIRA link daemon commented on JENKINS-17478 Add extension point to rewrite test names Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/tasks/junit/CaseResult.java core/src/main/java/hudson/tasks/junit/ClassResult.java test/src/test/java/hudson/tasks/junit/TestNameTransformerTest.java http://jenkins-ci.org/commit/jenkins/6ea4532da3348453c8ebadee5bb3a2fa2d9897e6 Log: Merge pull request #774 from dnadolny/master JENKINS-17478 Various improvements from code reviews Compare: https://github.com/jenkinsci/jenkins/compare/b5d96e27dd8c...6ea4532da334 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-17910) groovy.lang.MissingMethodException in sidepanel.jelly
Alex Earl commented on JENKINS-17910 groovy.lang.MissingMethodException in sidepanel.jelly optionalBlock and entry aren't even part of java.lang.String, they are taglib items from Jenkins. This is going to take someone more versed in Java than I am to understand. I am more than willing to try stuff in the email-ext plugin to help the debug though. 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] [clone-workspace-scm] (JENKINS-18031) Clone Workspace SCM uses display name of Jenkins job to attempt to locate workspace of clone
Mike Long created JENKINS-18031 Clone Workspace SCM uses display name of Jenkins job to attempt to locate workspace of clone Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: clone-workspace-scm Created: 21/May/13 6:35 PM Description: It looks like the "Clone Workspace SCM" plugin is using the display name of the Jenkins job that produces a workspace clone to attempt to locate the workspace that was cloned. This is fine if a display name has not been specified in the "Advanced Project Options" of the job that produces the clone to be restored, but if a display name has been specified then the job configured to use the cloned work space attempts to retrieve the clone from a non-existent directory named for the display name of the job that produced the clone. Project: Jenkins Priority: Minor Reporter: Mike Long 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-17681) LastSuccessful and LastStable symlinks are invalid under Windows
jmmckinnon commented on JENKINS-17681 LastSuccessful and LastStable symlinks are invalid under Windows 1 on LTS 1.509.2. I upgraded from 1.466.1 LTS to 1.509.1 and unfortunately could not roll back. I see 10,000 lines of exceptions in my log on startup (and frequently). It could be masking other issues... In the meantime I will run my master with Admin privileges as a 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 -- 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-17681) LastSuccessful and LastStable symlinks are invalid under Windows
jmmckinnon edited a comment on JENKINS-17681 LastSuccessful and LastStable symlinks are invalid under Windows Another 1 on LTS 1.509.2. I upgraded from 1.466.1 LTS to 1.509.1 and unfortunately could not roll back. I see 10,000 lines of exceptions in my log on startup (and frequently). It could be masking other issues... In the meantime I will run my master with Admin privileges as a 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 -- 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] [testflight] (JENKINS-17592) Testflight uploader plugin doesn't allow to upload multiple files
SCM/JIRA link daemon commented on JENKINS-17592 Testflight uploader plugin doesnt allow to upload multiple files Code changed in jenkins User: Jerome Lacoste Path: pom.xml src/main/java/testflight/TestflightRecorder.java src/main/java/testflight/TestflightRemoteRecorder.java src/main/java/testflight/TestflightUploader.java src/test/java/testflight/TestflightRemoteRecorderTest.java http://jenkins-ci.org/commit/testflight-plugin/289c25c05b4bcc130d5b45da4d9b032b40c04d51 Log: JENKINS-17592 support wildcards for ipa and apks 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] [testflight] (JENKINS-17592) Testflight uploader plugin doesn't allow to upload multiple files
lacostej resolved JENKINS-17592 as Fixed Testflight uploader plugin doesnt allow to upload multiple files Merged with master. This will make it into 1.3.7. Please test and report any issues! Change By: lacostej (21/May/13 7:53 PM) Status: Open Resolved Assignee: lacostej 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-17030) Display long job names without breaking Jenkins layout
dogfood commented on JENKINS-17030 Display long job names without breaking Jenkins layout Integrated in jenkins_main_trunk #2531 FIXED JENKINS-17030 Enable word breaking for job names (Revision 2c240bdc876e74fe7a4a1ebeb5e3707e2d8f7bf3) JENKINS-17030 Noting, fixing/adding @since, adding @Bug. (Revision b5d96e27dd8c0aa5f5c50aa2260f3369d1d758a4) Result = UNSTABLE ogondza : 2c240bdc876e74fe7a4a1ebeb5e3707e2d8f7bf3 Files : core/src/main/resources/lib/hudson/buildListTable.jelly core/src/main/resources/lib/hudson/executors.jelly core/src/main/resources/hudson/model/Job/index.jelly core/src/main/resources/lib/hudson/jobLink.jelly core/src/main/java/hudson/Functions.java core/src/main/resources/lib/layout/breakable.jelly core/src/main/resources/hudson/matrix/MatrixProject/index.jelly core/src/test/java/hudson/FunctionsTest.java core/src/main/resources/lib/hudson/queue.jelly core/src/main/resources/hudson/views/JobColumn/column.jelly Jesse Glick : b5d96e27dd8c0aa5f5c50aa2260f3369d1d758a4 Files : core/src/main/resources/lib/layout/breakable.jelly core/src/test/java/hudson/FunctionsTest.java changelog.html core/src/main/java/hudson/Functions.java 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-17910) groovy.lang.MissingMethodException in sidepanel.jelly
Geoff Cummings commented on JENKINS-17910 groovy.lang.MissingMethodException in sidepanel.jelly I'm new to groovy, so this is a guess, but is it possible that the MethodMissingHandler in ScriptContent.Java is impacting other groovy code? https://github.com/jenkinsci/email-ext-plugin/blob/4a6c1446ff95591a511cec527f2e5702c07a0c6d/src/main/java/hudson/plugins/emailext/plugins/content/ScriptContent.java GroovyShell shell = createEngine(Collections.singletonMap("methodMissing", (Object)InvokerHelper.getMethodPointer(handler, "methodMissing"))); shell.evaluate("Script.metaClass.methodMissing = methodMissing"); the exceptions are due to missingMethodExceptions seems to happen after groovyTemplate email is sent which would execute this code GroovyShell is created with the uberclassloader, would this cause metaClass changes to Script to remain and impact other functionality... 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-17910) groovy.lang.MissingMethodException in sidepanel.jelly
Alex Earl commented on JENKINS-17910 groovy.lang.MissingMethodException in sidepanel.jelly I was wondering the same thing, I didn't think that should be the case. I thought the shell would its own self-contained 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 -- 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] [gui] (JENKINS-18032) Delete Project link fails with 403 Exception: No valid crumb was included in the request
John Genoese created JENKINS-18032 Delete Project link fails with 403 Exception: No valid crumb was included in the request Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: gui Created: 21/May/13 8:36 PM Description: Unable to delete any project. Environment: Mac OS X 10.7.5 Project: Jenkins Priority: Major Reporter: John Genoese 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] [gui] (JENKINS-18033) Module Links produce Status Code 404 when clicked
John Genoese created JENKINS-18033 Module Links produce Status Code 404 when clicked Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: gui Created: 21/May/13 8:40 PM Description: In a multi-module Maven project, individual modules are appropriately displayed when the "Modules" link is clicked. However, when an individual module link is clicked, Jenkins returns a 404 response with no stacktrace. Environment: Mac OS X 10.7.5 Project: Jenkins Priority: Major Reporter: John Genoese 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] [gui] (JENKINS-18033) Module Links produce Status Code 404 when clicked
John Genoese updated JENKINS-18033 Module Links produce Status Code 404 when clicked Attachment "18033-1.png" depicts a multi-module display. Attachment "18033-2.png" depicts the 404. Change By: John Genoese (21/May/13 8:49 PM) Attachment: 18033-1.png Attachment: 18033-2.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/groups/opt_out.
[JIRA] [core] (JENKINS-17412) Multiple maven builds: Jenkins frequently dies
Jesse Glick resolved JENKINS-17412 as Incomplete Multiple maven builds: Jenkins frequently dies The thread dump does show one thread loading fingerprints, but that is not enough to go on. Change By: Jesse Glick (21/May/13 8:53 PM) Status: Open Resolved Resolution: Incomplete 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] [gui] (JENKINS-18032) Delete Project link fails with 403 Exception: No valid crumb was included in the request
John Genoese updated JENKINS-18032 Delete Project link fails with 403 Exception: No valid crumb was included in the request Attachment "18032-1.png" depicts a Jenkins dashboard. Attachment "18032-2.png" depicts the 403 response to the "Delete Project" click. Change By: John Genoese (21/May/13 8:52 PM) Attachment: 18032-1.png Attachment: 18032-2.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/groups/opt_out.