[JIRA] (JENKINS-14463) email ext plugin : full console log mail
dev D updated JENKINS-14463 email ext plugin : full console log mail Attached job config file Change By: dev D (18/Jul/12 6:50 AM) Attachment: config.xml This message is automatically generated by JIRA. 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-14463) email ext plugin : full console log mail
dev D
commented on JENKINS-14463
email ext plugin : full console log mail
Thank u . It worked
${BUILD_LOG, maxLines=8000, escapeHtml=true}
This message is automatically generated by JIRA.
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-10333) Maven jobs don't report all details of failures
Federico Paolantoni commented on JENKINS-10333 Maven jobs dont report all details of failures Same issue with jenkins 1.447.2, maven 3.0.2 and plugin version 2.0.2. There is some relation between the plugin and jenkins. Because in other environment, running build from cli, the console output shows the correct error log. This message is automatically generated by JIRA. 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-14477) Build fails for svn revision check failed (403 Forbidden)
tigren zhang commented on JENKINS-14477 Build fails for svn revision check failed (403 Forbidden) Oh sorry, but who can help to delete the first image? 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-7781) Test Statistics Grid double counting aggregated tests
Marco Ambu commented on JENKINS-7781 Test Statistics Grid double counting aggregated tests I don't understand the behaviour either, but you said that this also happens when displaying the test results in jenkins. This is important because we don't do any special processing with the test results and we get them directly from jenkins APIs. Can you please show me also the standard test result for the main job? Does it show the 5 missing tests? Need to check about the disabled job: do you think we should include it as well in the total count? If not we could "mark it" in a special way so that it does not cause confusion in the table? What version of the dashboard-view plugin are you using? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14478) 1.474 breaks adding a list-view to sectioned-view plugin
Dirk Kuypers created JENKINS-14478 1.474 breaks adding a list-view to sectioned-view plugin Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 18/Jul/12 9:01 AM Description: I just wanted to add another list-view section in a sectioned view existing for some time now. I am using Jenkins 1.474, all plugins latest. As the sectioned view plugin was updated last year I suspect that there broke something in Jenkins core because downgrading Jenkins to 1.473 makes the bug disappear, so my guess is that it is a core issue?! This is the stack trace I get when trying to save the edited sectioned-view: Status Code: 500 Exception: net.sf.json.JSONException: JSONObjectuseincluderegex is not a JSONObject. Stacktrace: javax.servlet.ServletException: net.sf.json.JSONException: JSONObjectuseincluderegex is not a JSONObject. at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:616) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) 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 net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:202) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:175) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) 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.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at
[JIRA] (JENKINS-13864) JDK auto installer installs to a different path than JAVA_HOME for a build uses
Nikolay Diakov commented on JENKINS-13864 JDK auto installer installs to a different path than JAVA_HOME for a build uses Ok, I have finally managed to cleanup the old config paths - these were in the registry at various locations, such as: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\Folders HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Development Kit\1.6.0_31 ... What you need to do is search in all keys/values/data for the JDK signature, e.g., "1.6.0_31", also search the wrong JDK paths, e.g., "hudson" in this case. Then all remote installations from the master of JDKs will proceed in the proper places. I guess the headless installer that forces 'yes' on all questions, also uses any default suggestions that the installer may make for directories, and an existing one happens to override the instructed place to install argh! This message is automatically generated by JIRA. 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-14479) Wiki documentation
wernight created JENKINS-14479 Wiki documentation Issue Type: Task Assignee: rsandell Components: gerrit-trigger Created: 18/Jul/12 9:17 AM Description: Gerrit can be complex and a Wiki documentation point would be more than useful. It's nearly necessary. The introduction on Jenkins page is far from enough and community cannot really participate well on it. Some topics or FAQ on top of my mind: Can multiple jobs review the same changeset (possibly giving different answers)? What are the access rights I need to setup in Gerrit? -- Add to non-interactive, then give read right... Why doesn't the build button work? Can I disable it? -- Re-trigger I have found answer to some the hard way and could have shared it. Other answer (like the first question above) I still need to figure it out. Project: Jenkins Priority: Major Reporter: wernight This message is automatically generated by JIRA. 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-14479) Wiki documentation
wernight updated JENKINS-14479 Wiki documentation Change By: wernight (18/Jul/12 9:39 AM) Description: GerritcanbecomplexandaWikidocumentationpointwouldbemorethanuseful.Itsnearlynecessary.TheintroductiononJenkinspageisfarfromenoughandcommunitycannotreallyparticipatewellonit.SometopicsorFAQontopofmymind:-Canmultiplejobsreviewthesamechangeset(possiblygivingdifferentanswers)?-WhataretheaccessrightsIneedtosetupinGerrit?--Addtonon-interactive,thengivereadright...-Whydoesntthebuildbuttonwork?CanIdisableit?--Re-triggerIhavefoundanswertosomethehardwayandcouldhavesharedit.Otheranswer(likethefirstquestionabove)Istillneedtofigureitout. Hereisagoodreferencepointtoinclude:http://strongspace.com/rtyler/public/gerrit-jenkins-notes.pdf This message is automatically generated by JIRA. 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-14479) Wiki documentation
wernight updated JENKINS-14479 Wiki documentation Change By: wernight (18/Jul/12 9:44 AM) Description: GerritcanbecomplexandaWikidocumentationpointwouldbemorethanuseful.Itsnearlynecessary.TheintroductiononJenkinspageisfarfromenoughandcommunitycannotreallyparticipatewellonit.SometopicsorFAQontopofmymind:-Canmultiplejobsreviewthesamechangeset(possiblygivingdifferentanswers)? --yes,seearound90%ofthePDFbelowbutshouldbeelaborated -WhataretheaccessrightsIneedtosetupinGerrit?--Addtonon-interactive,thengivereadright...-Whydoesntthebuildbuttonwork?CanIdisableit?--Re-trigger -Howtohavethebuildbuttontobuildfromabranchbydefault? Ihavefoundanswertosomethehardwayandcouldhavesharedit. Otheranswer(likethefirstquestionabove)Istillneedtofigureitout. Hereisagoodreferencepointtoinclude:http://strongspace.com/rtyler/public/gerrit-jenkins-notes.pdf This message is automatically generated by JIRA. 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-13989) Config Rotator summary section is missing logo
Mads Nielsen resolved JENKINS-13989 as Fixed Config Rotator summary section is missing logo Fixed in 1.0.1 Change By: Mads Nielsen (18/Jul/12 10:04 AM) Status: InProgress Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11074) LOADING Overlay does not go away - IE 8
naveen karnati commented on JENKINS-11074 LOADING Overlay does not go away - IE 8 Similar issue here. A quick fix is, I have copied "hudson-behavior.js" "autocomplete-min.js" from old jenkins version (1.410) to our newer jenkins version (1.447), cleared browsing history and it solved the problem. In my case culprit is both autocomplete-min.js hudson-behavior.js Message: 'YAHOO.util.DataSourceBase.TYPE_JSON' is null or not an object Line: 7 Char: 343 Code: 0 URI: http:xx/scripts/yui/autocomplete/autocomplete-min.js Message: Object expected Line: 681 Char: 9 Code: 0 URI: http:xx/scripts/hudson-behavior.js This message is automatically generated by JIRA. 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.
vjuranek commented on JENKINS-14248 DiskUsage dont show values. @Mauricio Fenoglio you just need to allow show graphs on project pages in Jenkins global config, but don't need any special privileges. If you are able to view overall disk usage page, you should be able to see the numbers as well, so I'm quite sure the problem is somewhere else than missing rights or something like this. @Martin Stenderup thanks for investigation. I'll try to re-check the changes made since rel. 0.12 if I spot any change which could cause such kind of problems. Obvious candidate is https://github.com/jenkinsci/disk-usage-plugin/pull/5 introduced in rel 0.15, but IIRC I tested this change quite carefully and it seemed to work fine. Anyway I'll re-check. This message is automatically generated by JIRA. 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-14480) Git plugin 1.1.21 cannot build branches with repository specified but no wildcards
Richard Maw
created JENKINS-14480
Git plugin 1.1.21 cannot build branches with repository specified but no wildcards
Issue Type:
Bug
Affects Versions:
current
Assignee:
Nicolas De Loof
Components:
git
Created:
18/Jul/12 10:57 AM
Description:
If a branch to build is specified like REPONAME/BRANCHNAME then the git plugin will look for branches named REPONAME/REPONAME/BRANCHNAME.
Worse still, if the git repository has multiple repositories configured, it will then search for OTHERREPO/REPONAME/REPONAME/BRANCHNAME.
I believe this is the same cause as https://issues.jenkins-ci.org/browse/JENKINS-14394
I believe the problem code to be https://github.com/jenkinsci/git-plugin/blob/master/src/main/java/hudson/plugins/git/util/DefaultBuildChooser.java#L73, the block after 'if (!singleBranch.contains("/"))' should be inside it, since that is for unqialified branches.
I worked around this issue by changing the refspecs to include an extra component in the branch, so origin/master becomes origin/UGLYHACK/master with +refs/heads/:+refs/remotes/origin/UGLYHACK/, so the branch specification becomes origin/*/master.
Environment:
Debian Squeeze on x86_64
Project:
Jenkins
Priority:
Major
Reporter:
Richard Maw
This message is automatically generated by JIRA.
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.
Martin Stenderup commented on JENKINS-14248 DiskUsage dont show values. @vjuranek Hi, I just had a crasy idea, and upgraded the plugin in steps. First from 0.12 to 0.14 and then 0.17. It now shows values even in 0.17, perhaps it has something to do with first time install of the plugin. I haven't yet verified if it gathers values correctly in 0.17, or just shows the values cached by 0.12. This message is automatically generated by JIRA. 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-14480) Git plugin 1.1.21 cannot build branches with repository specified but no wildcards
Richard Maw updated JENKINS-14480 Git plugin 1.1.21 cannot build branches with repository specified but no wildcards Change By: Richard Maw (18/Jul/12 10:58 AM) Description: IfabranchtobuildisspecifiedlikeREPONAME/BRANCHNAMEthenthegitpluginwilllookforbranchesnamedREPONAME/REPONAME/BRANCHNAME.Worsestill,ifthegitrepositoryhasmultiplerepositoriesconfigured,itwillthensearchforOTHERREPO/REPONAME/REPONAME/BRANCHNAME.Ibelievethisisthesamecauseashttps://issues.jenkins-ci.org/browse/JENKINS-14394Ibelievetheproblemcodetobehttps://github.com/jenkinsci/git-plugin/blob/master/src/main/java/hudson/plugins/git/util/DefaultBuildChooser.java#L73,theblockafterif(!singleBranch.contains(/))shouldbeinsideit,sincethatisforunqialifiedbranches.Iworkedaroundthisissuebychangingtherefspecstoincludeanextracomponentinthebranch,soorigin/masterbecomesorigin/UGLYHACK/masterwith+refs/heads/ \ *:refs/remotes/origin/UGLYHACK/*,sothebranchspecificationbecomesorigin/ \ */master. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14474) Multi-configuration jobs disappear from the list when Jenkins configuration is reloaded from disk
Sarah Woodall assigned JENKINS-14474 to Sarah Woodall Multi-configuration jobs disappear from the list when Jenkins configuration is reloaded from disk Change By: Sarah Woodall (18/Jul/12 11:08 AM) Assignee: SarahWoodall This message is automatically generated by JIRA. 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-14474) Multi-configuration jobs disappear from the list when Jenkins configuration is reloaded from disk
Sarah Woodall assigned JENKINS-14474 to Unassigned Multi-configuration jobs disappear from the list when Jenkins configuration is reloaded from disk Change By: Sarah Woodall (18/Jul/12 11:08 AM) Assignee: SarahWoodall This message is automatically generated by JIRA. 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-11186) Jenkins hangs while producing testReport
Martin Heinrich commented on JENKINS-11186 Jenkins hangs while producing testReport same here, assuming a different reason. (Jenkins ver. 1.473) loading testReport for only one specific build takes more the 1 minute but succeeds. the build in question as "large" diffs: package1: fail_diff -60 diff -225 package6: diff +114 total_tests in packages: 1339+24+2739+38+74+25+114 = 4353 it seems like jenkins is recalculating the diff on this static(?!) page every time it is loaded... and the static(?!) page has auto refresh. This message is automatically generated by JIRA. 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-11186) Jenkins hangs while producing testReport
Martin Heinrich updated JENKINS-11186 Jenkins hangs while producing testReport Change By: Martin Heinrich (18/Jul/12 11:30 AM) Labels: performance Environment: Jenkinsver.1.433 Jenkinsver.1.473 This message is automatically generated by JIRA. 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.
Martin Stenderup edited a comment on JENKINS-14248 DiskUsage dont show values. @vjuranek Hi, I just had a crasy idea, and upgraded the plugin in steps. First from 0.12 to 0.14 and then 0.17. It now shows values even in 0.17, perhaps it has something to do with first time install of the plugin. I haven't yet verified if it gathers values correctly in 0.17, or just shows the values cached by 0.12. Update: It seems it uses the cached values. Sizes of builds started after upgrade to 0.17 are not calculated. This message is automatically generated by JIRA. 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.
Martin Stenderup edited a comment on JENKINS-14248 DiskUsage dont show values. @vjuranek Hi, I just had a crasy idea, and upgraded the plugin in steps. First from 0.12 to 0.14 and then 0.17. It now shows values even in 0.17, perhaps it has something to do with first time install of the plugin. I haven't yet verified if it gathers values correctly in 0.17, or just shows the values cached by 0.12. Update: It seems it uses the cached values. Sizes of builds started after upgrade to 0.17 are not shown. This message is automatically generated by JIRA. 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-14482) com.cloudbees.plugins.flow.JobExecutionFailureException
Ralf Rausch created JENKINS-14482 com.cloudbees.plugins.flow.JobExecutionFailureException Issue Type: Bug Assignee: Nicolas De Loof Attachments: console-output.txt Components: build-flow Created: 18/Jul/12 12:15 PM Description: My Build-Flow "Test-Flow" looks like the following: build( "Test1" ) build( "Test2" ) If Job "Test1" ends with "Finished: UNSTABLE" the "Test-Flow" will break with the following error (see attachment) Environment: Jenkins ver. 1.474 Build Flow Plugin 0.4 Project: Jenkins Priority: Major Reporter: Ralf Rausch This message is automatically generated by JIRA. 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-14483) Remaining Xvfb processes in matrix jobs
Thorsten Kahler created JENKINS-14483 Remaining Xvfb processes in matrix jobs Issue Type: Bug Assignee: zregvart Components: matrix, xvfb Created: 18/Jul/12 12:24 PM Description: Enabling the Xvfb plugin on matrix jobs starts a Xvfb server for the job itself and one for each configuration. The Xvfb servers for the configurations are stoppd properly, but the Xvfb server for the job itself keeps running when the job finishes. This ends up in locked screens and a vast number of directories. We experienced that on a master only instance as well as in master-slave mode. Xvfb plugin version 1.0.2 Project: Jenkins Labels: plugin Priority: Major Reporter: Thorsten Kahler This message is automatically generated by JIRA. 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
Stefan Brausch commented on JENKINS-14303 Config changes are logged even when job saved with no changes You should configure the plugin that it not save duplicate configuration files. This could help you. Description: Do not save the history if there is no change from the previous saved configuration. Duplicate history is often saved if the save option is selected after viewing a configuration without making any adjustments. It is also common for system-level settings, as all system settings are saved again when the main configuration page is saved. This message is automatically generated by JIRA. 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-14445) Recording NUnit tests results very slow
wernight commented on JENKINS-14445 Recording NUnit tests results very slow It's 277 KB. We have like 100 or 200 unit tests but some of a few them may have like 500 tests cases (like those using Random). After that there is the Violation plugin which doesn't seem to log anything in the console (strangely), and Archiving artifacts which is the next I used. I'll try putting NUnit last to check if it comes from Violations. This message is automatically generated by JIRA. 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-14461) Warnings plugin not Java 1.5 compatible?
Trevor Bekolay commented on JENKINS-14461 Warnings plugin not Java 1.5 compatible? Agreed, the error is really not informative... 3.21 worked for a project that had the warnings post-build action already configured, but I've since removed it so I can't try to a build out to see. However, with 3.21 in my 1.474 installation, it now allows me to add "Scan compiler warnings" as a post-build action, but when I press "Add" to add a new parser, nothing happens, and nothing appears in the log. This is an elusive bug! I'm going to try a bunch of different versions of the plugin to see if I can get any of them working. This message is automatically generated by JIRA. 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-14479) Wiki documentation
wernight commented on JENKINS-14479 Wiki documentation Just saw I can edit the Jenkins wiki page. I may do 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-14461) Warnings plugin not Java 1.5 compatible?
Trevor Bekolay commented on JENKINS-14461 Warnings plugin not Java 1.5 compatible? Oh, perhaps this is a bit more helpful of an error message. I installed 4.12 and now get this in the log when trying to add a post-build action (relevant lines only): WARNING: Caught exception evaluating: action.iconFileName!=null. Reason: java.lang.reflect.InvocationTargetException ... Caused by: java.lang.UnsupportedClassVersionError: Bad version number in .class file ... at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at hudson.plugins.warnings.WarningsResultAction.getSmallImage(WarningsResultAction.java:63) at hudson.plugins.analysis.core.AbstractResultAction.getIconFileName(AbstractResultAction.java:138) This message is automatically generated by JIRA. 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-14479) Wiki documentation
wernight resolved JENKINS-14479 as Fixed Wiki documentation Change By: wernight (18/Jul/12 1:24 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-14479) Wiki documentation
wernight stopped work on JENKINS-14479 Wiki documentation Change By: wernight (18/Jul/12 1:24 PM) Status: InProgress 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-14479) Wiki documentation
wernight assigned JENKINS-14479 to wernight Wiki documentation Change By: wernight (18/Jul/12 1:24 PM) Assignee: rsandell wernight This message is automatically generated by JIRA. 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-14484) Define time period in which a mail is desired
Robin Pradel created JENKINS-14484 Define time period in which a mail is desired Issue Type: Improvement Affects Versions: current Assignee: Slide-O-Mix Components: email-ext Created: 18/Jul/12 1:29 PM Description: We build every night our projects for testing issues. Also the system should provide on the same way the latest development state to all developers. When a quick fix rises or extra test runs are manually triggered, it would be nice to disable email notification because the user triggering this build will observe or check it by browser. In general these actions take place during the day, so a rule like: "send email on error only for builds between 21:00 - 06:00" would be very nice. Project: Jenkins Priority: Major Reporter: Robin Pradel This message is automatically generated by JIRA. 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-14485) Continue job after previous job has failed
Marcus Warm updated JENKINS-14485 Continue job after previous job has failed Change By: Marcus Warm (18/Jul/12 1:35 PM) Attachment: buildAlways.txt This message is automatically generated by JIRA. 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-14486) Provide help icon for common settings
wernight created JENKINS-14486 Provide help icon for common settings Issue Type: Task Assignee: Nicolas De Loof Components: git Created: 18/Jul/12 1:40 PM Description: Two settings should have a help message to describe what they do: "Clean after checkout": Does a git clean -xdf globally and on each submodule? "Wipe out workspace before build" All other settings should also have some help but they are probably less frequently used. Project: Jenkins Priority: Major Reporter: wernight This message is automatically generated by JIRA. 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-7781) Test Statistics Grid double counting aggregated tests
ellisonch commented on JENKINS-7781 Test Statistics Grid double counting aggregated tests On the c-semantics project page, it says "Latest Test Result (85 failures / ±0)" without double counting that. If I click that link, it gives me "5 tests", which is correct for the main job. If I click to "aggregated test result" on the left, I see good numbers. 85 failures, 1554 total tests, 526 unit tests, 33 integration, 777 torture, 127 third party, 91 negative, and N/A csmith. It does leave out the 5 tests in the main job, but it doesn't double count anything. It's been so long since my initial report that I'm not sure what I used to see. We're using Jenkins 1.444 and Dashboard View 2.1 now. I won't be able to upgrade or try installing different things because I'm leaving the group. I do know that the double counting has happened pretty reliably over the past few years. Hope this helps! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14487) Allow parameterization of whether to use Xvnc for a build
David Watson created JENKINS-14487 Allow parameterization of whether to use Xvnc for a build Issue Type: New Feature Assignee: Unassigned Components: xvnc Created: 18/Jul/12 2:36 PM Description: I have a job that I fire off with different parameters to run different UTs across my jenkins cluster. Most of my UTs are headless, but a few require a GUI, and I'd like to only start up Xvnc for the runs where it is necessary. A solution would be to allow a boolean parameter that controls whether or not Xvnc is used on a per-run basis. Project: Jenkins Priority: Major Reporter: David Watson This message is automatically generated by JIRA. 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-14461) Warnings plugin not Java 1.5 compatible?
Trevor Bekolay commented on JENKINS-14461 Warnings plugin not Java 1.5 compatible? analysis-core is version 1.43, yeah. This message is automatically generated by JIRA. 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-7501) POST'ing a config.xml to create a new job via the XML API results in newlines being removed from XML elements containing them (ant build steps, winbatch steps, etc)
Bernhard Wiedemann commented on JENKINS-7501 POSTing a config.xml to create a new job via the XML API results in newlines being removed from XML elements containing them (ant build steps, winbatch steps, etc) still present in Jenkins 1.461 It is breaking backup/restore for us because we have multi-line properties to set multiple shell variables This message is automatically generated by JIRA. 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-14445) Recording NUnit tests results very slow
wernight commented on JENKINS-14445 Recording NUnit tests results very slow Now that's very particular, after moving Violations just before NUnit I don't even see those 5 min wasted anywhere. NUnit takes only a few seconds which is perfectly fine. Thank you for you help. This message is automatically generated by JIRA. 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-13677) Active Direcoty Plugin not encrypted - FINE: Failed to start TLS. Authentication will be done via plain-text LDAP
Jolly E commented on JENKINS-13677 Active Direcoty Plugin not encrypted - FINE: Failed to start TLS. Authentication will be done via plain-text LDAP Can anybody help me with 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-14488) No way to use nodelabelparameter to specify multiple labels
David Watson created JENKINS-14488 No way to use nodelabelparameter to specify multiple labels Issue Type: Bug Assignee: domi Components: nodelabelparameter Created: 18/Jul/12 3:57 PM Description: I need the ability to specify multiple labels (ANDed together) through the NodeLabelParameter. This doesn't appear to work. I've tried both making multiple NodeLabelParameters and filling those in, but it only takes the first one. I've also tried separating the labels with commas or spaces, and it complains that there are no nodes with the label 'label1 label2' online. Project: Jenkins Priority: Major Reporter: David Watson This message is automatically generated by JIRA. 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-14488) No way to use nodelabelparameter to specify multiple labels
David Watson updated JENKINS-14488 No way to use nodelabelparameter to specify multiple labels Change By: David Watson (18/Jul/12 4:05 PM) Description: Ineedtheabilitytospecifymultiplelabels(ANDedtogether)throughthe NodeLabelParameter LabelParameter .Thisdoesntappeartowork.Ivetriedbothmakingmultiple NodeLabelParameters LabelParameters andfillingthosein,butitonlytakesthefirstone.Ivealsotriedseparatingthelabelswithcommasorspaces,anditcomplainsthattherearenonodeswiththelabellabel1label2online. This message is automatically generated by JIRA. 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-14345) Grails wrapper doesn't respect Project Base Directory
kiy0taka assigned JENKINS-14345 to kiy0taka Grails wrapper doesnt respect Project Base Directory Change By: kiy0taka (18/Jul/12 4:07 PM) Assignee: jeffg2one kiy0taka This message is automatically generated by JIRA. 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-14345) Grails wrapper doesn't respect Project Base Directory
kiy0taka resolved JENKINS-14345 as Fixed Grails wrapper doesnt respect Project Base Directory Change By: kiy0taka (18/Jul/12 4:08 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-14445) Recording NUnit tests results very slow
wernight resolved JENKINS-14445 as Not A Defect Recording NUnit tests results very slow Change By: wernight (18/Jul/12 4:11 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-14489) Exclusion per slave
wernight created JENKINS-14489 Exclusion per slave Issue Type: Task Assignee: Unassigned Components: exclusion Created: 18/Jul/12 4:13 PM Description: Nearly all my exclusions are because jobs use a resource shared on that machine but not between machines. So I actually need an exclusion for each slave to avoid the same slave to run the critical block, but two different slave should be allowed to run the critical block. Project: Jenkins Priority: Major Reporter: wernight This message is automatically generated by JIRA. 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-10371) Ubuntu DVD iso not recognized as valid
evernat updated JENKINS-10371 Ubuntu DVD iso not recognized as valid Change By: evernat (18/Jul/12 4:21 PM) Component/s: pxe Component/s: 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-10398) Jenkins only uses hostname not fqdn for EHLO
evernat resolved JENKINS-10398 as Duplicate Jenkins only uses hostname not fqdn for EHLO Change By: evernat (18/Jul/12 4:42 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-10405) Post-receive hook doesn't work
Jonathan Vaughn commented on JENKINS-10405 Post-receive hook doesnt work We have also encountered an issue with permissions (403 response to POST on the webhook URL) using LDAP security, as lesterp commented on 12/27/2011. We are using Matrix-based security with users and groups in LDAP. We were able to work around it by giving anonymous users Overall read access, however ideally there should be some way to grant github read access without giving anonymous users github access, and preferably without having to create a dummy github account in LDAP (is that an option even? where do we tell github what password to use?). This message is automatically generated by JIRA. 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-10405) Post-receive hook doesn't work
Jonathan Vaughn edited a comment on JENKINS-10405 Post-receive hook doesnt work We have also encountered an issue with permissions (403 response to POST on the webhook URL) using LDAP security, as lesterp commented on 12/27/2011. We are using Matrix-based security with users and groups in LDAP. We were able to work around it by giving anonymous users Overall read access, however ideally there should be some way to grant github read access without giving anonymous users github access, and preferably without having to create a dummy github account in LDAP (is that an option even? where do we tell github what password to use?). Also, if it makes any difference, we're running on CentOS6 x86_64. This message is automatically generated by JIRA. 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-14429) LDAPS gives Administrative Limit Exceeded error, the recommended steps not applicable
hab 278 resolved JENKINS-14429 as Not A Defect LDAPS gives Administrative Limit Exceeded error, the recommended steps not applicable The file to be modified, LDAPBindSecurityRealm.groovy file was located in JENKINS_HOME/plugins/ldap/WEB-INF/classes/hudson/security/. Change By: hab 278 (18/Jul/12 6:46 PM) Status: Open Resolved Assignee: hab278 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-14491) HTML Publisher Plugin Add button broken after 1.474 upgrade
mcrooney updated JENKINS-14491 HTML Publisher Plugin Add button broken after 1.474 upgrade Change By: mcrooney (18/Jul/12 7:30 PM) Summary: HTMLPublisherPluginAddbutton doesnotwork brokenafter1.474upgrade Component/s: core This message is automatically generated by JIRA. 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-14396) honor Remote FS root
SCM/JIRA link daemon resolved JENKINS-14396 as Fixed honor Remote FS root Change By: SCM/JIRA link daemon (18/Jul/12 7:55 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-14396) honor Remote FS root
SCM/JIRA link daemon commented on JENKINS-14396 honor Remote FS root Code changed in jenkins User: Andrew Bayer Path: src/main/java/jenkins/plugins/jclouds/compute/JCloudsSlaveTemplate.java http://jenkins-ci.org/commit/jclouds-plugin/4fbbddb6ff20fc6527895961d3140855e9cd4e7f Log: FIXED JENKINS-14396 Use fs root as jenkins user home. This message is automatically generated by JIRA. 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-14492) IAE Illegal character(s) in message header value from com.saucelabs.rest.Credential.call
jglick
created JENKINS-14492
IAE Illegal character(s) in message header value from com.saucelabs.rest.Credential.call
Issue Type:
Bug
Assignee:
Kohsuke Kawaguchi
Components:
sauce-ondemand
Created:
18/Jul/12 8:08 PM
Description:
A user reports getting an error message when attempting to use the Test Connection button. The meat of the exception is
java.lang.IllegalArgumentException: Illegal character(s) in message header value: Basic someLongBase64EncodedMessHereEtcEtcEtcEtcEtcEtcEtcEtcEtcEtcEtcEtcEtcAndAnEOL
sun.net.www.protocol.http.HttpURLConnection.checkMessageHeader(HttpURLConnection.java:428)
sun.net.www.protocol.http.HttpURLConnection.isExternalMessageHeaderAllowed(HttpURLConnection.java:394)
sun.net.www.protocol.http.HttpURLConnection.setRequestProperty(HttpURLConnection.java:2374)
sun.net.www.protocol.https.HttpsURLConnectionImpl.setRequestProperty(HttpsURLConnectionImpl.java:296)
com.saucelabs.rest.Credential.call(Credential.java:167)
com.saucelabs.rest.Credential.call(Credential.java:151)
com.saucelabs.rest.SauceTunnelFactory.list(SauceTunnelFactory.java:88)
hudson.plugins.sauce_ondemand.PluginImpl$DescriptorImpl.doValidate(PluginImpl.java:137)
Note that HttpURLConnection is complaining rightly that the authentication string contains a newline. Credential.call has
String userpassword = username + ":" + key;
con.setRequestProperty("Authorization", "Basic " + new BASE64Encoder().encode(userpassword.getBytes()));
You can see that this will fail in some cases:
public class Demo {
public static void main(String... args) {
System.out.println("got: '" + new sun.misc.BASE64Encoder().encode(new String("someusername:apiKeyEtc01234567890123456789012345678901234").getBytes()) + "'");
}
}
produces
got: 'c29tZXVzZXJuYW1lOmFwaUtleUV0YzAxMjM0NTY3ODkwMTIzNDU2Nzg5MDEyMzQ1Njc4OTAxMjM0
'
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6947917 discusses a similar bug in the JRE, and suggests the workaround:
public class Demo {
public static void main(String... args) {
System.out.println("got: '" + new sun.misc.BASE64Encoder() {
@Override protected int bytesPerLine() {
return ;
}
}.encode(new String("someusername:apiKeyEtc01234567890123456789012345678901234").getBytes()) + "'");
}
}
producing
got: 'c29tZXVzZXJuYW1lOmFwaUtleUV0YzAxMjM0NTY3ODkwMTIzNDU2Nzg5MDEyMzQ1Njc4OTAxMjM0'
By the way https://github.com/infradna/saucerest-java/ seems to be the source of the REST API, but this appears long out of date whereas https://github.com/saucelabs/saucerest-java/ looks to be the authoritative library (which however still appears to suffer from this same bug, at least according to an inspection of sources).
Environment:
1.14
Project:
Jenkins
Priority:
Major
Reporter:
jglick
This message is automatically generated by JIRA.
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-14492) IAE Illegal character(s) in message header value from com.saucelabs.rest.Credential.call
jglick assigned JENKINS-14492 to Ross Rowe IAE Illegal character(s) in message header value from com.saucelabs.rest.Credential.call Change By: jglick (18/Jul/12 8:16 PM) Assignee: KohsukeKawaguchi RossRowe This message is automatically generated by JIRA. 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-9671) NODE_NAME not defined for master node
Slide-O-Mix commented on JENKINS-9671 NODE_NAME not defined for master node Looks like the way environment variables are gathered is now different with the new EnvironmentContributor. Though I am not sure why it would be missing, the same code as was used to set it from before has been moved to CoreEnvironmentContributor, so it should still be adding it. This message is automatically generated by JIRA. 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-9671) NODE_NAME not defined for master node
Slide-O-Mix commented on JENKINS-9671 NODE_NAME not defined for master node Also, I am using 1.465 and don't see this 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
[JIRA] (JENKINS-9336) Culprits Email List - Names Can be Dropped
Slide-O-Mix closed JENKINS-9336 as Duplicate Culprits Email List - Names Can be Dropped Duplicate of JENKINS-2244 Change By: Slide-O-Mix (18/Jul/12 9:13 PM) Status: Open Closed 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-14484) Define time period in which a mail is desired
Slide-O-Mix resolved JENKINS-14484 as Wont Fix Define time period in which a mail is desired Please implement using pre-send script. Change By: Slide-O-Mix (18/Jul/12 9:14 PM) Status: Open Resolved Resolution: WontFix This message is automatically generated by JIRA. 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-13192) groovy template meets error when there are git changes
SCM/JIRA link daemon commented on JENKINS-13192 groovy template meets error when there are git changes Code changed in jenkins User: slide Path: src/main/resources/hudson/plugins/emailext/templates/groovy-text.template http://jenkins-ci.org/commit/email-ext-plugin/86f5f9e91b839be3b944d9b4a2fd7ceb2c0dfe41 Log: Fix JENKINS-13192 for text template Fixed the author issue for the text template as well. This message is automatically generated by JIRA. 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-13295) Jenkins hangs for ~1 hour after posting 'Sending Email'
Slide-O-Mix commented on JENKINS-13295 Jenkins hangs for ~1 hour after posting Sending Email Please update with more info on the environment, e.g., plugins, scm and so forth. Also, if you can get a stack trace that would be helpful. This message is automatically generated by JIRA. 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-13102) Build hangs trying to send email if an email address isn't defined in Active Directory
Slide-O-Mix commented on JENKINS-13102 Build hangs trying to send email if an email address isnt defined in Active Directory What if you add the build user to the Jenkins user list and give it a valid email address? This should resolve 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
[JIRA] (JENKINS-14338) NPE when retrieving requester address for a promoted build
Slide-O-Mix resolved JENKINS-14338 as Incomplete NPE when retrieving requester address for a promoted build Change By: Slide-O-Mix (18/Jul/12 9:50 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
[JIRA] (JENKINS-13359) Blank email (subject+body) for Failure emails only
Slide-O-Mix resolved JENKINS-13359 as Incomplete Blank email (subject+body) for Failure emails only Change By: Slide-O-Mix (18/Jul/12 9:54 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
[JIRA] (JENKINS-10340) Email-ext plugin does not work with testng results(format)
Slide-O-Mix commented on JENKINS-10340 Email-ext plugin does not work with testng results(format) It looks like this would be easy if the testng plugin inherited from the AbstractTestResultAction. (http://javadoc.jenkins-ci.org/hudson/tasks/test/AbstractTestResultAction.html) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10340) Email-ext plugin does not work with testng results(format)
Slide-O-Mix resolved JENKINS-10340 as Wont Fix Email-ext plugin does not work with testng results(format) testng plugin needs to use the built-in way of reporting and associating test results with a build. http://javadoc.jenkins-ci.org/hudson/tasks/test/AbstractTestResultAction.html Change By: Slide-O-Mix (18/Jul/12 10:04 PM) Status: Open Resolved Resolution: WontFix This message is automatically generated by JIRA. 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-12797) Don't Keep this build forever button doesn't work on some matrix job and prevent removing old build
Lothar Werzinger commented on JENKINS-12797 Dont Keep this build forever button doesnt work on some matrix job and prevent removing old build I'm seeing the same 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
[JIRA] (JENKINS-12797) Don't Keep this build forever button doesn't work on some matrix job and prevent removing old build
Lothar Werzinger edited a comment on JENKINS-12797 Dont Keep this build forever button doesnt work on some matrix job and prevent removing old build I'm seeing the same issue (Jenkins ver. 1.474) This message is automatically generated by JIRA. 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-12797) Don't Keep this build forever button doesn't work on some matrix job and prevent removing old build
Lothar Werzinger edited a comment on JENKINS-12797 Dont Keep this build forever button doesnt work on some matrix job and prevent removing old build I'm seeing the same issue (Jenkins ver. 1.474) I have a 2x3 matrix with a touchstone build This message is automatically generated by JIRA. 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-7859) Email-ext trigger for the transition from success to failure
SCM/JIRA link daemon commented on JENKINS-7859 Email-ext trigger for the transition from success to failure Code changed in jenkins User: slide Path: src/main/java/hudson/plugins/emailext/EmailExtensionPlugin.java src/main/java/hudson/plugins/emailext/plugins/trigger/FirstFailureTrigger.java src/test/java/hudson/plugins/emailext/ExtendedEmailPublisherTest.java http://jenkins-ci.org/commit/email-ext-plugin/d072f821f5d545558cc5ddf17b68e1e23ad9d02d Log: Fix JENKINS-7859 Added FirstFailureTrigger.java to handle the case when a build moves from Success to Failure (or on first build run + Failure) This message is automatically generated by JIRA. 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-14016) Xcode codesign fails in Jenkins but works as user running Jenkins
Sami Tikka resolved JENKINS-14016 as Duplicate Xcode codesign fails in Jenkins but works as user running Jenkins Not a bug in Jenkins, more like a feature request. See the comments in the linked duplicate case. Change By: Sami Tikka (18/Jul/12 11:41 PM) Status: Open Resolved Fix Version/s: current 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-14492) IAE Illegal character(s) in message header value from com.saucelabs.rest.Credential.call
Ross Rowe started work on JENKINS-14492 IAE Illegal character(s) in message header value from com.saucelabs.rest.Credential.call Change By: Ross Rowe (19/Jul/12 12:06 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
[JIRA] (JENKINS-6703) Allow for selection of Cc:, Bcc: fields for email recipients on global recipient list
SCM/JIRA link daemon commented on JENKINS-6703 Allow for selection of Cc:, Bcc: fields for email recipients on global recipient list Code changed in jenkins User: slide Path: src/main/java/hudson/plugins/emailext/EmailRecepientUtils.java src/main/java/hudson/plugins/emailext/EmailRecipientUtils.java src/main/java/hudson/plugins/emailext/ExtendedEmailPublisher.java src/main/java/hudson/plugins/emailext/ExtendedEmailPublisherDescriptor.java src/test/java/hudson/plugins/emailext/EmailRecepientUtilsTest.java src/test/java/hudson/plugins/emailext/EmailRecipientUtilsTest.java http://jenkins-ci.org/commit/email-ext-plugin/4e7e05ad87e894814dd15c2516c1273bb384c2b4 Log: Fix JENKINS-6703 Email addresses can now be prepended with cc: to denote that the email should be sent to them as a CC Also fixed spelling of files and classes This message is automatically generated by JIRA. 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-6703) Allow for selection of Cc:, Bcc: fields for email recipients on global recipient list
Slide-O-Mix resolved JENKINS-6703 as Fixed Allow for selection of Cc:, Bcc: fields for email recipients on global recipient list Change By: Slide-O-Mix (19/Jul/12 12:25 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
[JIRA] (JENKINS-14494) Need to be able to use Flexible Publish in matrix job post-build actions
owenmehegan created JENKINS-14494 Need to be able to use Flexible Publish in matrix job post-build actions Issue Type: New Feature Affects Versions: current Assignee: bap Components: flexible-publish Created: 19/Jul/12 12:29 AM Description: I would love to be able to use this (and, by extension, Conditional Build Steps), in matrix job post-build actions. Please please!! Project: Jenkins Priority: Major Reporter: owenmehegan This message is automatically generated by JIRA. 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-13295) Jenkins hangs for ~1 hour after posting 'Sending Email'
crwong commented on JENKINS-13295 Jenkins hangs for ~1 hour after posting Sending Email We are using the Git plugin v1.1.20, and the ext-email plugin v2.22. It looks like the issue only happens when Jenkins attempts to determine the email address of someone who has checked in code for that build. We use Perforce and Git in our office. The Perforce users are forced to enter valid email addresses when their users are created. However, the Git users are not, and I have only seen this issue with the jobs that use Git. This message is automatically generated by JIRA. 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-13295) Jenkins hangs for ~1 hour after posting 'Sending Email'
Slide-O-Mix commented on JENKINS-13295 Jenkins hangs for ~1 hour after posting Sending Email If you could get a stack trace, that would be very helpful, I would like to see which address resolver is causing your 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-3430) Regression trigger, improvement trigger, a few small improvements (PATCH)
Slide-O-Mix resolved JENKINS-3430 as Incomplete Regression trigger, improvement trigger, a few small improvements (PATCH) Change By: Slide-O-Mix (19/Jul/12 1:40 AM) Status: Reopened 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
[JIRA] (JENKINS-14495) Exception: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.parameterizedtrigger.TriggerBuilder
Romu Hu
created JENKINS-14495
Exception: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.parameterizedtrigger.TriggerBuilder
Issue Type:
Bug
Assignee:
huybrechts
Components:
parameterized-trigger
Created:
19/Jul/12 3:19 AM
Description:
Whenever I add a build step "trigger/call builds on other projects" and click save, I get the following error:
Status Code: 500
Exception: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.parameterizedtrigger.TriggerBuilder from {"configs":{"block":true,"buildStepFailureThreshold":"FAILURE","failureThreshold":"FAILURE","projects":"SlaveJob1","unstableThreshold":"UNSTABLE"},"kind":"hudson.plugins.parameterizedtrigger.TriggerBuilder","stapler-class":"hudson.plugins.parameterizedtrigger.TriggerBuilder"}
Stacktrace:
javax.servlet.ServletException: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.parameterizedtrigger.TriggerBuilder from {"configs":{"block":true,"buildStepFailureThreshold":"FAILURE","failureThreshold":"FAILURE","projects":"SlaveJob1","unstableThreshold":"UNSTABLE"},"kind":"hudson.plugins.parameterizedtrigger.TriggerBuilder","stapler-class":"hudson.plugins.parameterizedtrigger.TriggerBuilder"}
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:616)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574)
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.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
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
