[JIRA] (JENKINS-14017) main-page can't show picture/icon before login
Andreas Sandberg updated JENKINS-14017 main-page cant show picture/icon before login Change By: Andreas Sandberg (03/Jul/12 6:24 AM) Attachment: FullStacktrace.txt Environment: jenkins:1.464OS:LINux Alternativeenvironment:Jenkins1.473UsingActiveDirectorypluginforauthentication.OS:WindowsServer2008 Description: Beforeuserlogin,thepicutureofwebshowsXasattachment .EasiestwaytoreproduceistosetupsecurityinJenkins(currentversion)andpressCTRL+F5(fullreload)inthewebbrowser(beforeloggingin).Ivealsofoundthisstacktraceinthejenkins.err.logfilewhichseemstoberelatedtotheimages.Pleaseseeattachementforfullstacktrace:2012-jul-0308:17:13winstone.LoggerlogInternalVARNING:UntrappedErrorinServletjava.lang.NullPointerException athudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:50) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14017) main-page can't show picture/icon before login
Andreas Sandberg commented on JENKINS-14017 main-page cant show picture/icon before login I've just realized that this bug is not related to Jenkins (core) but is related to the GreenBalls plugin (didnt realize that when I edited the issue). The good news is that this issue is already solved in the GreenBalls plugin (version 1.12). So in order to fix this, update your greenballs plugin to the current version. See release notes: https://wiki.jenkins-ci.org/display/JENKINS/Green+Balls This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14017) main-page can't show picture/icon before login
Andreas Sandberg closed JENKINS-14017 as Not A Defect main-page cant show picture/icon before login Fixed in the Greenballs plugin (version 1.12). https://wiki.jenkins-ci.org/display/JENKINS/Green+Balls Change By: Andreas Sandberg (03/Jul/12 6:46 AM) Status: Open Closed Fix Version/s: current 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
[JIRA] (JENKINS-11853) Duplicate build numbers in the Build History
Maximilian Kernbach commented on JENKINS-11853 Duplicate build numbers in the Build History Still occurs in Jenkins v1.472. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11853) Duplicate build numbers in the Build History
Maximilian Kernbach updated JENKINS-11853 Duplicate build numbers in the Build History Current Build-Numbers : Server: # 51 Gerrit DevTest Build #793 Project "Nightly DevTest Build" is DEACTIVATED, but also showing up on build history! Change By: Maximilian Kernbach (03/Jul/12 8:33 AM) Attachment: BrokenBuildHistory.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11853) Duplicate build numbers in the Build History
Maximilian Kernbach edited a comment on JENKINS-11853 Duplicate build numbers in the Build History (Comment to Attachment Broken Build History.jpg) Current Build-Numbers : Server: # 51 Gerrit DevTest Build #793 Project "Nightly DevTest Build" is DEACTIVATED, but also showing up on build history! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11853) Duplicate build numbers in the Build History
Maximilian Kernbach edited a comment on JENKINS-11853 Duplicate build numbers in the Build History Still occurs in Jenkins v1.472. So.. as I asked three months ago.. What information are needed that we can fix this annoying bug? Jenkins is currently not usable for me. (I'm only using 3 "broken" projects instead of 20-25 as I want to) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14247) Master Executor Needed for SCM polling even with slaves
Steve Eckerlein commented on JENKINS-14247 Master Executor Needed for SCM polling even with slaves If i define a system environment variable PATH with cleartool the problem is resolved. Tested on a test platform. But on my production network, i have no rights. I can't extend PATH and i face this problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14289) Multi-configuration project chooses wrong slave to build the project
Chen Lu created JENKINS-14289 Multi-configuration project chooses wrong slave to build the project Issue Type: Bug Affects Versions: current Assignee: rsandell Attachments: jenkins-1.png, jenkins-2.png Components: multi-slave-config Created: 03/Jul/12 9:05 AM Description: In a multi-configuration project, I specified the slaves by choosing labels or individual nodes in added axis Slaves. But it will choose wrong slave to build the project. Project: Jenkins Labels: jenkins Priority: Critical Reporter: Chen Lu This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14289) Multi-configuration project chooses wrong slave to build the project
Chen Lu commented on JENKINS-14289 Multi-configuration project chooses wrong slave to build the project The version of Jenkins we're using is Jenkins ver. 1.458. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14289) Multi-configuration project chooses wrong slave to build the project
rsandell updated JENKINS-14289 Multi-configuration project chooses wrong slave to build the project wrong component Change By: rsandell (03/Jul/12 9:08 AM) Component/s: core Component/s: multi-slave-config This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14289) Multi-configuration project chooses wrong slave to build the project
rsandell assigned JENKINS-14289 to Unassigned Multi-configuration project chooses wrong slave to build the project Change By: rsandell (03/Jul/12 9:09 AM) Assignee: rsandell This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14290) Support for Ivy project type
Balazs Jagri created JENKINS-14290 Support for Ivy project type Issue Type: Improvement Affects Versions: current Assignee: Gregory Boissinot Components: envinject Created: 03/Jul/12 9:14 AM Description: EnvInject functionality shall be available for Ivy projects similarly to Maven ones. Project: Jenkins Priority: Minor Reporter: Balazs Jagri This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14289) Multi-configuration project chooses wrong slave to build the project
Chen Lu resolved JENKINS-14289 as Not A Defect Multi-configuration project chooses wrong slave to build the project I think all I need is this https://wiki.jenkins-ci.org/display/JENKINS/Matrix+Tie+Parent+Plugin Change By: Chen Lu (03/Jul/12 9:25 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
[JIRA] (JENKINS-14291) Unavailable violations per file view for jslint
Arkadiusz Kawka created JENKINS-14291 Unavailable violations per file view for jslint Issue Type: Bug Affects Versions: current Assignee: peterkittreilly Components: violations Created: 03/Jul/12 9:48 AM Description: The per file view is unavailable for JSLint reports The problem was also discussed on https://groups.google.com/forum/#!topic/jenkinsci-users/cUfZimHHXqs If I follow to the per file view I get empty page. Environment: OS: Windows 7 Jenkins: v. 1.468 Violations plugin: v. 0.7.10 Project: Jenkins Priority: Major Reporter: Arkadiusz Kawka This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14097) Allow Script Path/Content to add/override environment variables for the build job
David Ehrenberger commented on JENKINS-14097 Allow Script Path/Content to add/override environment variables for the build job Behind the scenes it doesn't really matter to me how the environment variables are injected. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10821) Points are not awarded for new tests in Ruby
Matthias Viehweger commented on JENKINS-10821 Points are not awarded for new tests in Ruby I use the gem "ci_reporter" to give Jenkins the necessary information. cucumber comes with support for the necessary xml-output built-in. Test::Unit and RSpec need the "ci_reporter" gem installed. Both points in the CI-Game and a trending graph work fine on out Jenkins with that. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13916) Multiline text parameter displays as single line
Rafa de la Torre commented on JENKINS-13916 Multiline text parameter displays as single line I made a pull request to the upstream jenkins core that fixes this issue: https://github.com/rafatower/jenkins/commit/3ee724f9b1909565e74a6951443f38053175282a Regards This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13916) Multiline text parameter displays as single line
Rafa de la Torre edited a comment on JENKINS-13916 Multiline text parameter displays as single line I made a pull request to the upstream jenkins core that fixes this issue: https://github.com/jenkinsci/jenkins/pull/513 Regards This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14292) warnings-plugin chooses wrong reference build, counts too many new warnings
torbent created JENKINS-14292 warnings-plugin chooses wrong reference build, counts too many new warnings Issue Type: Bug Assignee: Ulli Hafner Components: warnings Created: 03/Jul/12 1:07 PM Description: I think this started when I upgraded the warnings-plugin to 4.6. Some of our people want to fail builds when they get new warnings, so have thresholds set for that. The plugin is then supposed to compare the number of warnings to the last successful build. After upgrade to 4.6 it has instead chosen to compare to the last build before the upgrade, as if it doesn't recognise the newer builds. A difference between before and now is also that we now have multiple graphs (not a problem, but maybe a contributing reason). We mostly have jobs with multiple parsers, sometimes using a custom parser. Of the embedded parsers we use the "GNU Compiler" and "MSBuild" parsers. I have seen other "funny" cases where build #N had 246 warnings and build #N+1 had 247, yet there were no new warnings according to the plugin. That job has 2 parsers working on 2 files each. Let me know if you need to know more about our setup or the jobs? Project: Jenkins Priority: Major Reporter: torbent This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14293) Error in ChangeLog if some of the changed files are locked
Gianvittorio Mauri created JENKINS-14293 Error in ChangeLog if some of the changed files are locked Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: cvs Created: 03/Jul/12 1:20 PM Description: While calling "cvs rlog", if some of the changed files are locked, the following error occurs : ... cvs rlog -S -d03 Jul 2012 10:50:26 +020003 Jul 2012 10:58:16 +0200 MI ... cvs rlog: Logging MI/MI/librtpr/rtbiglib cvs rlog: Logging MI/MI/librtpr/src cvs rlog: Logging MI/MI/librtpr/test cvs rlog: Logging MI/MI/librtpr/test/include cvs rlog: Logging MI/MI/old_libeqpr cvs rlog: Logging MI/MI/old_libeqpr/src FATAL: For input string: "3 locked by: mauri;" java.lang.NumberFormatException: For input string: "3 locked by: mauri;" at java.lang.NumberFormatException.forInputString(Unknown Source) at java.lang.Integer.parseInt(Unknown Source) at java.lang.Integer.parseInt(Unknown Source) at hudson.scm.CvsChangeLogHelper.isChangeValidForFileVersion(CvsChangeLogHelper.java:260) at hudson.scm.CvsChangeLogHelper.mapCvsLog(CvsChangeLogHelper.java:200) at hudson.scm.CVSSCM.calculateChangeLog(CVSSCM.java:419) at hudson.scm.CVSSCM.checkout(CVSSCM.java:831) at hudson.model.AbstractProject.checkout(AbstractProject.java:1248) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:589) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:494) at hudson.model.Run.execute(Run.java:1484) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236 Following is the "cvs rlog" command line output: cvs -Q rlog -S -d"03 Jul 2012 10:50:26 +020003 Jul 2012 10:58:16 +0200" MI RCS file: /home_new/mauri/jenkins/testrepo/MI/MI/librtpr/Makefile,v head: 1.3 branch: locks: strict mauri: 1.3 access list: symbolic names: ACME: 1.1.1.1 first-import: 1.1.1 keyword substitution: kv total revisions: 4; selected revisions: 1 description: revision 1.3locked by: mauri; date: 2012-07-03 10:54:50 +0200; author: mauri; state: Exp; lines: +0 -1; commitid: YV4vP97yquVGX5bw; bbb = It seems the plugin was not able to parse away the substring "locked by: mauri" from the revision line. Environment: cvs server version 1.12.13 Project: Jenkins Labels: plugin Priority: Major Reporter: Gianvittorio Mauri This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14294) Action List is empty when adding Post-Build Action
Walter Kacynski created JENKINS-14294 Action List is empty when adding Post-Build Action Issue Type: Bug Assignee: bap Attachments: AfterSave.png, BeforeSave.png Components: flexible-publish Created: 03/Jul/12 1:29 PM Description: When Flexible Publish is first added as a post-build action, the list of actions is empty and a NullPointer is thrown in the Master err.log After I go back into the project configuration the action list has been populated and things are fine. Project: Jenkins Labels: plugin Priority: Major Reporter: Walter Kacynski This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13114) dropdown views taskbar: error when saving jenkins config page
Chris Withers commented on JENKINS-13114 dropdown views taskbar: error when saving jenkins config page I'd prefer not to use snapshots. When is 1.6 going to be released? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14183) Nexus 502 error during builds
Steven Schoeffler reopened JENKINS-14183 Nexus 502 error during builds still having problems with this. I would request help verifying my Jenkins http_proxy settings are correct and how to do this. I see that there is a Tab in Plugin Manager that lets you set an http proxy, but is there a field for a no_proxy_host list for excluded local servers? Change By: Steven Schoeffler (03/Jul/12 1:58 PM) Resolution: Fixed Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13114) dropdown views taskbar: error when saving jenkins config page
jieryn commented on JENKINS-13114 dropdown views taskbar: error when saving jenkins config page I'd prefer not to make a release that is untested by the people that report the problem... I will let it bake for a while unless I get some affirmation that the fix is good. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14291) Unavailable violations per file view for jslint
Arkadiusz Kawka updated JENKINS-14291 Unavailable violations per file view for jslint Change By: Arkadiusz Kawka (03/Jul/12 2:07 PM) Attachment: jslint.xml Description: TheperfileviewisunavailableforJSLintreportsTheproblemwasalsodiscussedonhttps://groups.google.com/forum/#!topic/jenkinsci-users/cUfZimHHXqsIfIfollowtotheperfileviewIgetemptypage. Ivealsoattachedsampleoutputxmlfile This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13114) dropdown views taskbar: error when saving jenkins config page
Chris Withers commented on JENKINS-13114 dropdown views taskbar: error when saving jenkins config page Okay, how do I install the snapshot? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-6724) Allow user to select/choose all svn repositories
Slide-O-Mix resolved JENKINS-6724 as Not A Defect Allow user to select/choose all svn repositories This is not a bug, there are multiple ways to use whatever environment variable you have setup. Please check the wiki. Change By: Slide-O-Mix (03/Jul/12 2:09 PM) 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
[JIRA] (JENKINS-13114) dropdown views taskbar: error when saving jenkins config page
Billy Foss commented on JENKINS-13114 dropdown views taskbar: error when saving jenkins config page I have seen the problem as well and will test the snapshot plugin. 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
[JIRA] (JENKINS-13114) dropdown views taskbar: error when saving jenkins config page
jieryn commented on JENKINS-13114 dropdown views taskbar: error when saving jenkins config page Download the .hpi file from the build system, link above, then go into Manage Jenkins Manage Plugins Advanced ( or $JENKINS/pluginManager/advanced ) and use the Choose File and Upload buttons to manually update the 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
[JIRA] (JENKINS-13114) dropdown views taskbar: error when saving jenkins config page
Billy Foss
commented on JENKINS-13114
dropdown views taskbar: error when saving jenkins config page
With the snapshot installed on 1.472 running on Fedora, I get the following when trying to save the Configuration page.
Exception: java.lang.IllegalArgumentException: Failed to instantiate class hudson.views.ViewsTabBar from {"stapler-class":"hudson.views.tabbar.DropDownViewsTabBar"}
Stacktrace:
javax.servlet.ServletException: java.lang.IllegalArgumentException: Failed to instantiate class hudson.views.ViewsTabBar from {"stapler-class":"hudson.views.tabbar.DropDownViewsTabBar"}
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:616)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488)
at org.kohsuke.stapler.Stapler.service(Stapler.java:162)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)
at winstone.ServletConfiguration.execute(ServletConfiguration.java:248)
at winstone.RequestDispatcher.forward(RequestDispatcher.java:333)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at winstone.RequestDispatcher.forward(RequestDispatcher.java:331)
at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:215)
at winstone.RequestHandlerThread.run(RequestHandlerThread.java:138)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
Caused by: java.lang.IllegalArgumentException: Failed to instantiate class hudson.views.ViewsTabBar from {"stapler-class":"hudson.views.tabbar.DropDownViewsTabBar"}
at org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:633)
at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:377)
at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:373)
at hudson.views.ViewsTabBar$GlobalConfigurationImpl.configure(ViewsTabBar.java:84)
at jenkins.model.Jenkins.configureDescriptor(Jenkins.java:2686)
at jenkins.model.Jenkins.doConfigSubmit(Jenkins.java:2649)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151)
at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90)
at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574)
... 35 more
Caused by:
[JIRA] (JENKINS-13114) dropdown views taskbar: error when saving jenkins config page
Billy Foss commented on JENKINS-13114 dropdown views taskbar: error when saving jenkins config page Further information With the plugin installed and 'Default Views TabBar' selected, I can save the configuration With the plugin installed and 'DropDownViewsViewsTabBar' selected, I get the Error 500 message and the exception above. When I save the configuration and it fails with the 500 error, I lose any JDKs configured in the system. I can add them back in, but it is a pain to lose configuration. (fortunately I have hit this enough that I have a test instance of Jenkins to verify with) Thanks, Billy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13114) dropdown views taskbar: error when saving jenkins config page
Chris Withers commented on JENKINS-13114 dropdown views taskbar: error when saving jenkins config page Same here running in 1.472 on Mac OS X. Guess it was worth having people test those snapshots This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11548) Heavy Job plugin not working with Matrix jobs
Juri Timošin commented on JENKINS-11548 Heavy Job plugin not working with Matrix jobs Hello. Could you share the patch somehow? That would be very kind of you. We would like to start using this plugin with matrix jobs. Or may you can create a pull request in github? Thanks in advance. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13114) dropdown views taskbar: error when saving jenkins config page
jieryn commented on JENKINS-13114 dropdown views taskbar: error when saving jenkins config page I only tested against 1.455, where I used to be able to reproduce the error and now can not... I didn't test with 1.472, and this defect is filed against 1.455. I'm sure everyone is frustrated by this, I certainly am. I'm at a loss for what to do, it seems I will have to make a 1.6 release for 1.455 and then 1.7 for 1.472 ... can anyone seeing the original problem verify it is fixed for 1.455? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14297) Slave Monitor for system load average do not work on IBM AIX OS
erwan_q created JENKINS-14297 Slave Monitor for system load average do not work on IBM AIX OS Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: monitoring Created: 03/Jul/12 3:20 PM Description: Install "Slave Monitor for system load average" plugin. https://wiki.jenkins-ci.org/display/JENKINS/System+Load+Average+Monitor+Plugin This plugin do not work for IBM AIX slaves. Sorry I do not found existing jenkins bug. Could be duplicate. WARNING: Failed to monitor k35aix01 for System Load Average java.io.IOException: Remote call on k35aix01 failed at hudson.remoting.Channel.call(Channel.java:672) at hudson.plugins.systemloadaverage_monitor.SystemLoadAverageMonitor$1.monitor(SystemLoadAverageMonitor.java:47) at hudson.plugins.systemloadaverage_monitor.SystemLoadAverageMonitor$1.monitor(SystemLoadAverageMonitor.java:42) at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:202) Caused by: java.lang.NoSuchMethodError: java/lang/management/OperatingSystemMXBean.getSystemLoadAverage()D at hudson.plugins.systemloadaverage_monitor.SystemLoadAverageMonitor$MonitorTask.call(SystemLoadAverageMonitor.java:73) at hudson.plugins.systemloadaverage_monitor.SystemLoadAverageMonitor$MonitorTask.call(SystemLoadAverageMonitor.java:64) 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:284) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690) at java.lang.Thread.run(Thread.java:810) Jul 3, 2012 1:26:43 AM hudson.node_monitors.AbstractNodeMonitorDescriptor$Record run Environment: IBM AIX Version 5.3 Jenkins ver. 1.472 Slave Monitor for system load average plugin 1.2 Project: Jenkins Priority: Minor Reporter: erwan_q This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14288) thinBackup doesn't put back the current shutdown flag after backing up
Thomas Fürer commented on JENKINS-14288 thinBackup doesnt put back the current shutdown flag after backing up please try also the newer version 1.6.1 where I did some bug fixing about this topic. Please be aware that once you have chosen a value greater than zero for 'Force Jenkins to quite mode after specified minutes' jenkins will be forced to quiet mode until the backup is finished (compare https://wiki.jenkins-ci.org/display/JENKINS/thinBackup). Be also aware that the quiet mode in case of an triggered backup is not cancleable, for now. please also check if the backup do not have some problems like missing permissions or slow network connection with shared folders. 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
[JIRA] (JENKINS-14298) Login unsuccessful authentication stack trace
erwan_q created JENKINS-14298 Login unsuccessful authentication stack trace Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: security Created: 03/Jul/12 3:48 PM Description: When a user try an unsuccessful authentication, I have an INFO stack trace in the jenkins log file Is it necessary to have this information in the jenkins log file? This increase the jenkins log file and I try to scan an check this file to detect jenkin critical errors. Jul 3, 2012 3:08:35 PM hudson.security.AuthenticationProcessingFilter2 onUnsuccessfulAuthentication INFO: Login attempt failed org.acegisecurity.BadCredentialsException: Failed to login as USER_A at hudson.security.HudsonPrivateSecurityRealm.authenticate(HudsonPrivateSecurityRealm.java:173) at hudson.security.HudsonPrivateSecurityRealm.authenticate(HudsonPrivateSecurityRealm.java:89) at hudson.security.AbstractPasswordBasedSecurityRealm$Authenticator.retrieveUser(AbstractPasswordBasedSecurityRealm.java:137) at org.acegisecurity.providers.dao.AbstractUserDetailsAuthenticationProvider.authenticate(AbstractUserDetailsAuthenticationProvider.java:119) at org.acegisecurity.providers.ProviderManager.doAuthentication(ProviderManager.java:195) at org.acegisecurity.AbstractAuthenticationManager.authenticate(AbstractAuthenticationManager.java:45) at org.acegisecurity.ui.webapp.AuthenticationProcessingFilter.attemptAuthentication(AuthenticationProcessingFilter.java:71) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:252) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:63) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:215) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:138) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Environment:
[JIRA] (JENKINS-13893) email-ext crashes when job log contains left or right simple-quote ''
Slide-O-Mix resolved JENKINS-13893 as Cannot Reproduce email-ext crashes when job log contains left or right simple-quote I have tried various things to reproduce this and have not been able to. Change By: Slide-O-Mix (03/Jul/12 3:49 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14183) Nexus 502 error during builds
Steven Schoeffler updated JENKINS-14183 Nexus 502 error during builds Change By: Steven Schoeffler (03/Jul/12 4:34 PM) Status: Reopened Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14183) Nexus 502 error during builds
Steven Schoeffler closed JENKINS-14183 as Fixed Nexus 502 error during builds Change By: Steven Schoeffler (03/Jul/12 4:34 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14183) Nexus 502 error during builds
Steven Schoeffler resolved JENKINS-14183 as Fixed Nexus 502 error during builds the problem is fixed. I added some MAVEN_OPTS variables that listed my proxy server and the build completed. Change By: Steven Schoeffler (03/Jul/12 4:34 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14210) EMAIL-EXT - FILE token doesn't allow NESTED contents.
Arun Sangal
commented on JENKINS-14210
EMAIL-EXT - FILE token doesnt allow NESTED contents.
Thanks a lot Slide. You're great.
Now, similar to this same request.
In the Editable email notification (Email-ext plugin), we have Subject, Recepients etc fields.
What I was wondering is if I can defined those in all of my Jenkins jobs as one variable like: $RECEPIENTS, $SUBJECT etc. Now, what I'll do is, I'll set these variables from a file that I'll use as a environment variable property file. i.e.
If I give C:\giga\email.config.jobname.instancename.txt as the environment file withing Jenkins JOB, then, inside this file, I'll set the variables for EMAIL variables like:
RECEPIENTS=a...@xyz.com, g...@fifa.com
SUBJECT=$INSTANCE_NAME Build $BUILD_STATUS: $PROJECT_NAME # $BUILD_NUMBER
or
SUBJECT=$INSTANCE_NAME Build $BUILD_STATUS: $PROJECT_NAME # ${ENV,var="build.label"}
NOW, seems like when I tried using this behaviour, I found that an environment variable IF containing another variable are NOT EXPANDING as well. Is there any way, we can achieve this too.
Now, your question towards me would be:
1. Why dont I use the above variables in the Jenkins job directly and remain silent / happy ???
Actually to answer it: I see the following conclusions:
1. As I have many Jenkins job, I want all the jobs to reflect MINIMAL configuration at the Jenkins setting i.e. if Email Ext "SUBJECT" box contains: $SUBJECT
only, then, it'll lot easier for the new user to understand and learn.
2. All the jobs will be SAME as far as EMAIL-EXT (Editable email notification) section is concerned. SAME in the sense of using the environment variables.
3. Definition of these environment variables DONT have to be defined at the Jenkins job level as we will create a config file and define the variables there and just use one variable name per box (for each Editable email notification fields/boxes).
4. If someday we need to change the subject,
FROM:
SUBJECT=$INSTANCE_NAME Build $BUILD_STATUS: $PROJECT_NAME # $BUILD_NUMBER
-to-
SUBJECT=$INSTANCE_NAME Build $BUILD_STATUS: $PROJECT_NAME # ${ENV,var="build.label"}
or -to-
SUBJECT=Jenkins Build $BUILD_STATUS: $PROJECT_NAME # ${ENV,var="version.label"}
I dont have to go in Jenkins job configuration and change it there. I'll just change my config file and there you'll see the change in the email notification as Jenkins job's EMAIL SUBJECT box is stil containing $SUBJECT variable which's defined in our config file.
5. BASICALLY, what we need in the above request is...
similarly like you allowed nested contents in the JELLY script (EMAIL CONTENT area),
can we have the same "nested" capability in other parts of the JENKINS jobs where we specify some variables (it can be Email's fields/boxes, or it can be any field/box in Jenkins job's whole configuraiton).
What we want to achieve here is (3 feet view):
if X=$Y and if Y=${VAR}-I_like_it and VAR=FIFA.
Then X should result as:
"FIFA-I_like_it"
Apart from that, when can we expect the nested funcationality of Jelly to be included in the next version of Jenkins build .war? Kindly advise.
Thanks.
Regards
Arun Sangal
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14210) EMAIL-EXT - FILE token doesn't allow NESTED contents.
Arun Sangal
edited a comment on JENKINS-14210
EMAIL-EXT - FILE token doesnt allow NESTED contents.
Thanks a lot Slide.
Now, similar to this same request. I opened a new request to get similar funcationality.
PS (LINK): https://issues.jenkins-ci.org/browse/JENKINS-14299
In the Editable email notification (Email-ext plugin), we have Subject, Recepients etc fields.
What I was wondering is if I can defined those in all of my Jenkins jobs as one variable like: $RECEPIENTS, $SUBJECT etc. Now, what I'll do is, I'll set these variables from a file that I'll use as a environment variable property file. i.e.
If I give C:\giga\email.config.jobname.instancename.txt as the environment file withing Jenkins JOB, then, inside this file, I'll set the variables for EMAIL variables like:
RECEPIENTS=a...@xyz.com, g...@fifa.com
SUBJECT=$INSTANCE_NAME Build $BUILD_STATUS: $PROJECT_NAME # $BUILD_NUMBER
or
SUBJECT=$INSTANCE_NAME Build $BUILD_STATUS: $PROJECT_NAME # ${ENV,var="build.label"}
NOW, seems like when I tried using this behaviour, I found that an environment variable IF containing another variable are NOT EXPANDING as well. Is there any way, we can achieve this too.
Now, your question towards me would be:
1. Why dont I use the above variables in the Jenkins job directly and remain silent / happy ???
Actually to answer it: I see the following conclusions:
1. As I have many Jenkins job, I want all the jobs to reflect MINIMAL configuration at the Jenkins setting i.e. if Email Ext "SUBJECT" box contains: $SUBJECT
only, then, it'll lot easier for the new user to understand and learn.
2. All the jobs will be SAME as far as EMAIL-EXT (Editable email notification) section is concerned. SAME in the sense of using the environment variables.
3. Definition of these environment variables DONT have to be defined at the Jenkins job level as we will create a config file and define the variables there and just use one variable name per box (for each Editable email notification fields/boxes).
4. If someday we need to change the subject,
FROM:
SUBJECT=$INSTANCE_NAME Build $BUILD_STATUS: $PROJECT_NAME # $BUILD_NUMBER
-to-
SUBJECT=$INSTANCE_NAME Build $BUILD_STATUS: $PROJECT_NAME # ${ENV,var="build.label"}
or -to-
SUBJECT=Jenkins Build $BUILD_STATUS: $PROJECT_NAME # ${ENV,var="version.label"}
I dont have to go in Jenkins job configuration and change it there. I'll just change my config file and there you'll see the change in the email notification as Jenkins job's EMAIL SUBJECT box is stil containing $SUBJECT variable which's defined in our config file.
5. BASICALLY, what we need in the above request is...
similarly like you allowed nested contents in the JELLY script (EMAIL CONTENT area),
can we have the same "nested" capability in other parts of the JENKINS jobs where we specify some variables (it can be Email's fields/boxes, or it can be any field/box in Jenkins job's whole configuraiton).
What we want to achieve here is (3 feet view):
if X=$Y and if Y=${VAR}-I_like_it and VAR=FIFA.
Then X should result as:
"FIFA-I_like_it"
Apart from that, when can we expect the nested funcationality of Jelly to be included in the next version of Jenkins build .war? Kindly advise.
Thanks.
Regards
Arun Sangal
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14299) EMAIL-EXT - Jenkins Configuraiton boxes / fields doesn't allow NESTED contents.
Arun Sangal
created JENKINS-14299
EMAIL-EXT - Jenkins Configuraiton boxes / fields doesnt allow NESTED contents.
Issue Type:
Improvement
Assignee:
Slide-O-Mix
Components:
email-ext
Created:
03/Jul/12 4:47 PM
Description:
Thanks a lot to "Slide" for resolving: https://issues.jenkins-ci.org/browse/JENKINS-14210
Improvement/Issue: (EMAIL-EXT - FILE token doesn't allow NESTED contents.)
Viewers: Before reading below, it's recommended to see the above link first (not required though).
==
Hi Slide,
Now, similar to the above request.
In the Editable email notification (Email-ext plugin), we have Subject, Recepients etc fields.
What I was wondering is if I can defined those in all of my Jenkins jobs as one variable like: $RECEPIENTS, $SUBJECT etc. Now, what I'll do is, I'll set these variables from a file that I'll use as a environment variable property file. i.e.
If I give C:\giga\email.config.jobname.instancename.txt as the environment file withing Jenkins JOB, then, inside this file, I'll set the variables for EMAIL variables like:
RECEPIENTS=a...@xyz.com, g...@fifa.com
SUBJECT=$INSTANCE_NAME Build $BUILD_STATUS: $PROJECT_NAME # $BUILD_NUMBER
or
SUBJECT=$INSTANCE_NAME Build $BUILD_STATUS: $PROJECT_NAME # ${ENV,var="build.label"}
NOW, seems like when I tried using this behaviour, I found that an environment variable IF containing another variable are NOT EXPANDING as well. Is there any way, we can achieve this too.
Now, your question towards me would be:
1. Why dont I use the above variables in the Jenkins job directly and remain silent / happy ???
Actually to answer it: I see the following conclusions:
1. As I have many Jenkins job, I want all the jobs to reflect MINIMAL configuration at the Jenkins setting i.e. if Email Ext "SUBJECT" box contains: $SUBJECT
only, then, it'll lot easier for the new user to understand and learn.
2. All the jobs will be SAME as far as EMAIL-EXT (Editable email notification) section is concerned. SAME in the sense of using the environment variables.
3. Definition of these environment variables DONT have to be defined at the Jenkins job level as we will create a config file and define the variables there and just use one variable name per box (for each Editable email notification fields/boxes).
4. If someday we need to change the subject,
FROM:
SUBJECT=$INSTANCE_NAME Build $BUILD_STATUS: $PROJECT_NAME # $BUILD_NUMBER
to
SUBJECT=$INSTANCE_NAME Build $BUILD_STATUS: $PROJECT_NAME # ${ENV,var="build.label"}
or to
SUBJECT=Jenkins Build $BUILD_STATUS: $PROJECT_NAME # ${ENV,var="version.label"}
I dont have to go in Jenkins job configuration and change it there. I'll just change my config file and there you'll see the change in the email notification as Jenkins job's EMAIL SUBJECT box is stil containing $SUBJECT variable which's defined in our config file.
5. BASICALLY, what we need in the above request is...
similarly like you allowed nested contents in the JELLY script (EMAIL CONTENT area),
can we have the same "nested" capability in other parts of the JENKINS jobs where we specify some variables (it can be Email's fields/boxes, or it can be any field/box in Jenkins job's whole configuraiton).
What we want to achieve here is (3 feet view):
if X=$Y and if Y=${VAR}-I_like_it and VAR=FIFA.
Then X should result as:
"FIFA-I_like_it"
Apart from that, when can we expect the nested funcationality of Jelly to be included in the next version of Jenkins build .war? Kindly advise.
Thanks.
Regards
Arun Sangal
Due Date:
31/Jul/12 12:00 AM
Environment:
Any Windows / Unix / Linux
Project:
Jenkins
Labels:
plugin
email-ext
configuration
Jenkins
[JIRA] (JENKINS-8916) Allowing same type of parameter for triggered build more than once seems redundant
Daniel Beck commented on JENKINS-8916 Allowing same type of parameter for triggered build more than once seems redundant All parameter sources are only supported once now, i.e. it's not possible to specify multiple property files anymore? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14300) unable to checkout svn Caused by: hudson/remoting/PipeWindow$Key
nicolas dejovani created JENKINS-14300 unable to checkout svn Caused by: hudson/remoting/PipeWindow$Key Issue Type: Bug Assignee: Unassigned Components: subversion Created: 03/Jul/12 5:08 PM Description: I get the following exception from a lot of my jobs (Matrix or simple one): Started by an SCM change Building remotely on oaf1vm3-ci-2-w hudson.util.IOException2: remote file operation failed: D:/jenkins/ws/V5.2R0E0 at hudson.remoting.Channel@2696dfcf:oaf1vm3-ci-2-w at hudson.FilePath.act(FilePath.java:779) at hudson.FilePath.act(FilePath.java:765) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:743) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:685) at hudson.model.AbstractProject.checkout(AbstractProject.java:1195) at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:568) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:457) at hudson.model.Run.run(Run.java:1404) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) Caused by: java.io.IOException: Remote call on oaf1vm3-ci-2-w failed at hudson.remoting.Channel.call(Channel.java:690) at hudson.FilePath.act(FilePath.java:772) ... 10 more Caused by: java.lang.NoClassDefFoundError: hudson/remoting/PipeWindow$Key at hudson.remoting.Channel.getPipeWindow(Channel.java:654) at hudson.remoting.ProxyOutputStream.connect(ProxyOutputStream.java:84) at hudson.remoting.ProxyOutputStream.init(ProxyOutputStream.java:70) at hudson.remoting.RemoteOutputStream.readObject(RemoteOutputStream.java:90) 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 java.io.ObjectStreamClass.invokeReadObject(Unknown Source) at java.io.ObjectInputStream.readSerialData(Unknown Source) at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source) at java.io.ObjectInputStream.readObject0(Unknown Source) at java.io.ObjectInputStream.readObject(Unknown Source) at hudson.util.StreamTaskListener.readObject(StreamTaskListener.java:166) 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 java.io.ObjectStreamClass.invokeReadObject(Unknown Source) at java.io.ObjectInputStream.readSerialData(Unknown Source) at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source) at java.io.ObjectInputStream.readObject0(Unknown Source) at java.io.ObjectInputStream.defaultReadFields(Unknown Source) at java.io.ObjectInputStream.readSerialData(Unknown Source) at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source) at java.io.ObjectInputStream.readObject0(Unknown Source) at java.io.ObjectInputStream.defaultReadFields(Unknown Source) at java.io.ObjectInputStream.readSerialData(Unknown Source) at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source) at java.io.ObjectInputStream.readObject0(Unknown Source) at java.io.ObjectInputStream.readObject(Unknown Source) at hudson.remoting.UserRequest.deserialize(UserRequest.java:182) at hudson.remoting.UserRequest.perform(UserRequest.java:98) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:287) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.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) Due Date: 03/Jul/12 12:00 AM Environment:
[JIRA] (JENKINS-13000) Git repositories (git plugin 1.1.15) used within Jenkins multiple SCMs plugin (0.2) are not detected by the remote-trigger hook functionality
Liya Katz commented on JENKINS-13000 Git repositories (git plugin 1.1.15) used within Jenkins multiple SCMs plugin (0.2) are not detected by the remote-trigger hook functionality It seems to be a limitation of the MultiSCM plugin - see https://wiki.jenkins-ci.org/display/JENKINS/Multiple+SCMs+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
[JIRA] (JENKINS-14301) Failed to use multiple plugin repositories
Nickolay Rumyantsev created JENKINS-14301 Failed to use multiple plugin repositories Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 03/Jul/12 5:18 PM Description: I tried to configure two plugin repos: internal and updates.jenkins-ci.org (base) on my jenkins instance. For internal server I create my own update-center.json file. If I specify only my repo, or only base repo - I have no problems with plugin manager(plugins are displayed, installed and updated correctly). But if I set two repos at the same time (by groovy script), I have a problem. I can see plugins only from one server but duplicated twice (or any other times depends on how much repos did I add). Jenkins error log says that data was obtained without errors (signature fails or JSON parsing fails and others) from all repos - default and mine. Unfortunately Plugin manager (via User Interface and Groovy scripts) shows that myUpdateSite.getAvailables and defaultUpdateSite.getAvailables contain same data, that is impossible according to contents of JSON update files. Due Date: 03/Jul/12 12:00 AM Environment: winXP and Linux Project: Jenkins Labels: plugins jenkins Priority: Minor Reporter: Nickolay Rumyantsev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13715) User email suffixes are getting overwritten with the with the subversion repo UUID
David Pattison commented on JENKINS-13715 User email suffixes are getting overwritten with the with the subversion repo UUID ?xml version='1.0' encoding='UTF-8'? user fullNamechandrav/fullName properties hudson.model.MyViewsProperty views hudson.model.AllView owner class="hudson.model.MyViewsProperty" reference="../../.."/ nameAll/name filterExecutorsfalse/filterExecutors filterQueuefalse/filterQueue properties class="hudson.model.View$PropertyList"/ /hudson.model.AllView /views /hudson.model.MyViewsProperty jenkins.security.ApiTokenProperty apiToken/apiToken /jenkins.security.ApiTokenProperty hudson.plugins.ircbot.IrcUserProperty/ hudson.tasks.Mailer_-UserProperty emailAddresschandrav@046000e8-c612-472f-bb51-fe359d1450d5/emailAddress /hudson.tasks.Mailer_-UserProperty /properties i can edit it/remove it and it will still come back This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14232) EnvInject/Parameterized trigger not handling properties file with logical lines
Mike Harris commented on JENKINS-14232 EnvInject/Parameterized trigger not handling properties file with logical lines I verified version 1.59 works for me. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14299) Jenkins Configuraiton boxes / fields doesn't allow NESTED contents.
Arun Sangal
commented on JENKINS-14299
Jenkins Configuraiton boxes / fields doesnt allow NESTED contents.
Thanks Slide. Yep, I'll do that as a last option. Also, I thought again - if we achieve the above, we may land into an infinite nested loop during variable expansion. Otherwise, this would have been a great improvement.
ex:
if X=$Y and if Y=${VAR}-I_like_it and VAR=FIFA_$X.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13715) User email suffixes are getting overwritten with the with the subversion repo UUID
David Pattison commented on JENKINS-13715 User email suffixes are getting overwritten with the with the subversion repo UUID that is the bug i keep setting it to the correct value and it gets reverted to the svn uuid. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13114) dropdown views taskbar: error when saving jenkins config page
Billy Foss commented on JENKINS-13114 dropdown views taskbar: error when saving jenkins config page I tried on a 1.465 install and it would not save even when 'Default View TabBar' was selected. Lost JDK configuration too. So it seems better on 1.472. Don't have 1.455 to test with. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-6215) Hudson.getInstance().getRootUrl() returns incorrect URL if Hudson is running on different prot.
Tim Pizey commented on JENKINS-6215 Hudson.getInstance().getRootUrl() returns incorrect URL if Hudson is running on different prot. Another datapoint: this works fine for me on a an https url without a port but on an http url with a port eg http://localhost:21337/ the url returned is http://http//localhost:21337/job/... This bit me in the HTMLReport 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
[JIRA] (JENKINS-14248) DiskUsage dont show values.
Mauricio Fenoglio commented on JENKINS-14248 DiskUsage dont show values. vjuranek How do get the disk usage?. Maybe there are a privileges problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14183) Nexus 502 error during builds
Jørgen Tjernø updated JENKINS-14183 Nexus 502 error during builds This jenkins-plugin-runtime is a component for ruby plugins etc. Changing to maven (I assume that's where it belongs?) Change By: Jørgen Tjernø (03/Jul/12 8:05 PM) Assignee: JørgenTjernø Component/s: maven Component/s: ruby-plugin-runtime This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14183) Nexus 502 error during builds
Jørgen Tjernø closed JENKINS-14183 as Not A Defect Nexus 502 error during builds Reclosing. Change By: Jørgen Tjernø (03/Jul/12 8:05 PM) Status: Reopened Closed Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13795) NPE with Flexible Publisher job
SCM/JIRA link daemon commented on JENKINS-13795 NPE with Flexible Publisher job Code changed in jenkins User: bap2000 Path: src/main/java/org/jenkins_ci/plugins/flexible_publish/ConditionalPublisher.java src/main/resources/org/jenkins_ci/plugins/flexible_publish/ConditionalPublisher/config.jelly http://jenkins-ci.org/commit/flexible-publish-plugin/2c906b84b1fed6e1b0781cb98cadf6579478f592 Log: FIXED JENKINS-13795 NPE when configuring flexible publish in new job This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14294) Action List is empty when adding Post-Build Action
bap resolved JENKINS-14294 as Duplicate Action List is empty when adding Post-Build Action Change By: bap (03/Jul/12 9:02 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14303) Config changes are logged even when job saved with no changes
Patrick Connolly created JENKINS-14303 Config changes are logged even when job saved with no changes Issue Type: Bug Assignee: Mirko Friedenhagen Components: jobconfighistory Created: 03/Jul/12 10:03 PM Description: Wasn't sure whether this was a bug or by design, but would it not make more sense to only log changes when the config files has actually been altered (as opposed to simply saved)? Not such a large concern when all changes are made by people, but when using a plugin that alters config.xml programmatically, lots of noise can accumulate in the change log. In particular, the build description setter plugin saves the job configs on each run. Thanks! Project: Jenkins Priority: Minor Reporter: Patrick Connolly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14290) Support for Ivy project type
SCM/JIRA link daemon commented on JENKINS-14290 Support for Ivy project type Code changed in jenkins User: Gregory Boissinot Path: pom.xml src/main/java/org/jenkinsci/plugins/envinject/EnvInjectListener.java src/main/java/org/jenkinsci/plugins/envinject/service/BuildWrapperService.java src/main/java/org/jenkinsci/plugins/envinject/service/EnvInjectPasswordsMasker.java http://jenkins-ci.org/commit/envinject-plugin/729f70a6658f37ff19afc762e3e4a26e6c1a9d69 Log: Fix JENKINS-14290 Compare: https://github.com/jenkinsci/envinject-plugin/compare/24d4fe426581...729f70a6658f This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12764) Missing Overview in Violations Plugin
Arthur Rio commented on JENKINS-12764 Missing Overview in Violations Plugin Just uploaded your HPI, works like a charm Thank you so much This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14304) StackOverflow on remote slave
Juan Civile created JENKINS-14304 StackOverflow on remote slave Issue Type: Bug Assignee: Unassigned Attachments: jenkins build log.txt Components: master-slave Created: 03/Jul/12 10:56 PM Description: I configured a slave to handle some builds that we're taking too much time in our server. Now some of the builds on the slave fail with hudson.util.IOException2 caused by a StackOverflowError. I've attached the build log for the build that fails most often. Environment: Linux with Ubuntu 10.04 LTS Oracle Java 1.6.0_33-b03 Project: Jenkins Priority: Major Reporter: Juan Civile This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13715) User email suffixes are getting overwritten with the with the subversion repo UUID
David Pattison commented on JENKINS-13715 User email suffixes are getting overwritten with the with the subversion repo UUID You can update the user profile in jenkins. It will correctly save but on the next build it gets reverted. we are running a slightly older version of svn (server): svn, version 1.4.6 (r28521) compiled Mar 23 2011, 22:50:00 Probably next week we will do a jenkins upgrade to 1.447.2 (currently 1.447.1) and svn plugin v1.42 (currently 1.40) My gut feeling it is it is a bug between the jenkins svn plugin and the version of svn we are using. We have a plan to upgrade to svn 1.7 in august/september. Thanks for looking into this! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14223) accessing Jenkins through https produces browser warning about mixed https/http content
Dies Koper commented on JENKINS-14223 accessing Jenkins through https produces browser warning about mixed https/http content FYI, Rhodecode allows two ways to make it work with https. One is a setting on Rhodecode, as Jenkins has. The other is probably more like what brenuart and I were expecting: an external way, by adding an HTTP header (HTTP_X_URL_SCHEME) to requests. http://packages.python.org/RhodeCode/setup.html#https-support This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14305) Technical Version has marketing version at the beginning
Reuben Bijl created JENKINS-14305 Technical Version has marketing version at the beginning Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: xcode Created: 04/Jul/12 5:38 AM Description: check line 235 in XCodeBuilder.java. The output object never gets reinitialised before getting the technical version. This makes the technical version incorrect. Project: Jenkins Priority: Major Reporter: Reuben Bijl This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
