[JIRA] (JENKINS-17064) Unable to edit some build definitions
Andrzej Pasterczyk created JENKINS-17064 Unable to edit some build definitions Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: matrix Created: 05/Mar/13 8:00 AM Description: We've just upgraded to latest jenkins version + few plugin upgrades and now for some jobs it's not possible to edit them. Save button is missing and the gray "loading" panel stays forever. _javascript_ exception is logged in the console. Uncaught TypeError: Cannot call method 'hasClassName' of undefined hetero-list.js:16 (anonymous function) hetero-list.js:16 (anonymous function) behavior.js:111 (anonymous function) behavior.js:107 Behaviour.applySubtree behavior.js:93 Behaviour.apply behavior.js:76 (anonymous function) behavior.js:71 window.onload behavior.js:125 Also there's a HTTP500 error at the bottom of configuration page Status Code: 500 Exception: org.apache.commons.jelly.JellyTagException: jar:file:/C:/CI/Jenkins/war/WEB-INF/lib/jenkins-core-1.504.jar!/lib/form/hetero-list.jelly:119:94: st:include org.apache.commons.jelly.JellyTagException: jar:file:/C:/CI/Jenkins/war/WEB-INF/lib/jenkins-core-1.504.jar!/lib/form/entry.jelly:73:23: d:invokeBody Cannot get property 'description' on null object Stacktrace: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/C:/CI/Jenkins/war/WEB-INF/lib/jenkins-core-1.504.jar!/lib/form/hetero-list.jelly:119:94: st:include org.apache.commons.jelly.JellyTagException: jar:file:/C:/CI/Jenkins/war/WEB-INF/lib/jenkins-core-1.504.jar!/lib/form/entry.jelly:73:23: d:invokeBody Cannot get property 'description' on null object at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) 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:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487) at org.kohsuke.stapler.Stapler.service(Stapler.java:164) 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 com.marvelution.hudson.plugins.apiv2.servlet.filter.HudsonAPIV2ServletFilter.doFilter(HudsonAPIV2ServletFilter.java:115) 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:124) 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
[JIRA] (JENKINS-17064) Unable to edit some build definitions
Andrzej Pasterczyk
updated JENKINS-17064
Unable to edit some build definitions
Change By:
Andrzej Pasterczyk
(05/Mar/13 8:19 AM)
Assignee:
AlexEarl
Environment:
Jenkins1.504WindowsServer2008
email-extplugin2.27
Description:
Wevejustupgradedtolatestjenkinsversion+fewpluginupgradesandnowforsomejobsitsnotpossibletoeditthem.Savebuttonismissingandthegrayloadingpanelstaysforever._javascript_exceptionisloggedintheconsole.{noformat}UncaughtTypeError:CannotcallmethodhasClassNameofundefinedhetero-list.js:16(anonymousfunction)hetero-list.js:16(anonymousfunction)behavior.js:111(anonymousfunction)behavior.js:107Behaviour.applySubtreebehavior.js:93Behaviour.applybehavior.js:76(anonymousfunction)behavior.js:71window.onloadbehavior.js:125{noformat}AlsotheresaHTTP500erroratthebottomofconfigurationpage{noformat}StatusCode:500Exception:org.apache.commons.jelly.JellyTagException:jar:file:/C:/CI/Jenkins/war/WEB-INF/lib/jenkins-core-1.504.jar!/lib/form/hetero-list.jelly:119:94:st:includeorg.apache.commons.jelly.JellyTagException:jar:file:/C:/CI/Jenkins/war/WEB-INF/lib/jenkins-core-1.504.jar!/lib/form/entry.jelly:73:23:d:invokeBodyCannotgetpropertydescriptiononnullobjectStacktrace:javax.servlet.ServletException:org.apache.commons.jelly.JellyTagException:jar:file:/C:/CI/Jenkins/war/WEB-INF/lib/jenkins-core-1.504.jar!/lib/form/hetero-list.jelly:119:94:st:includeorg.apache.commons.jelly.JellyTagException:jar:file:/C:/CI/Jenkins/war/WEB-INF/lib/jenkins-core-1.504.jar!/lib/form/entry.jelly:73:23:d:invokeBodyCannotgetpropertydescriptiononnullobject atorg.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:658) atorg.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:658) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:487) atorg.kohsuke.stapler.Stapler.service(Stapler.java:164) atjavax.servlet.http.HttpServlet.service(HttpServlet.java:45) atwinstone.ServletConfiguration.execute(ServletConfiguration.java:248) atwinstone.RequestDispatcher.forward(RequestDispatcher.java:333) atwinstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) atcom.marvelution.hudson.plugins.apiv2.servlet.filter.HudsonAPIV2ServletFilter.doFilter(HudsonAPIV2ServletFilter.java:115) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) athudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) athudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) atwinstone.FilterConfiguration.execute(FilterConfiguration.java:194) atwinstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) athudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) atwinstone.FilterConfiguration.execute(FilterConfiguration.java:194) atwinstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) athudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
[JIRA] (JENKINS-16995) NullPointerException when viewing test results
Jarkko Palviainen updated JENKINS-16995 NullPointerException when viewing test results Change By: Jarkko Palviainen (05/Mar/13 8:21 AM) Environment: $uname-a2.6.32-42-server#95- Ubuntu SMPWedJul2516: 10 :49UTC2012x86_64GNU/Linux$java-versionjavaversion1 . 6.0_24OpenJDKRuntimeEnvironment(IcedTea61.11.3)(6b24-1.11.3-1ubuntu0.10. 04. 4LTS64bit 1)OpenJDK64-BitServerVM(build20.0-b12,mixedmode) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17064) Unable to edit some build definitions
Andrzej Pasterczyk commented on JENKINS-17064 Unable to edit some build definitions Reverting to 2.25 seems to fix the issue. However now it gives a warning about incompatible data in job definitions on Jenkins management screen MissingFieldException: No field 'compressBuildLog' found in class 'hudson.plugins.emailext.EmailType', MissingFieldException: No field 'compressBuildLog' found in class 'hudson.plugins.emailext.EmailType', MissingFieldException: No field 'compressBuildLog' found in class 'hudson.plugins.emailext.EmailType', MissingFieldException: No field 'compressBuildLog' found in class 'hudson.plugins.emailext.EmailType', MissingFieldException: No field 'compressBuildLog' found in class 'hudson.plugins.emailext.EmailType', MissingFieldException: No field 'compressBuildLog' found in class 'hudson.plugins.emailext.ExtendedEmailPublisher' This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17049) Xvnc -localhost -nolisten tcp should be configurable
Federico Fissore commented on JENKINS-17049 Xvnc -localhost -nolisten tcp should be configurable If for "screenshots" you intend "videos" then it answers my needs but introduces an overhead that may no be acceptable. In my case I needed to see the application running because the glitch that caused the build to fail showed just for a moment. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16824) Builds aborting randomly
Ari Hyttinen updated JENKINS-16824 Builds aborting randomly Debug/troubleshooting patch on top of Remoting-2.17, modifying Request.java file. Change By: Ari Hyttinen (05/Mar/13 8:36 AM) Attachment: Request.java.patch This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16824) Builds aborting randomly
Ari Hyttinen edited a comment on JENKINS-16824 Builds aborting randomly I attached debug/troubleshooting patch on top of Remoting-2.17, modifying Request.java file, to this ticket. We have had this in use for a week now, without problems. I created it for debugging/troubleshooting purposes, which is why it is kind of messy. For us, it seems to stop the problem from occuring, based on log output. And by that I mean, the (apparently) spurious InterruptedExceptions, which aborted builds in a bad way, no longer happen at all, while other presumably normal InterruptedExceptions do get logged... So this might be some kind of timing/race condition issue, where changing the code will change the behavior and hide the bug. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16824) Builds aborting randomly
Ari Hyttinen edited a comment on JENKINS-16824 Builds aborting randomly I attached debug/troubleshooting patch on top of Remoting-2.17, modifying Request.java file, to this ticket. We have had this in use for a week now, without problems. I created it for debugging/troubleshooting purposes, which is why it is kind of messy. For us, it seems to stop the problem from occuring, based on log output. And by that I mean, the (apparently) spurious InterruptedExceptions, which aborted builds in a bad way, no longer happen at all, while other presumably normal InterruptedExceptions do get logged... So this might be some kind of timing/race condition issue, where changing the code will change the behavior and hide the bug. This is also why I attached the messy patch as-is, since cleaning it up might bring the problem out again. But we're not going to test that in our production system as long as problem stays away... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17065) Exception is appeared in the jenkins log when UI trying to show build history for redeploy builds
Vladimir Kravets created JENKINS-17065 Exception is appeared in the jenkins log when UI trying to show build history for redeploy builds Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: jenkins.log Components: maven Created: 05/Mar/13 8:52 AM Description: Exception is appeared in the jenkins log when UI trying to show build history for redeploy builds See detail log in the attached file. Project: Jenkins Labels: maven redeploy Priority: Major Reporter: Vladimir Kravets This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16824) Builds aborting randomly
Ari Hyttinen commented on JENKINS-16824 Builds aborting randomly Rough how-to for those willing to try the attached patch, who are not familiar with building the jar: 0. have JDK, maven (I used maven 2, not sure if maven 3 works too) and (optionally) git properly installed 1. Get sources from https://github.com/jenkinsci/remoting/tree/remoting-2.17 2. Apply the patch 3. Build (mvn package) to get your custom remoting-2.17.jar 4. Stop Jenkins 5. To use this on Master (which is where problem occurs), go to folder ...jenkins/war/WEB-INF/lib, and replace existing remoting*.jar with the one you built 6. Optionally, to use this also on slaves where Jenkins copies the .jar file to slave, go to folder ...jenkins/war/WEB-INF, and replace existing remoting.jar and slave.jar with the one you built. 7. Restart Jenkins, look at log files, search for "interrupthack" string to find out stuff logged by the patch. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16824) Builds aborting randomly
Ari Hyttinen edited a comment on JENKINS-16824 Builds aborting randomly A rough, untested how-to for those willing to try the attached patch, who are not familiar with building the jar: 0. have a JDK, maven (I used maven 2, not sure if maven 3 works too) and (optionally) git properly installed 1. Get sources from https://github.com/jenkinsci/remoting/tree/remoting-2.17 2. Apply the patch 3. Build (mvn package) to get your custom remoting-2.17.jar 4. Stop Jenkins 5. To use this on Master (which is where problem occurs), go to folder ...jenkins/war/WEB-INF/lib, and replace existing remoting*.jar with the one you built 6. Optionally, to use this also on slaves where Jenkins copies the .jar file to slave, go to folder ...jenkins/war/WEB-INF, and replace existing remoting.jar and slave.jar with the one you built. 7. Restart Jenkins, look at log files, search for "interrupthack" string to find stuff logged by the patch. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16824) Builds aborting randomly
kutzi commented on JENKINS-16824 Builds aborting randomly Ari can you create a Github pull request with your changes? That would make commenting on the changes and integrating them much easier. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17003) JNLP Slave on Windows Server 2012 will not reconnect to master after network disconnect/reconnect
Linards L assigned JENKINS-17003 to Linards L JNLP Slave on Windows Server 2012 will not reconnect to master after network disconnect/reconnect Change By: Linards L (05/Mar/13 10:00 AM) Assignee: LinardsL This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17003) JNLP Slave on Windows Server 2012 will not reconnect to master after network disconnect/reconnect
Linards L commented on JENKINS-17003 JNLP Slave on Windows Server 2012 will not reconnect to master after network disconnect/reconnect Jenkins v1.502 , created slave, using as windows service - v1.504 , slave working correctly after upgrade. Now crossing fingers that upgrade from v1.494 will also result in working slave. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15596) Jenkins will not start as a Windows Service after KB2661254
Linards L commented on JENKINS-15596 Jenkins will not start as a Windows Service after KB2661254 Not affected by this issue on my win 2k8 r2 x64 sp1 machine though even after upgrade from v1.502 to v1.504 with having this KB2661254 installed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15596) Jenkins will not start as a Windows Service after KB2661254
Linards L edited a comment on JENKINS-15596 Jenkins will not start as a Windows Service after KB2661254 Not affected by this issue on my win 2k8 r2 x64 sp1 (jdk7) machine though even after upgrade from v1.502 to v1.504 with having this KB2661254 installed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17065) Exception is appeared in the jenkins log when UI trying to show build history for redeploy builds
Vladimir Kravets updated JENKINS-17065 Exception is appeared in the jenkins log when UI trying to show build history for redeploy builds Change By: Vladimir Kravets (05/Mar/13 10:38 AM) Description: ExceptionisappearedinthejenkinslogwhenUItryingtoshowbuildhistoryforredeploybuilds . Stepstoreproduce:1.Openredeploypage.2.Runredeploy(ClickOkbutton)3.Waitingwhenbuildisapparedinthebuildhistory(makesurethatpagewasntreloaded)=4.ExceptionisthrowninthejenkinsconsolePleasenotethattokenwhichcannottransformtointegerhavevaluebuildHistory Seedetaillogintheattachedfile. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16689) Jenkins complains about unauthorized SVN URL, but actually can access it, since IT IS authorized
Linards L commented on JENKINS-16689 Jenkins complains about unauthorized SVN URL, but actually can access it, since IT IS authorized Same here. Digget out all available logs in centos 5.6 but only trace found that svn auth through AD and LDAP was failing for some users. Fixed it by reverting to plugin version 1.44. I highly DO NOT RECOMMEND ANYONE to use version 1.45. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16689) Jenkins complains about unauthorized SVN URL, but actually can access it, since IT IS authorized
Linards L edited a comment on JENKINS-16689 Jenkins complains about unauthorized SVN URL, but actually can access it, since IT IS authorized Same here. Digget out all available logs in centos 5.6 but only trace found that svn auth through AD and LDAP was failing for some users. Fixed it by reverting to plugin version 1.44. I highly DO NOT RECOMMEND ANYONE to use version 1.45. Affecting Jenkins v1.494 @ jdk7 , win 2k8 r2 x64 sp1 datacenter. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16689) Jenkins complains about unauthorized SVN URL, but actually can access it, since IT IS authorized
Linards L edited a comment on JENKINS-16689 Jenkins complains about unauthorized SVN URL, but actually can access it, since IT IS authorized Same here. Digget out all available logs in centos 5.6 but only trace found that svn auth through AD and LDAP was failing for some users. Fixed it by reverting to plugin version 1.44. I highly DO NOT RECOMMEND ANYONE to use version 1.45. Affecting Jenkins v1.494 installation @ jdk7 , tomcat7 , win 2k8 r2 x64 sp1 datacenter. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14062) can we zip ALL the backups and not just the 'old' ones?
Ferreira Olivier commented on JENKINS-14062 can we zip ALL the backups and not just the old ones? I had to create a job and execute a script with groovy to do this. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17064) Unable to edit some build definitions
Alex Earl commented on JENKINS-17064 Unable to edit some build definitions Can you determine the difference between the items that you can and can't edit? What is the difference? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17064) Unable to edit some build definitions
Dirk Kuypers commented on JENKINS-17064 Unable to edit some build definitions I have the same problem. When trying to change job configuration the page stays in the "Loading" stage with grey upper part. When scrolling down the last field to configure is the email-ext section, post-build events I know of running later like groovy-postbuild are not visible. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17064) Unable to edit some build definitions
Andrzej Pasterczyk
commented on JENKINS-17064
Unable to edit some build definitions
I was not able to edit anything that had email-ext plugin used inside job definition.
Here's how it looks like in one of the builds
publishers
hudson.tasks.ArtifactArchiver
artifacts*.html,*.txt/artifacts
latestOnlyfalse/latestOnly
/hudson.tasks.ArtifactArchiver
hudson.plugins.nunit.NUnitPublisher plugin="nunit@0.14"
testResultsPattern*_nunit.xml/testResultsPattern
debugfalse/debug
keepJUnitReportsfalse/keepJUnitReports
skipJUnitArchiverfalse/skipJUnitArchiver
/hudson.plugins.nunit.NUnitPublisher
hudson.plugins.emailext.ExtendedEmailPublisher plugin="email-ext@2.27"
recipientList$DEFAULT_RECIPIENTS,${ENV, var=quot;RECEPIENTSquot;}/recipientList
configuredTriggers
hudson.plugins.emailext.plugins.trigger.UnstableTrigger
email
recipientList/recipientList
subject$PROJECT_DEFAULT_SUBJECT/subject
body$PROJECT_DEFAULT_CONTENT/body
sendToDeveloperstrue/sendToDevelopers
sendToRequesterfalse/sendToRequester
includeCulpritsfalse/includeCulprits
sendToRecipientListtrue/sendToRecipientList
attachmentsPattern/attachmentsPattern
attachBuildLogfalse/attachBuildLog
compressBuildLogfalse/compressBuildLog
replyTo/replyTo
/email
/hudson.plugins.emailext.plugins.trigger.UnstableTrigger
hudson.plugins.emailext.plugins.trigger.FailureTrigger
email
recipientList/recipientList
subject$PROJECT_DEFAULT_SUBJECT/subject
body$PROJECT_DEFAULT_CONTENT/body
sendToDeveloperstrue/sendToDevelopers
sendToRequesterfalse/sendToRequester
includeCulpritsfalse/includeCulprits
sendToRecipientListtrue/sendToRecipientList
attachmentsPattern/attachmentsPattern
attachBuildLogfalse/attachBuildLog
compressBuildLogfalse/compressBuildLog
replyTo/replyTo
/email
/hudson.plugins.emailext.plugins.trigger.FailureTrigger
hudson.plugins.emailext.plugins.trigger.FixedTrigger
email
recipientList/recipientList
subject$PROJECT_DEFAULT_SUBJECT/subject
body$PROJECT_DEFAULT_CONTENT/body
sendToDeveloperstrue/sendToDevelopers
sendToRequesterfalse/sendToRequester
includeCulpritsfalse/includeCulprits
sendToRecipientListtrue/sendToRecipientList
attachmentsPattern/attachmentsPattern
attachBuildLogfalse/attachBuildLog
compressBuildLogfalse/compressBuildLog
replyTo/replyTo
/email
/hudson.plugins.emailext.plugins.trigger.FixedTrigger
/configuredTriggers
contentTypedefault/contentType
defaultSubject$DEFAULT_SUBJECT/defaultSubject
defaultContent$DEFAULT_CONTENT/defaultContent
attachmentsPattern/attachmentsPattern
presendScript/presendScript
attachBuildLogfalse/attachBuildLog
compressBuildLogfalse/compressBuildLog
replyTo$DEFAULT_RECIPIENTS/replyTo
matrixTriggerModeONLY_CONFIGURATIONS/matrixTriggerMode
/hudson.plugins.emailext.ExtendedEmailPublisher
/publishers
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17064) Unable to edit some build definitions
Alex Earl commented on JENKINS-17064 Unable to edit some build definitions @Dirk, anything special about your jobs? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17064) Unable to edit some build definitions
Dirk Kuypers commented on JENKINS-17064 Unable to edit some build definitions Do you have something particular in mind despite using email-ext plugin? I am using a lot of Jenkins stuff in terms of different plugins but the error applies to different kinds of jobs I have: compile jobs, test jobs, installer build jobs. Platform is Windows 7 64 bit, Java 7, Jenkins (1.504) and all plugins latest. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14062) can we zip ALL the backups and not just the 'old' ones?
Ferreira Olivier edited a comment on JENKINS-14062 can we zip ALL the backups and not just the old ones? I had to create a job and execute a script with groovy to do this.. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17064) Unable to edit some build definitions
Alex Earl commented on JENKINS-17064 Unable to edit some build definitions Are they matrix jobs? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17064) Unable to edit some build definitions
Dirk Kuypers commented on JENKINS-17064 Unable to edit some build definitions No, definetely not. I was not really successful in setting up matrix jobs, instead I am creating our nightly test jobs via groovy scripts. But the job configurations failing I mentioned earlier are not generated at all, they have been hand-crafted. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17064) Unable to edit some build definitions
Alex Earl commented on JENKINS-17064 Unable to edit some build definitions Can you post the exception you are getting and your job.xml for the failing jobs (scrubbed of corporate info of course) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17064) Unable to edit some build definitions
Dirk Kuypers edited a comment on JENKINS-17064 Unable to edit some build definitions No, definitely not. I was not really successful in setting up matrix jobs, instead I am creating our nightly test jobs via groovy scripts. But the job configurations failing I mentioned earlier are not generated at all, they have been hand-crafted. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16863) After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable
Alex Earl commented on JENKINS-16863 After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable Probably need to make sure that the Mailer plugin is installed and enabled. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17064) Unable to edit some build definitions
Dirk Kuypers commented on JENKINS-17064 Unable to edit some build definitions OK, here is the exception (Job will follow): WARNING: Untrapped servlet exception javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/D:/Jenkins/war/WEB-INF/lib/jenkins-core-1.504.jar!/lib/form/hetero-list.jelly:119:94: st:include org.apache.commons.jelly.JellyTagException: jar:file:/D:/Jenkins/war/WEB-INF/lib/jenkins-core-1.504.jar!/lib/form/advanced.jelly:52:23: d:invokeBody java.lang.StackOverflowError at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) 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:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487) at org.kohsuke.stapler.Stapler.service(Stapler.java:164) 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:206) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:179) 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:124) 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:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) 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
[JIRA] (JENKINS-17064) Unable to edit some build definitions
Alex Earl commented on JENKINS-17064 Unable to edit some build definitions @Dirk, if you drop back to email-ext-2.25, does your issue go away? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17064) Unable to edit some build definitions
Dirk Kuypers commented on JENKINS-17064 Unable to edit some build definitions At the moment I can not restart. But Andrzej said that downgrading helped. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16361) @Grab Grape support
Daniel Spilker commented on JENKINS-16361 @Grab Grape support When adding Ivy to the plugin without using "Mask-Classes", the exception is the same as without Ivy. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17066) Unrealized exception is there while executing QTP Test Cases through HP ALM Plugin
Jeebitesh Kalantri created JENKINS-17066 Unrealized exception is there while executing QTP Test Cases through HP ALM Plugin Issue Type: Bug Affects Versions: current Assignee: Ofir Shaked Components: hp-application-automation-tools-plugin Created: 05/Mar/13 1:37 PM Description: 05/03/2013 08:12:12 Running test: 1ConfigTest, Test id: 89659, Test instance id: 101041 Test: 1ConfigTest, Id: 101041, Execution status: Running Test: 1ConfigTest, Id: 101041, Execution status: Passed, Message: Passed Step: Test iteration 1, Status: PassedException while reading step data: Object reference not set to an instance of an object. Due Date: 27/Mar/13 12:00 AM Project: Jenkins Labels: plugin Priority: Trivial Reporter: Jeebitesh Kalantri This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17067) Finding the correct delivering Stream to cancel
Christian Wolfgang created JENKINS-17067 Finding the correct delivering Stream to cancel Issue Type: Improvement Assignee: Praqma Support Components: clearcase-ucm Created: 05/Mar/13 1:38 PM Description: It is not always the correct stream, that is found when force cancel deliver. Project: Jenkins Priority: Major Reporter: Christian Wolfgang This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16974) Build Now link on MultiJob page doesn't work
C. S. commented on JENKINS-16974 Build Now link on MultiJob page doesnt work Same problem with stopping the 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-12935) Allow plugin to specify region to run CloudFormation script in
Marcin Kulisz commented on JENKINS-12935 Allow plugin to specify region to run CloudFormation script in Thx a lot for this, it's working like a charm. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17064) Unable to edit some build definitions
Krzysztof Malinowski commented on JENKINS-17064 Unable to edit some build definitions Same issue here. Running Jenkins 1.504 on RHEL5 x86_64, with email-ext 1.27. It seems however that it is only triggered in Matrix builds and the stacktrace is a little bit different: Content Token Reference Help for feature: Content Token Reference Trigger for matrix projects Status Code: 500 Exception: org.apache.commons.jelly.JellyTagException: jar:file:/jenkins/jenkins_home/war/WEB-INF/lib/jenkins-core-1.504.jar!/lib/form/hetero-list.jelly:119:94: st:include org.apache.commons.jelly.JellyTagException: jar:file:/jenkins/jenkins_home/war/WEB-INF/lib/jenkins-core-1.504.jar!/lib/form/entry.jelly:73:23: d:invokeBody Cannot get property 'description' on null object Stacktrace: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/jenkins/jenkins_home/war/WEB-INF/lib/jenkins-core-1.504.jar!/lib/form/hetero-list.jelly:119:94: st:include org.apache.commons.jelly.JellyTagException: jar:file:/jenkins/jenkins_home/war/WEB-INF/lib/jenkins-core-1.504.jar!/lib/form/entry.jelly:73:23: d:invokeBody Cannot get property 'description' on null object at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) 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:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) 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:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487) at org.kohsuke.stapler.Stapler.service(Stapler.java:164) at javax.servlet.http.HttpServlet.service(HttpServlet.java:50) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:102) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) 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:126) 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:272) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:175) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:65) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:82) at
[JIRA] (JENKINS-17069) Can't reset job view
C. S. created JENKINS-17069 Cant reset job view Issue Type: Bug Assignee: Unassigned Attachments: sort.png, sortDefault.png Components: jenkins-multijob-plugin Created: 05/Mar/13 2:52 PM Description: After using the sort by job name, I can't reset the sort order/getting back to the default (see screenshots). Project: Jenkins Priority: Major Reporter: C. S. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17069) Can't reset job view
C. S. resolved JENKINS-17069 as Duplicate Cant reset job view Change By: C. S. (05/Mar/13 2:55 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17070) Missing times with multiconfiguration projects
C. S. created JENKINS-17070 Missing times with multiconfiguration projects Issue Type: Bug Assignee: Unassigned Attachments: timesMissing.png Components: jenkins-multijob-plugin Created: 05/Mar/13 3:07 PM Project: Jenkins Priority: Major Reporter: C. S. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17071) Support for multiconfiguration projects
C. S. created JENKINS-17071 Support for multiconfiguration projects Issue Type: New Feature Assignee: Unassigned Components: jenkins-multijob-plugin Created: 05/Mar/13 3:11 PM Description: It seems that the plugin doesn't really support multiconfiguration projects. I have some and want to archive artifacts over all instances. The only way at the moment is to have a checkout and archive job at the beginning and at the end. Project: Jenkins Priority: Major Reporter: C. S. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-6744) Need Good Run parameter
Geoff Cummings commented on JENKINS-6744 Need Good Run parameter I have had a go at adding filtering based on Build result, this will also allow you to filter out jobs which have not completed yet. I am new at this so all feedback welcome!! https://github.com/jenkinsci/jenkins/pull/728 thanks Geoff This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-7280) run parameters show builds that have not completed or have failed / unstable
Geoff Cummings commented on JENKINS-7280 run parameters show builds that have not completed or have failed / unstable I have had a go at adding filtering based on Build result, this will also allow you to filter out jobs which have not completed yet. I am new at this so all feedback welcome!! https://github.com/jenkinsci/jenkins/pull/728 thanks Geoff This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17072) Link to sonar not updated after update of projectid and artifactid in pom.xml
Henrik Nilsson created JENKINS-17072 Link to sonar not updated after update of projectid and artifactid in pom.xml Issue Type: Bug Affects Versions: current Assignee: Sonar Team Components: sonar Created: 05/Mar/13 3:27 PM Description: The link to sonar in a build job is not updated when the groupid artifactid is updated in the pom of the project. Even if the build job is deleted and recreated using the same name the projectKey part of the link will first be based on the new groupid:artifactid values but it will be replaced with the old link after a build. Same behaviour if a new build job is created and then renamed to the same name as the previously deleted build job. Same behavior even if the projectKey is set to the new grouid:artifactid in the post-build actions – Sonar - advanced - Additional properties field. Due Date: 31/Mar/13 12:00 AM Project: Jenkins Labels: Plugins Priority: Minor Reporter: Henrik Nilsson This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17073) Support specifying logger for phing
Alexander Obuhovich updated JENKINS-17073 Support specifying logger for phing Change By: Alexander Obuhovich (05/Mar/13 3:32 PM) Priority: Major Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17073) Support specifying logger for phing
Alexander Obuhovich created JENKINS-17073 Support specifying logger for phing Issue Type: Improvement Affects Versions: current Assignee: sogabe Components: phing Created: 05/Mar/13 3:32 PM Description: Right now in Phing plugin for Jenkins DefaultLogger is hardcoded. This logger doesn't support Ansi Colors. I'm proposing one of 2 things (which one can be implemented): allow to specify phing logger parameter in project configuration automatically set logger to AnsiLogger in case, when "AnsiColor Plugin" is installed and ANSI colors option is enabled in a project Project: Jenkins Priority: Major Reporter: Alexander Obuhovich This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17055) Git 1.2: only one remote is actually added
Fredric Lonngren commented on JENKINS-17055 Git 1.2: only one remote is actually added I have the same issue using two remote repos. First one works, second fails. Both are using ssh. Works with 1.1.26: Building in workspace /local/hudson-build/workspace/TCM_Builds_beta Checkout:TCM_Builds_beta / /local/hudson-build/workspace/TCM_Builds_beta - hudson.remoting.LocalChannel@1d0540c Using strategy: Default Last Built Revision: Revision 900242706776d7f77f28da58bc33d0a88fd3d764 (origin/foo_dev) Fetching changes from [org.eclipse.jgit.transport.RemoteConfig@35cf9c, org.eclipse.jgit.transport.RemoteConfig@d1258b] remote Git repositories Fetching upstream changes from ssh://iptcm-git.epk.ericsson.se:29418/foo-bar-dev/bar-team Fetching upstream changes from ssh://iptcm-git.epk.ericsson.se:29418/tcm/builds Seen branch in repository origin/HEAD Not working with 1.2.0 Building in workspace /local/hudson-build/workspace/TCM_Builds_beta Checkout:TCM_Builds_beta / /local/hudson-build/workspace/TCM_Builds_beta - hudson.remoting.LocalChannel@d53153 Using strategy: Default Last Built Revision: Revision e55cce57f3e954e5e554014f0ba64fa45ed70acb (origin/foo_dev) Fetching changes from 2 remote Git repositories Fetching upstream changes from origin Fetching upstream changes from tcm_repo ERROR: Problem fetching from tcm_repo / tcm_repo - could be unavailable. Continuing anyway hudson.plugins.git.GitException: Command "git fetch -t tcm_repo +refs/heads/*:refs/remotes/tcm_repo/*" returned status code 128: stdout: stderr: fatal: 'tcm_repo' does not appear to be a git repository fatal: Could not read from remote repository. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17055) Git 1.2: only one remote is actually added
Fredric Lonngren edited a comment on JENKINS-17055 Git 1.2: only one remote is actually added I have the same issue using two remote repos. First one works, second fails. Both are using ssh. Works with 1.1.26: Building in workspace /local/hudson-build/workspace/TCM_Builds_beta Checkout:TCM_Builds_beta / /local/hudson-build/workspace/TCM_Builds_beta - hudson.remoting.LocalChannel@1d0540c Using strategy: Default Last Built Revision: Revision 900242706776d7f77f28da58bc33d0a88fd3d764 (origin/foo_dev) Fetching changes from [org.eclipse.jgit.transport.RemoteConfig@35cf9c, org.eclipse.jgit.transport.RemoteConfig@d1258b] remote Git repositories Fetching upstream changes from ssh://iptcm-git.epk.ericsson.se:29418/foo-bar-dev/bar-team Fetching upstream changes from ssh://iptcm-git.epk.ericsson.se:29418/tcm/builds Seen branch in repository origin/HEAD Not working with 1.2.0 Building in workspace /local/hudson-build/workspace/TCM_Builds_beta Checkout:TCM_Builds_beta / /local/hudson-build/workspace/TCM_Builds_beta - hudson.remoting.LocalChannel@d53153 Using strategy: Default Last Built Revision: Revision e55cce57f3e954e5e554014f0ba64fa45ed70acb (origin/foo_dev) Fetching changes from 2 remote Git repositories Fetching upstream changes from origin Fetching upstream changes from tcm_repo ERROR: Problem fetching from tcm_repo / tcm_repo - could be unavailable. Continuing anyway hudson.plugins.git.GitException: Command "git fetch -t tcm_repo +refs/heads/*:refs/remotes/tcm_repo/*" returned status code 128: stdout: stderr: fatal: 'tcm_repo' does not appear to be a git repository fatal: Could not read from remote repository. Back on 1.1.26 for now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17055) Git 1.2: only one remote is actually added
Fredric Lonngren edited a comment on JENKINS-17055 Git 1.2: only one remote is actually added I have the same issue using two remote repos. First one works, second fails. Both are using ssh. Works with 1.1.26: Building in workspace /local/hudson-build/workspace/TCM_Builds_beta Checkout:TCM_Builds_beta / /local/hudson-build/workspace/TCM_Builds_beta - hudson.remoting.LocalChannel@1d0540c Using strategy: Default Last Built Revision: Revision 900242706776d7f77f28da58bc33d0a88fd3d764 (origin/foo_dev) Fetching changes from [org.eclipse.jgit.transport.RemoteConfig@35cf9c, org.eclipse.jgit.transport.RemoteConfig@d1258b] remote Git repositories Fetching upstream changes from ssh://iptcm-git.epk.ericsson.se:29418/foo-bar-dev/bar-team Fetching upstream changes from ssh://iptcm-git.epk.ericsson.se:29418/tcm/builds Seen branch in repository origin/HEAD Not working with 1.2.0 Building in workspace /local/hudson-build/workspace/TCM_Builds_beta Checkout:TCM_Builds_beta / /local/hudson-build/workspace/TCM_Builds_beta - hudson.remoting.LocalChannel@d53153 Using strategy: Default Last Built Revision: Revision e55cce57f3e954e5e554014f0ba64fa45ed70acb (origin/foo_dev) Fetching changes from 2 remote Git repositories Fetching upstream changes from origin Fetching upstream changes from tcm_repo ERROR: Problem fetching from tcm_repo / tcm_repo - could be unavailable. Continuing anyway hudson.plugins.git.GitException: Command "git fetch -t tcm_repo +refs/heads/*:refs/remotes/tcm_repo/*" returned status code 128: stdout: stderr: fatal: 'tcm_repo' does not appear to be a git repository fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:772) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:738) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.fetch(CliGitAPIImpl.java:159) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1023) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:941) at hudson.FilePath.act(FilePath.java:865) at hudson.FilePath.act(FilePath.java:838) at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:941) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1113) and-so-on Back on 1.1.26 for now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16990) unable to resolve class hudson.maven.reporters.SurefireAggregatedReport in groovy template
Josh Unger commented on JENKINS-16990 unable to resolve class hudson.maven.reporters.SurefireAggregatedReport in groovy template Thanks, I was going to ask... how one might use Joda Time... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17074) ImprovementTrigger doesn't trigger when a build improves all the way to having 0 test failures
Josh Unger created JENKINS-17074 ImprovementTrigger doesnt trigger when a build improves all the way to having 0 test failures Issue Type: Bug Assignee: Alex Earl Components: email-ext Created: 05/Mar/13 3:54 PM Description: According to the trigger help, the improvement trigger will send an email "... any time there is an improvement. A build is considered to have improved wheneverit has fewer failures than the previous build." When a build improves all the way to having 0 test failures, this trigger is not triggered. I looked at the code and the ImprovementTrigger is using number of current failures 0 (numCurrFailures 0) as part of the criteria if the trigger should run. However, this condition matches the help text. Can the code be fixed? Or, the help text could be changed, but I'd prefer fixing the code so that this trigger produces the similar "back to stable" email messages. Thanks. Project: Jenkins Priority: Major Reporter: Josh Unger This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17074) ImprovementTrigger doesn't trigger when a build improves all the way to having 0 test failures
Josh Unger updated JENKINS-17074 ImprovementTrigger doesnt trigger when a build improves all the way to having 0 test failures Change By: Josh Unger (05/Mar/13 3:57 PM) Description: Accordingtothetriggerhelp,theimprovementtriggerwillsendanemail...anytimethereisanimprovement.Abuildisconsideredtohaveimprovedwheneverithasfewerfailuresthanthepreviousbuild.Whenabuildimprovesallthewaytohaving0testfailures,thistriggerisnottriggered.IlookedatthecodeandtheImprovementTriggerisusingnumberofcurrentfailures0(numCurrFailures0)aspartofthecriteriaifthetriggershouldrun.However,thisconditionmatchesthehelptext.Canthecodebefixed?Or,thehelptextcouldbechanged,butIdpreferfixingthecodesothatthistriggerproducesthesimilarbacktostableemailmessages.Thanks. EDIT:IseethatthereisaFixedtrigger,somaybejusttweakthehelptext? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17075) Warnings Plugin Wind River Diab Compiler (C/C++)-parser is missing support for fatal errors
Stefan Landström created JENKINS-17075 Warnings Plugin Wind River Diab Compiler (C/C++)-parser is missing support for fatal errors Issue Type: Bug Assignee: Ulli Hafner Components: warnings Created: 05/Mar/13 4:06 PM Description: Given an existing job with a "Wind River Diab Compiler (C/C++)"-parser and the "Run always" option enabled, when the build produces a fatal warning, then I want it included in the results from the plugin. Below is an example of the output of a division by zero warning with the different supported severity levels. (based of Wind Rivier Diab Combiler User's Guide, B.3.6 "-e, Change diagnostic severity level") i, Information, equivalent to ignore. -ei1025 w, Warning. -ew1025 "main.c", line 5: warning (dcc:1025): division by zero e, Error (continue compilation). -ee1025 "main.c", line 5: error (dcc:1025): division by zero f, Fatal error (terminate immediately). -ef1025 "main.c", line 5: fatal error (dcc:1025): division by zero Also, if it can have a positive effect on the performance - some of the \s* in the parser's regex could be removed/changed to a fixed space based off the format examples above. Environment: Jenkins LTS 1.480.3 Static Analysis Utilities 1.49 Warnings Plug-in 4.23 Project: Jenkins Priority: Major Reporter: Stefan Landström This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17076) Poll SCM brings up a window complaining about submitting a POST
Peter Nordquist created JENKINS-17076 Poll SCM brings up a window complaining about submitting a POST Issue Type: Bug Assignee: jieryn Components: job-poll-action Created: 05/Mar/13 4:13 PM Description: When I click the Poll SCM link for a job it brings up a window complaining about not using a HTTP POST. You must use POST method to trigger builds. (From scripts you may instead pass a per-project authentication token, or authenticate with your API token.) If you see this page, it may be because a plugin offered a GET link; file a bug report for that plugin. Environment: Jenkins 1.502 Job Poll Action Plugin 1.0 Windows Server 2008 R2 Project: Jenkins Priority: Major Reporter: Peter Nordquist This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17076) Poll SCM brings up a window complaining about submitting a POST
Peter Nordquist updated JENKINS-17076 Poll SCM brings up a window complaining about submitting a POST Change By: Peter Nordquist (05/Mar/13 4:14 PM) Description: WhenIclickthePollSCMlinkforajobitbringsupawindowcomplainingaboutnotusingaHTTPPOST. Themessageisbelow. YoumustusePOSTmethodtotriggerbuilds.(Fromscriptsyoumayinsteadpassaper-projectauthenticationtoken,orauthenticatewithyourAPItoken.)Ifyouseethispage,itmaybebecauseapluginofferedaGETlink;fileabugreportforthatplugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17077) Potential Security Violation of using Jenkins as a Service
kirankumar konduri created JENKINS-17077 Potential Security Violation of using Jenkins as a Service Issue Type: Task Assignee: Unassigned Components: security Created: 05/Mar/13 4:15 PM Description: Frds, I installed Jenkins on a server and using for builds and deployments as a service. One of a team member raised his concern about security violation.(copied his email below). Does Jenkins really transmit the data to out side of the network.? Is Jenkins Reliable in terms of Security policies.? Can any one mention the standard clients who are using Jenkins.? What is the purpose of the below line.? “CloudBees reserves the right to access any or all Your accounts...” Please i need more information on this to prove Jenkins is a safe tool to use for builds and deployments. "Email send by one of our team member" Has this software been approved by the IT Standards group? I took a quick look at the CloudBees TERMS of SERVICE: http://www.cloudbees.com/company-TOS.cb In order to download the free version of this software, Then Someone agreed to this TOS. Some highlights: “CloudBees reserves the right to access any or all Your accounts...” “You understand that the technical processing and transmission of the Service, including Your content, may be transferred unencrypted and involve (a) transmissions over various networks...” “YOU ACKNOWLEDGE THAT CLOUDBEES DOES NOT WARRANT THAT THE SERVICE WILL BE UNINTERRUPTED, TIMELY, SECURE, ERROR-FREE OR VIRUS-FREE AND NO INFORMATION OR ADVICE OBTAINED BY YOU FROM CLOUDBEES OR THROUGH THE SERVICE SHALL CREATE ANY WARRANTY NOT EXPRESSLY STATED IN THIS TOS.” It appears that this service might transmit our comany-owned source code, unencrypted, outside of our network. I doubt that this would be acceptable to Corporate Security, Legal or IP. Due Date: 06/Mar/13 12:00 AM Environment: security violation of terms and conditions. Project: Jenkins Labels: security Priority: Critical Reporter: kirankumar konduri This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16990) unable to resolve class hudson.maven.reporters.SurefireAggregatedReport in groovy template
Alex Earl commented on JENKINS-16990 unable to resolve class hudson.maven.reporters.SurefireAggregatedReport in groovy template No idea This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17074) ImprovementTrigger doesn't trigger when a build improves all the way to having 0 test failures
Alex Earl commented on JENKINS-17074 ImprovementTrigger doesnt trigger when a build improves all the way to having 0 test failures Feel free to submit a pull request with updated help text that you feel would be more clear. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15643) Consistent Out Of Memory Error When Adding 101st Build Node
Greg horvath resolved JENKINS-15643 as Not A Defect Consistent Out Of Memory Error When Adding 101st Build Node Change By: Greg horvath (05/Mar/13 5:05 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15643) Consistent Out Of Memory Error When Adding 101st Build Node
Greg horvath closed JENKINS-15643 as Not A Defect Consistent Out Of Memory Error When Adding 101st Build Node Change By: Greg horvath (05/Mar/13 5:06 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15643) Consistent Out Of Memory Error When Adding 101st Build Node
Greg horvath commented on JENKINS-15643 Consistent Out Of Memory Error When Adding 101st Build Node Increasing max proc fixed this. Going to close out the ticket. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14062) can we zip ALL the backups and not just the 'old' ones?
Thomas Fürer commented on JENKINS-14062 can we zip ALL the backups and not just the old ones? this is a valid request. I need to find a solution to manage this, because I need an uncompressed version to do the differential backups. Also there are some higher priored issues I need to fix, e.g. more feedback during backup and abortable backup. Please stay tuned. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-9905) Expose new env var containing job name without build axis information appended
Camillo Bruni commented on JENKINS-9905 Expose new env var containing job name without build axis information appended I totally agree. If you have a lot of projects it is nice to depend on the JOB_NAME for settings. How about introducing JOB_BASENAME which does not contain this params? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17078) Different view of artifact in project overview
C. S. created JENKINS-17078 Different view of artifact in project overview Issue Type: Bug Assignee: Unassigned Attachments: artifacts.png Components: core Created: 05/Mar/13 5:18 PM Description: It seems there is a difference in showing artifacts in multi configuration projects. Project: Jenkins Labels: artifact view Priority: Minor Reporter: C. S. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17079) hudson.tasks.LogRotator@e696f9/365/x on screen
Markus KARG created JENKINS-17079 hudson.tasks.LogRotator@e696f9/365/x on screen Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 05/Mar/13 5:26 PM Description: The job configuration page shows this string: "hudson.tasks.LogRotator@e696f9/365/x". I appears under the line where the number of days to keep build is to be entered. Environment: Jenkins 1.504 / Tomcat 6 / JDK 1.6.0_18 / Debian 6 / x86 Project: Jenkins Priority: Minor Reporter: Markus KARG This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17080) Jenkins fails to start after restart
Vassilena Treneva created JENKINS-17080 Jenkins fails to start after restart Issue Type: Bug Assignee: Unassigned Components: core Created: 05/Mar/13 5:35 PM Description: After restarting the machine, I started seeing this error when trying to start Jenkins. Any ideas what went wrong? Perhaps some configuration? bambpmsauto:/etc/init.d # ./jenkins start Starting Jenkins startproc -n 0 -s -e -l /var/log/jenkins.rc -p /var/run/jenkins .pid -t 1 /bin/su -l -s /bin/bash -c /usr/local/jdk1.7.0_17/bin/java -Djava.awt. headless=true -XX:MaxPermSize=512M -DJENKINS_HOME=/var/lib/jenkins -jar /usr/lib /jenkins/jenkins.war --javaHome=/usr/local/jdk1.7.0_17 --logfile=/var/log/jenkin s/jenkins.log --webroot=/var/cache/jenkins/war --httpPort=8080 --ajp13Port=8009 --debug=5 --handlerCountMax=100 --handlerCountMaxIdle=20 jenkins failed Project: Jenkins Priority: Critical Reporter: Vassilena Treneva This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17081) Permission hudson.model.Item.Read:anonymous coming from nowhere
José Roberto A. JR. created JENKINS-17081 Permission hudson.model.Item.Read:anonymous coming from nowhere Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: 1-after-save.png, 2-click-reload.png, 3-after-reload.png Components: security Created: 05/Mar/13 5:51 PM Description: Steps to reproduce: 1. Go to the Configure Global Security screen (http://server/jenkins/configureSecurity/) and choose "enable security" 2. Select "Jenkins's own user database" as the security realm 3. Select "Project-based Matrix Authorization Strategy" as the authorization 4. Give anonymous user the read access to overall 5. In the text box below the table, type in your user name and click "add" 6. Give yourself a full access by checking the entire row for your user name 7. Scroll all the way to the bottom, click "save" Now, you have access to all projects and anonymous users have access to specific projects, the config.xml will have: authorizationStrategy class="hudson.security.ProjectMatrixAuthorizationStrategy" permissionhudson.model.Computer.Configure:jose.rob.jr/permission permissionhudson.model.Computer.Connect:jose.rob.jr/permission permissionhudson.model.Computer.Create:jose.rob.jr/permission permissionhudson.model.Computer.Delete:jose.rob.jr/permission permissionhudson.model.Computer.Disconnect:jose.rob.jr/permission permissionhudson.model.Hudson.Administer:jose.rob.jr/permission permissionhudson.model.Hudson.ConfigureUpdateCenter:jose.rob.jr/permission permissionhudson.model.Hudson.Read:anonymous/permission permissionhudson.model.Hudson.Read:jose.rob.jr/permission permissionhudson.model.Hudson.RunScripts:jose.rob.jr/permission permissionhudson.model.Hudson.UploadPlugins:jose.rob.jr/permission permissionhudson.model.Item.Build:jose.rob.jr/permission permissionhudson.model.Item.Cancel:jose.rob.jr/permission permissionhudson.model.Item.Configure:jose.rob.jr/permission permissionhudson.model.Item.Create:jose.rob.jr/permission permissionhudson.model.Item.Delete:jose.rob.jr/permission permissionhudson.model.Item.Discover:jose.rob.jr/permission permissionhudson.model.Item.Read:jose.rob.jr/permission permissionhudson.model.Item.Workspace:jose.rob.jr/permission permissionhudson.model.Run.Delete:jose.rob.jr/permission permissionhudson.model.Run.Update:jose.rob.jr/permission permissionhudson.model.View.Configure:jose.rob.jr/permission permissionhudson.model.View.Create:jose.rob.jr/permission permissionhudson.model.View.Delete:jose.rob.jr/permission permissionhudson.model.View.Read:jose.rob.jr/permission permissionhudson.scm.SCM.Tag:jose.rob.jr/permission /authorizationStrategy Go to jenkin management screen (http://server/jenkins/manage) and click "Reload configs from disk" After it finishes anonymous users can now access all projects, if you go to the Configure Global Security screen you'll see that anonymous task read is checked If you save again without changing anything, the config.xml will have: authorizationStrategy class="hudson.security.ProjectMatrixAuthorizationStrategy" permissionhudson.model.Computer.Configure:jose.rob.jr/permission permissionhudson.model.Computer.Connect:jose.rob.jr/permission permissionhudson.model.Computer.Create:jose.rob.jr/permission permissionhudson.model.Computer.Delete:jose.rob.jr/permission permissionhudson.model.Computer.Disconnect:jose.rob.jr/permission permissionhudson.model.Hudson.Administer:jose.rob.jr/permission permissionhudson.model.Hudson.ConfigureUpdateCenter:jose.rob.jr/permission permissionhudson.model.Hudson.Read:anonymous/permission permissionhudson.model.Hudson.Read:jose.rob.jr/permission permissionhudson.model.Hudson.RunScripts:jose.rob.jr/permission permissionhudson.model.Hudson.UploadPlugins:jose.rob.jr/permission permissionhudson.model.Item.Build:jose.rob.jr/permission
[JIRA] (JENKINS-17082) Jenkins Job failed because slave was done in the middle of the run
Albert Cheng created JENKINS-17082 Jenkins Job failed because slave was done in the middle of the run Issue Type: Bug Assignee: Unassigned Components: slave-status Created: 05/Mar/13 6:15 PM Description: ERROR: Failed to parse POMs hudson.remoting.ChannelClosedException: channel is already closed at hudson.remoting.Channel.send(Channel.java:494) at hudson.remoting.Request.call(Request.java:129) at hudson.remoting.Channel.call(Channel.java:672) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:158) at $Proxy31.isAlive(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:866) at hudson.maven.ProcessCache$MavenProcess.call(ProcessCache.java:161) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:791) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:500) at hudson.model.Run.execute(Run.java:1502) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Caused by: java.net.SocketException: socket closed at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(Unknown Source) at java.io.BufferedInputStream.fill(Unknown Source) at java.io.BufferedInputStream.read(Unknown Source) at java.io.ObjectInputStream$PeekInputStream.peek(Unknown Source) at java.io.ObjectInputStream$BlockDataInputStream.peek(Unknown Source) at java.io.ObjectInputStream$BlockDataInputStream.peekByte(Unknown Source) at java.io.ObjectInputStream.readObject0(Unknown Source) at java.io.ObjectInputStream.readObject(Unknown Source) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:59) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) Looks like the node went offline during the build. Check the slave log for the details. details FATAL: channel is already closed hudson.remoting.ChannelClosedException: channel is already closed at hudson.remoting.Channel.send(Channel.java:494) at hudson.remoting.Request.call(Request.java:129) at hudson.remoting.Channel.call(Channel.java:672) at hudson.Launcher$RemoteLauncher.kill(Launcher.java:823) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:523) at hudson.model.Run.execute(Run.java:1502) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Caused by: java.net.SocketException: socket closed at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(Unknown Source) at java.io.BufferedInputStream.fill(Unknown Source) at java.io.BufferedInputStream.read(Unknown Source) at java.io.ObjectInputStream$PeekInputStream.peek(Unknown Source) at java.io.ObjectInputStream$BlockDataInputStream.peek(Unknown Source) at java.io.ObjectInputStream$BlockDataInputStream.peekByte(Unknown Source) at java.io.ObjectInputStream.readObject0(Unknown Source) at java.io.ObjectInputStream.readObject(Unknown Source) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:59) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) Environment: Windows Server 2012 Project: Jenkins Priority: Major Reporter: Albert Cheng
[JIRA] (JENKINS-17076) Poll SCM brings up a window complaining about submitting a POST
Peter Nordquist
updated JENKINS-17076
Poll SCM brings up a window complaining about submitting a POST
Update bug based on issue submission guidelines (change priority) and add Workaround.
Change By:
Peter Nordquist
(05/Mar/13 6:21 PM)
Priority:
Major
Minor
Description:
WhenIclickthePollSCMlinkforajobitbringsupawindowcomplainingaboutnotusingaHTTPPOST.Themessageisbelow.
{{
YoumustusePOSTmethodtotriggerbuilds.(Fromscriptsyoumayinsteadpassaper-projectauthenticationtoken,orauthenticatewithyourAPItoken.)Ifyouseethispage,itmaybebecauseapluginofferedaGETlink;fileabugreportforthatplugin.
}}Workaround:Clicktheproceedbuttononthenewwebpageanditwillpollproperly.YouthenhavetoreturntotheJobviathebreadcrumbs.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17083) Git Plugin 1.2.0 fails to use ENV vars (1.1.26 works)
bootstraponline created JENKINS-17083 Git Plugin 1.2.0 fails to use ENV vars (1.1.26 works) Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 05/Mar/13 7:21 PM Description: Build works using Git plugin 1.1.26. Upgrading to 1.2.0 causes build to fail. Downgrading plugin back to 1.1.26 restores the build. Fetching changes from 1 remote Git repository Fetching upstream changes from origin No candidate revisions ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job. Archiving artifacts Recording test results Finished: FAILURE I'm using a parameterized build with environment variables for repository url and branch specifier. Environment: Jenkins 1.504 Project: Jenkins Priority: Major Reporter: bootstraponline This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17084) ChangeLog should produce output even if some annotator fails
vjuranek created JENKINS-17084 ChangeLog should produce output even if some annotator fails Issue Type: Bug Assignee: vjuranek Attachments: changeset_error.png Components: core Created: 05/Mar/13 7:34 PM Description: If some ChangeLogAnnotator fails (usually by throwing exception or error), there's no changelog message at all (see attached screenshot). If possible, Jenkins core should be resistant to third party failures (plugin or underlaying servlet container) and produce some reasonable output even in such cases. Project: Jenkins Priority: Major Reporter: vjuranek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17084) ChangeLog should produce output even if some annotator fails
vjuranek commented on JENKINS-17084 ChangeLog should produce output even if some annotator fails partially fixed in https://github.com/jenkinsci/jenkins/commit/d85dc98e8051066a967f2c77aaa6e06c4be9262d This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17083) Git Plugin 1.2.0 fails to use ENV vars (1.1.26 works)
bootstraponline updated JENKINS-17083 Git Plugin 1.2.0 fails to use ENV vars (1.1.26 works) Change By: bootstraponline (05/Mar/13 7:48 PM) Description: BuildworksusingGitplugin1.1.26.Upgradingto1.2.0causesbuildtofail.Downgradingpluginbackto1.1.26restoresthebuild.Fetchingchangesfrom1remoteGitrepositoryFetchingupstreamchangesfromoriginNocandidaterevisionsERROR:Couldntfindanyrevisiontobuild.Verifytherepositoryandbranchconfigurationforthisjob.ArchivingartifactsRecordingtestresultsFinished:FAILUREImusingaparameterizedbuildwithenvironmentvariablesforrepositoryurlandbranchspecifier. ThebuildistriggeredwithleeroywhichusesGIT_BASE_REPO,GIT_HEAD_REPO,GIT_SHA1,GITHUB_URL.https://github.com/litl/leeroy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17084) ChangeLog should produce output even if some annotator fails
vjuranek commented on JENKINS-17084 ChangeLog should produce output even if some annotator fails proposed fix: https://github.com/jenkinsci/jenkins/pull/729 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-9905) Expose new env var containing job name without build axis information appended
Thomas Fields commented on JENKINS-9905 Expose new env var containing job name without build axis information appended Don't hold your breath for this change. The issue isn't even assigned and it's well over a year old. Sad face. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17085) f:textarea previewEndpoint=/markupFormatter/previewDescription/ does not work when crumbs enabled
Jesse Glick created JENKINS-17085 f:textarea previewEndpoint=/markupFormatter/previewDescription/ does not work when crumbs enabled Issue Type: Bug Assignee: Jesse Glick Components: core Created: 05/Mar/13 8:20 PM Description: Create an admin user with full perms, and deny all perms to anonymous; and enable CSRF protection. Now go to the Jenkins root page, click add description, type anything, and click Preview. You are greeted with div class="textarea-preview" style=""403 No_valid_crumb_was_included_in_the_requesthr meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" titleError 403 /title h2HTTP ERROR: 403/h2preNo valid crumb was included in the request/pre pRequestURI=/markupFormatter/previewDescription/ppismalla href="" class="code-quote">"http://jetty.mortbay.org/"Powered by Jetty:///a/small/i/pbr ... /div Environment: 1.446.2 or 1.506-SNAPSHOT Project: Jenkins Labels: csrf security Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16716) FILE token does not evaluate a path that contains an environment variable
Kavita Tiwari commented on JENKINS-16716 FILE token does not evaluate a path that contains an environment variable Thanks for clarifying about PROPFILE. As I am no longer using PROPFILE, I'll hold off on raising a ticket with the token-macro plug-in for PROPFILE not evaluating a path that contain an environment variable. Yes you are right. I could probably do what I have described above in this ticket with a groovy template and have the groovy do the job of evaluating the environment variable. But at present I've only been using plain-text e-mails. Though I do like the suggestion of using a groovy template, and it would be a good workaround for this issue. Do you know when the next version of email-ext with your changes will be made available? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16884) EC2 plugin starts too many slave nodes
Kevin Fleming updated JENKINS-16884 EC2 plugin starts too many slave nodes The attached 'ec2.hpi' is a build from the current master of the ec2-plugin repository, plus a proposed patch to correct a backwards compatibility issue created by a recent patch of mine that has already been merged. Thanks for offering to help test it! Change By: Kevin Fleming (05/Mar/13 8:27 PM) Attachment: ec2.hpi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16716) FILE token does not evaluate a path that contains an environment variable
Alex Earl commented on JENKINS-16716 FILE token does not evaluate a path that contains an environment variable I haven't implemented anything in regards to this ticket, so I am not sure what version it will get into. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17083) Git Plugin 1.2.0 fails to use ENV vars (1.1.26 works)
bootstraponline updated JENKINS-17083 Git Plugin 1.2.0 fails to use ENV vars (1.1.26 works) Change By: bootstraponline (05/Mar/13 8:35 PM) Description: BuildworksusingGitplugin1.1.26.Upgradingto1.2.0causesbuildtofail.Downgradingpluginbackto1.1.26restoresthebuild.Fetchingchangesfrom1remoteGitrepositoryFetchingupstreamchangesfromoriginNocandidaterevisionsERROR:Couldntfindanyrevisiontobuild.Verifytherepositoryandbranchconfigurationforthisjob.ArchivingartifactsRecordingtestresultsFinished:FAILUREImusingaparameterizedbuildwithenvironmentvariablesforrepositoryurlandbranchspecifier.ThebuildistriggeredwithleeroywhichusesGIT_BASE_REPO,GIT_HEAD_REPO,GIT_SHA1,GITHUB_URL.https://github.com/litl/leeroy Theresalsoanotherissue.java.lang.UnsupportedOperationException:getCandidateRevisionsmethodmustbeoverriddenUninstallinggit,git-client,rebooting,theninstallinggit,git-clientandrebootingoncemoreappearstohavefixedtheissue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16716) FILE token does not evaluate a path that contains an environment variable
Kavita Tiwari commented on JENKINS-16716 FILE token does not evaluate a path that contains an environment variable I meant when the new version of email-ext with your fix for this other ticket https://issues.jenkins-ci.org/browse/JENKINS-16916 will be available to upgrade 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16716) FILE token does not evaluate a path that contains an environment variable
Alex Earl commented on JENKINS-16716 FILE token does not evaluate a path that contains an environment variable It's available now (2.27) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-7291) Flyweight jobs and zero executors
recampbell commented on JENKINS-7291 Flyweight jobs and zero executors It would be nice if one could allow flyweight tasks on master even when no executors are configured. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-7280) run parameters show builds that have not completed or have failed / unstable
Geoff Cummings assigned JENKINS-7280 to Geoff Cummings run parameters show builds that have not completed or have failed / unstable Change By: Geoff Cummings (05/Mar/13 8:55 PM) Assignee: GeoffCummings This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-7280) run parameters show builds that have not completed or have failed / unstable
Geoff Cummings started work on JENKINS-7280 run parameters show builds that have not completed or have failed / unstable Change By: Geoff Cummings (05/Mar/13 9:03 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-10435) Join project not triggered correctly when passing SCM info downstream via downstream-ext plugin
Thomas Fields commented on JENKINS-10435 Join project not triggered correctly when passing SCM info downstream via downstream-ext plugin Just going over some of my old issues - did you manage to make the change to the join plugin and Jenkins 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17083) Git Plugin 1.2.0 fails to use ENV vars (1.1.26 works)
bootstraponline updated JENKINS-17083 Git Plugin 1.2.0 fails to use ENV vars (1.1.26 works) Change By: bootstraponline (05/Mar/13 9:30 PM) Description: BuildworksusingGitplugin1.1.26.Upgradingto1.2.0causesbuildtofail.Downgradingpluginbackto1.1.26restoresthebuild.Fetchingchangesfrom1remoteGitrepositoryFetchingupstreamchangesfromoriginNocandidaterevisionsERROR:Couldntfindanyrevisiontobuild.Verifytherepositoryandbranchconfigurationforthisjob.ArchivingartifactsRecordingtestresultsFinished:FAILUREImusingaparameterizedbuildwithenvironmentvariablesforrepositoryurlandbranchspecifier.ThebuildistriggeredwithleeroywhichusesGIT_BASE_REPO,GIT_HEAD_REPO,GIT_SHA1,GITHUB_URL.https://github.com/litl/leeroyTheresalsoanotherissue.java.lang.UnsupportedOperationException:getCandidateRevisionsmethodmustbeoverriddenUninstallinggit,git-client,rebooting,theninstallinggit,git-clientandrebootingoncemoreappearstohavefixedtheissue. Nocandidaterevisionsstilloccursthough. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17064) Unable to edit some build definitions
Yury Zaytsev commented on JENKINS-17064 Unable to edit some build definitions Same here, Jenkins LTS / RHEL6 / email-ext: can't edit the jobs that have email-ext (in my case all matrix jobs). The error appears where email-ext configuration ought to be: Exception: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.480.3.jar!/lib/form/hetero-list.jelly:112:94: st:include org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.480.3.jar!/lib/form/entry.jelly:73:23: d:invokeBody Cannot get property 'description' on null object This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17064) Unable to edit some build definitions
Alex Earl commented on JENKINS-17064 Unable to edit some build definitions Yes, it seems as if there is something that is not working with the f:enum taglib when using it within a groovy view. I am trying to determine what is going on and as soon as I do, I will do a fix and a release. For now, I recommend downgrading to 2.25 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17079) hudson.tasks.LogRotator@e696f9/365/x on screen
kutzi resolved JENKINS-17079 as Duplicate hudson.tasks.LogRotator@e696f9/365/x on screen Change By: kutzi (05/Mar/13 9:47 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17083) Git Plugin 1.2.0 fails to use ENV vars (1.1.26 works)
bootstraponline updated JENKINS-17083 Git Plugin 1.2.0 fails to use ENV vars (1.1.26 works) Change By: bootstraponline (05/Mar/13 9:49 PM) Description: BuildworksusingGitplugin1.1.26.Upgradingto1.2.0causesbuildtofail.Downgradingpluginbackto1.1.26restoresthebuild.Fetchingchangesfrom1remoteGitrepositoryFetchingupstreamchangesfromoriginNocandidaterevisionsERROR:Couldntfindanyrevisiontobuild.Verifytherepositoryandbranchconfigurationforthisjob.ArchivingartifactsRecordingtestresultsFinished:FAILUREImusingaparameterizedbuildwithenvironmentvariablesforrepositoryurlandbranchspecifier.ThebuildistriggeredwithleeroywhichusesGIT_BASE_REPO,GIT_HEAD_REPO,GIT_SHA1,GITHUB_URL.https://github.com/litl/leeroyTheresalsoanotherissue.java.lang.UnsupportedOperationException:getCandidateRevisionsmethodmustbeoverriddenUninstallinggit,git-client,rebooting,theninstallinggit,git-clientandrebootingoncemoreappearstohavefixed theissue getCandidateRevisions .Nocandidaterevisionsstilloccursthough. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14238) Use Local module directory instead Use custom workspace
kutzi resolved JENKINS-14238 as Duplicate Use Local module directory instead Use custom workspace Change By: kutzi (05/Mar/13 9:51 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-10446) Cannot save a job in Jenkins
kutzi resolved JENKINS-10446 as Cannot Reproduce Cannot save a job in Jenkins No response from reporter = closing as not reproducable Change By: kutzi (05/Mar/13 9:51 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17085) f:textarea previewEndpoint=/markupFormatter/previewDescription/ does not work when crumbs enabled
SCM/JIRA link daemon resolved JENKINS-17085 as Fixed f:textarea previewEndpoint=/markupFormatter/previewDescription/ does not work when crumbs enabled Change By: SCM/JIRA link daemon (05/Mar/13 10:07 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17085) f:textarea previewEndpoint=/markupFormatter/previewDescription/ does not work when crumbs enabled
SCM/JIRA link daemon commented on JENKINS-17085 f:textarea previewEndpoint=/markupFormatter/previewDescription/ does not work when crumbs enabled Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/resources/lib/form/textarea/textarea.js http://jenkins-ci.org/commit/jenkins/50f14f28e55bb39dd2959040734964889c70c7cb Log: FIXED JENKINS-17085 Bogus requestHeaders value prevented crumb addition. (Ah, the joys of dynamic typing!) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17064) Unable to edit some build definitions
SCM/JIRA link daemon commented on JENKINS-17064 Unable to edit some build definitions Code changed in jenkins User: Alex Earl Path: src/main/resources/hudson/plugins/emailext/ExtendedEmailPublisher/config.groovy http://jenkins-ci.org/commit/email-ext-plugin/eebeaa6f5eb83eb6dc9ac5e47a26869e84a98b89 Log: Fix JENKINS-17064 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
