[JIRA] (JENKINS-16764) Pruning too many baselines, case 8559
Christian Wolfgang updated JENKINS-16764 Pruning too many baselines, case 8559 Change By: Christian Wolfgang (12/Feb/13 7:59 AM) Summary: Pruningtoomanybaselines ,case8559 This message is automatically generated by JIRA. 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-16761) Linux support, case 8616
Christian Wolfgang updated JENKINS-16761 Linux support, case 8616 Change By: Christian Wolfgang (12/Feb/13 8:00 AM) Summary: Linuxsupport ,case8616 This message is automatically generated by JIRA. 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-16763) Resolved issue with polling, case 8614
Christian Wolfgang updated JENKINS-16763 Resolved issue with polling, case 8614 Change By: Christian Wolfgang (12/Feb/13 8:01 AM) Summary: Resolvedissuewithpolling ,case8614 This message is automatically generated by JIRA. 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-16762) Changed logger, case 8615
Christian Wolfgang updated JENKINS-16762 Changed logger, case 8615 Change By: Christian Wolfgang (12/Feb/13 8:02 AM) Summary: Changedlogger ,case8615 This message is automatically generated by JIRA. 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-16768) move jenkins from local to my host
kutzi closed JENKINS-16768 as Not A Defect move jenkins from local to my host Change By: kutzi (12/Feb/13 8:35 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16768) move jenkins from local to my host
kutzi resolved JENKINS-16768 as Not A Defect move jenkins from local to my host Not a bug. Please use the users list for questions! Change By: kutzi (12/Feb/13 8:34 AM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16770) missing build title in /rssAll when build has no test result
Richard Mortimer started work on JENKINS-16770 missing build title in /rssAll when build has no test result Change By: Richard Mortimer (12/Feb/13 9:00 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16770) missing build title in /rssAll when build has no test result
Richard Mortimer created JENKINS-16770 missing build title in /rssAll when build has no test result Issue Type: Bug Affects Versions: current Assignee: Richard Mortimer Components: core Created: 12/Feb/13 9:00 AM Description: The title element for a build is empty in the /rssAll feed if a particular build does not have a test result but the previous build had a test result. entrytitle/link type="text/html" href="" class="code-quote">"http://jenkins.local/job/MyTestJob/19/" rel="alternate"/idtag:hudson.dev.java.net,2013:MyTestJob:2013-02-11_16-50-40/idpublished2013-02-11T16:50:40Z/publishedupdated2013-02-11T16:50:40Z/updated/entry The following stacktrace appears in jenkins.log 11-Feb-2013 17:31:11 hudson.ExpressionFactory2$JexlExpression evaluate WARNING: Caught exception evaluating: adapter.getEntryTitle(e) in /rssAll. Reason: java.lang.NullPointerException java.lang.NullPointerException at hudson.model.Run.determineDetailedUnstableSummary(Run.java:1829) at hudson.model.Run.getBuildStatusSummary(Run.java:1800) at hudson.model.Run$DefaultFeedAdapter.getEntryTitle(Run.java:2145) at hudson.model.Run$DefaultFeedAdapter.getEntryTitle(Run.java:2143) at sun.reflect.GeneratedMethodAccessor106.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258) at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly.parser.EscapingExpression.evaluate(EscapingExpression.java:24) at org.apache.commons.jelly.impl.ExpressionScript.run(ExpressionScript.java:66) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.impl.StaticTag.doTag(StaticTag.java:65) at org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java:124) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.impl.StaticTag.doTag(StaticTag.java:65) at org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java:124) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.impl.StaticTag.doTag(StaticTag.java:65) at org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java:124) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) at org.kohsuke.stapler.jelly.JellyRequestDispatcher.forward(JellyRequestDispatcher.java:55) at hudson.model.RSS.forwardToRss(RSS.java:86) at hudson.model.View.rss(View.java:988)
[JIRA] (JENKINS-16754) $JOB_NAME is set to some autogenerated string instead of the project name
Gregory Boissinot commented on JENKINS-16754 $JOB_NAME is set to some autogenerated string instead of the project name According to the EnvInject source code, it does not modify the JOB NAME variable. Does your WORKSPACE variable value is correct? I suggest you should try to isolate the problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-16398) Relative pre-build Script paths don't work
Gregory Boissinot commented on JENKINS-16398 Relative pre-build Script paths dont work Does it work for you? This message is automatically generated by JIRA. 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-16766) Claim plugin no longer renders HTML in Reason field after upgrade from 1.7 to 2.0
Christian Åkerström started work on JENKINS-16766 Claim plugin no longer renders HTML in Reason field after upgrade from 1.7 to 2.0 Change By: Christian Åkerström (12/Feb/13 9:31 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16754) $JOB_NAME is set to some autogenerated string instead of the project name
Emil Bäckmark commented on JENKINS-16754 $JOB_NAME is set to some autogenerated string instead of the project name Yes, the WORKSPACE variable contains the correct JOB_NAME. This message is automatically generated by JIRA. 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-16723) NPE when performing integration.
Joan Ardiaca commented on JENKINS-16723 NPE when performing integration. I'm getting the same error with version 1.480.2. It doesn't matter if there were any changes or not in the repo, the same error comes always, almost: strangely the build succeeded once without this error. This message is automatically generated by JIRA. 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-16771) Xcode plugin doesn't read the Source Trees setting from the IDE
Tzuchien created JENKINS-16771 Xcode plugin doesnt read the Source Trees setting from the IDE Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: xcode Created: 12/Feb/13 10:29 AM Description: My source code relies upon the settings of Source Trees to build (from Xcode IDE - Preference - Locations - Source Trees). It seems that the Xcode plugin doesn't read these settings because the same source code can be built from the command line 'xcodebuild'. Project: Jenkins Priority: Critical Reporter: Tzuchien This message is automatically generated by JIRA. 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-16772) NullPointerException in Postbuild action for matrix child
Magnus Jacobsson created JENKINS-16772 NullPointerException in Postbuild action for matrix child Issue Type: Bug Assignee: Gregory Boissinot Components: postbuildscript Created: 12/Feb/13 10:30 AM Description: PostBuildScript gives NullPointerException for matrix child jobs, Works ok for parent job. From parent log: Triggering value1 Triggering value2 value1 completed with result SUCCESS value2 completed with result SUCCESS PostBuildScript - Execution post build scripts. workspace $ /bin/sh -xe /tmp/hudson4750159053349493502.sh + echo Post-build action, build step, Execute shell Post-build action, build step, Execute shell + echo PREPARED_ENV_VAR = PREPARED_ENV_VAR = + echo GENERATED_ENV_VAR_FROM_SCRIPT = GENERATED_ENV_VAR_FROM_SCRIPT = + echo INJECTED_ENV_VAR = INJECTED_ENV_VAR = Finished: SUCCESS From child log: ... EnvInject - Script executed successfully. value1 $ /bin/sh -xe /tmp/hudson4061121161659393893.sh + echo Build, Execute shell Build, Execute shell + echo PREPARED_ENV_VAR = PREPARED_ENV_VAR = + echo GENERATED_ENV_VAR_FROM_SCRIPT = yes GENERATED_ENV_VAR_FROM_SCRIPT = yes + echo INJECTED_ENV_VAR = INJECTED_ENV_VAR = Finished: SUCCESS From system log_ 2013-feb-12 11:02:32 hudson.model.Run execute INFO: magjac-matrix-test #4 main build action completed: SUCCESS 2013-feb-12 11:02:31 hudson.model.Run execute INFO: magjac-matrix-test » value1 #4 main build action completed: SUCCESS 2013-feb-12 11:02:31 hudson.model.Run execute INFO: magjac-matrix-test » value2 #4 main build action completed: SUCCESS 2013-feb-12 11:02:31 hudson.model.listeners.RunListener report VARNING: RunListener failed java.lang.NullPointerException at org.jenkinsci.plugins.postbuildscript.PostBuildScriptListener.putLastListPostBuildPublisher(PostBuildScriptListener.java:51) at org.jenkinsci.plugins.postbuildscript.PostBuildScriptListener.onStarted(PostBuildScriptListener.java:36) at hudson.model.listeners.RunListener.fireStarted(RunListener.java:195) at hudson.model.Run.execute(Run.java:1552) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) 2013-feb-12 11:02:31 hudson.model.listeners.RunListener report VARNING: RunListener failed java.lang.NullPointerException at org.jenkinsci.plugins.postbuildscript.PostBuildScriptListener.putLastListPostBuildPublisher(PostBuildScriptListener.java:51) at org.jenkinsci.plugins.postbuildscript.PostBuildScriptListener.onStarted(PostBuildScriptListener.java:36) at hudson.model.listeners.RunListener.fireStarted(RunListener.java:195) at hudson.model.Run.execute(Run.java:1552) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) 2013-feb-12 11:00:08 hudson.model.Run execute INFO: magjac-trig-test #3 main build action completed: SUCCESS Environment: Ubuntu 10.04, Jenkins 1.500, Jenkins Post-Build Script Plug-in 0.10 Project: Jenkins Priority: Major Reporter: Magnus Jacobsson This message is automatically generated by JIRA. 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
[JIRA] (JENKINS-16773) Delete Project causes java.lang.NullPointerException
Hans Baer created JENKINS-16773 Delete Project causes java.lang.NullPointerException Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 12/Feb/13 10:54 AM Description: Once I try to delete an existing project, I face the following exception. Weird thing is that it does not seem to occur for all my jobs. Creating a new job and deleting it immediately, will not trigger this. Have not been able to determine on what is causing the exception. Please let me know if you need more inputs on this. Thanks! Status Code: 500 Exception: java.lang.NullPointerException Stacktrace: javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:615) 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: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.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) 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
[JIRA] (JENKINS-16773) Delete Project causes java.lang.NullPointerException
Hans Baer commented on JENKINS-16773 Delete Project causes java.lang.NullPointerException Figured out on what is causing the exception. In case you disable SCM "Base Clearcase" configuration of the corresponding job and then try to delete it, everything works out well. Thus Clearcase plugin seems to be the root cause for 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-16774) URLTrigger gives severe error message instead of detecting change
Magnus Jacobsson created JENKINS-16774 URLTrigger gives severe error message instead of detecting change Issue Type: Bug Assignee: Gregory Boissinot Attachments: config.xml Components: urltrigger Created: 12/Feb/13 11:17 AM Description: The URLTrigger gives severe error instead of detecting change. From trigger log: URLTrigger - Poll with a URL Inspecting Monitor a change of the content content for URL http://build.netinsight.se/autobuild/dev/acf/continuous/release/ Polling started on 2013-feb-12 12:12:12 Polling for the job dev-acf Looking nodes where the poll can be run. Looking for a candidate node to run the poll. Looking for a node with no predefined label. Trying to poll with the last built on node. Polling on master. ERROR - SEVERE - Polling error null I think this problem started after restart (and possibly upgrade of Jenkins and URLTrigger plugin). Updating the configuration doesn't help, but if manually run once, it seems to start working again. Attached is the config. Environment: Ubuntu 10.04, Jenkins 1.500, Jenkins URLTrigger Plug-in 0.27. Project: Jenkins Priority: Critical Reporter: Magnus Jacobsson This message is automatically generated by JIRA. 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-16715) Multijob builder creates two ParameterActions when using parameters from triggering job.
SCM/JIRA link daemon resolved JENKINS-16715 as Fixed Multijob builder creates two ParameterActions when using parameters from triggering job. Change By: SCM/JIRA link daemon (12/Feb/13 11:28 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16704) Wrong file delimiters - our case 8584
Christian Wolfgang resolved JENKINS-16704 as Fixed Wrong file delimiters - our case 8584 Change By: Christian Wolfgang (12/Feb/13 11:33 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16764) Pruning too many baselines, case 8559
Christian Wolfgang resolved JENKINS-16764 as Fixed Pruning too many baselines, case 8559 Change By: Christian Wolfgang (12/Feb/13 11:33 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16774) URLTrigger gives severe error message instead of detecting change
Marcel Huber commented on JENKINS-16774 URLTrigger gives severe error message instead of detecting change The same error applies when using jenkins 1.501 and URLTrigger plugin 0.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-16774) URLTrigger gives severe error message instead of detecting change
Marcel Huber edited a comment on JENKINS-16774 URLTrigger gives severe error message instead of detecting change The same error applies when using jenkins 1.501 and URLTrigger plugin 0.27 I just looked through the logs and detected these lines: Feb 12 12:54:32 ... jenkins438: Feb 12, 2013 12:54:32 PM org.jenkinsci.plugins.urltrigger.URLTrigger start Feb 12 12:54:32 ... jenkins438: SEVERE: Severe error on trigger startup null Feb 12 12:54:32 ... jenkins438: java.lang.NullPointerException Feb 12 12:54:32 ... jenkins438: at org.jenkinsci.lib.envinject.service.EnvInjectActionRetriever.getEnvInjectAction(EnvInjectActionRetriever.java:32) Feb 12 12:54:32 ... jenkins438: at org.jenkinsci.lib.envinject.service.EnvVarsResolver.getEnVars(EnvVarsResolver.java:52) Feb 12 12:54:32 ... jenkins438: at org.jenkinsci.lib.envinject.service.EnvVarsResolver.getPollingEnvVars(EnvVarsResolver.java:34) Feb 12 12:54:32 ... jenkins438: at org.jenkinsci.plugins.urltrigger.URLTrigger.getURLValue(URLTrigger.java:108) Feb 12 12:54:32 ... jenkins438: at org.jenkinsci.plugins.urltrigger.URLTrigger.start(URLTrigger.java:260) Feb 12 12:54:32 ... jenkins438: at org.jenkinsci.lib.xtrigger.AbstractTrigger.start(AbstractTrigger.java:97) Feb 12 12:54:32 ... jenkins438: at org.jenkinsci.lib.xtrigger.AbstractTrigger.start(AbstractTrigger.java:26) Feb 12 12:54:32 ... jenkins438: at hudson.model.AbstractProject.submit(AbstractProject.java:1884) Feb 12 12:54:32 ... jenkins438: at hudson.model.Project.submit(Project.java:195) Feb 12 12:54:32 ... jenkins438: at hudson.model.Job.doConfigSubmit(Job.java:1045) Feb 12 12:54:32 ... jenkins438: at hudson.model.AbstractProject.doConfigSubmit(AbstractProject.java:729) So it might be related to the EnvInject plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16338) Jenkins fails to keep connection alive on Windows 8
Ireneusz Makowski commented on JENKINS-16338 Jenkins fails to keep connection alive on Windows 8 I have similar issue on 1.501 hudson.util.IOException2: remote file operation failed: c:\jenkins\workspace\project at hudson.remoting.Channel@65817:win8-tmp at hudson.FilePath.act(FilePath.java:861) at hudson.FilePath.act(FilePath.java:838) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:789) at hudson.model.AbstractProject.checkout(AbstractProject.java:1331) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:682) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:587) at hudson.model.Run.execute(Run.java:1568) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Caused by: java.io.IOException: Remote call on win8-tmp failed at hudson.remoting.Channel.call(Channel.java:681) at hudson.FilePath.act(FilePath.java:854) ... 10 more Caused by: java.lang.OutOfMemoryError: PermGen space This message is automatically generated by JIRA. 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-16746) Unable to send email since Jenkins 1.500
Alex Earl commented on JENKINS-16746 Unable to send email since Jenkins 1.500 René, You must not know how frustrating it is to try and develop an plugin on my own time, with no pay and have to deal with a constantly changing target for features and issues. Most plugins are geared to work with the LTS version of Jenkins just for this reason. I'm sorry you are having an issue, if you want to reopen the issue, that is fine, I probably won't be able to get to it very soon. Feel free to debug and submit a pull request if you want to. Alex This message is automatically generated by JIRA. 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
Kavita, I agree. I need to determine how best to do what you want. One workaround I might propose for now would be to generate a file with the ${FILE, path="real_path_here"} when you know the env variable works to specify the path to the file. Then use that generated file in the email template, the FILE token allows for nested content, so it should read the file, then replace the FILE token inside with the content you are looking for. Let me know if you need more information.
This message is automatically generated by JIRA.
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-16746) Unable to send email since Jenkins 1.500
Ravi Teja Lokineni reopened JENKINS-16746 Unable to send email since Jenkins 1.500 In that case, lets just keep it open if someone wants to fix it. Change By: Ravi Teja Lokineni (12/Feb/13 12:31 PM) Resolution: WontFix Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-16775) Deployment fails with java.lang.SecurityException: class org.kohsuke.args4j.XmlParser$ArgumentImpl's signer information does not match signer information of other classes in
Thomas Poisl created JENKINS-16775 Deployment fails with java.lang.SecurityException: class org.kohsuke.args4j.XmlParser$ArgumentImpls signer information does not match signer information of other classes in the same package Issue Type: Bug Assignee: Unassigned Components: core Created: 12/Feb/13 12:39 PM Description: We are running Jenkins in JBoss 6.0.0 here, but deployment of 1.500 or 1.501 fails with the following error: DEPLOYMENTS IN ERROR: Deployment "vfs:///srv/jboss/server/default/deploy/jenkins.war" is in error due to the following reason(s): java.lang.SecurityException: class "org.kohsuke.args4j.XmlParser$ArgumentImpl"'s signer information does not match signer information of other classes in the same package at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1228) [:2.2.0.GA] at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:905) [:2.2.0.GA] at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.checkComplete(MainDeployerPlugin.java:87) [:6.0.0.Final] at org.jboss.profileservice.deployment.ProfileDeployerPluginRegistry.checkAllComplete(ProfileDeployerPluginRegistry.java:107) [:0.2.2] at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:135) [:6.0.0.Final] at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:56) [:6.0.0.Final] at org.jboss.bootstrap.impl.base.server.AbstractServer.startBootstraps(AbstractServer.java:827) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5] at org.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask.run(AbstractServer.java:417) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5] at java.lang.Thread.run(Thread.java:662) [:1.6.0_31] Since I could not find any information about this problem, it might be related to one of the plug-ins we are using: Name ↓ Version Enabled Pinned mailer 1.4 true false external-monitor-job 1.1 true false ldap 1.2 true true pam-auth 1.0 true false ant 1.1 true false javadoc 1.0 true false cvs 2.7 true true jmeter 0.3.0 true false token-macro 1.5.1 true false maven-plugin 1.499 true false m2-extra-steps 1.1.7 true false groovy 1.12 true false postbuild-task 1.8 true false googleanalytics 1.3 true false m2release 0.9.1 true false twitter 0.6 true false downstream-ext 1.7 true false batch-task 1.16 true false scis-ad 1.2 true false chucknorris 0.5 true false dashboard-view 2.4 true false cobertura 1.8 true false xunit 1.52 true false performance 1.8 true false analysis-core 1.48 true false email-ext 2.25 true false PrioritySorter 1.3 true false subversion 1.45 true true configurationslicing 1.36 true false maven-metadata-plugin 1.0.0 true false perfpublisher 7.97 true false deploy 1.9 true false dynamic-axis 1.0.1 true false job-poll-action-plugin 1.0 true false m2-repo-reaper 1.0 true false matrixtieparent 1.1 true false ruby-runtime 0.10 true false pathignore 0.6 true false tasks 4.35 true false checkstyle 3.32 true false findbugs 4.45 true false violations 0.7.11 true false pmd 3.33 true false warnings 4.21 true false ci-game 1.19 true false insight-ci 2.3.3 true false maven-repo-cleaner 1.2 true false parameterized-trigger 2.16 true false git 1.1.26 true false git-server 1.1 true false scriptler 2.5.1 true false publish-over-ssh 1.9 true false dry 2.33 true false analysis-collector 1.34 true false emma 1.29 true false android-lint 2.0.2 true false dynamicparameter 0.2.0 true false jira 1.35 true false envinject 1.82 true false matrix-reloaded 1.1.0 true false clone-workspace-scm 0.5 true false xvnc 1.11 true false sonatype-ci 1.3 true false groovyaxis 0.3 true false copyartifact 1.25 true false translation 1.10 true true port-allocator 1.5 true false measurement-plots 0.1 true false android-emulator 2.8 true false template-project 1.3 true false plot 1.5 true false locale 1.2 true false artifactory 2.1.4 true false lastfailureversioncolumn 1.1 true false
[JIRA] (JENKINS-16775) Deployment fails with java.lang.SecurityException: class org.kohsuke.args4j.XmlParser$ArgumentImpl's signer information does not match signer information of other classes in
Thomas Poisl updated JENKINS-16775 Deployment fails with java.lang.SecurityException: class org.kohsuke.args4j.XmlParser$ArgumentImpls signer information does not match signer information of other classes in the same package Change By: Thomas Poisl (12/Feb/13 12:40 PM) Environment: Deplyoment und with Jenkins1.499runs,whileJenkins1.500and1.501fails This message is automatically generated by JIRA. 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-16775) Deployment fails with java.lang.SecurityException: class org.kohsuke.args4j.XmlParser$ArgumentImpl's signer information does not match signer information of other classes in
Thomas Poisl
updated JENKINS-16775
Deployment fails with java.lang.SecurityException: class org.kohsuke.args4j.XmlParser$ArgumentImpls signer information does not match signer information of other classes in the same package
Change By:
Thomas Poisl
(12/Feb/13 12:47 PM)
Environment:
Deplyoment
Deployment
withJenkins1.499
runs
works
,whileJenkins1.500and1.501
fails
failtodeploy
Description:
WearerunningJenkinsinJBoss6.0.0here,butdeploymentof
Jenkins
1.500or1.501failswiththefollowingerror:{noformat}DEPLOYMENTSINERROR:Deploymentvfs:///srv/jboss/server/default/deploy/jenkins.warisinerrorduetothefollowingreason(s):java.lang.SecurityException:classorg.kohsuke.args4j.XmlParser$ArgumentImplssignerinformationdoesnotmatchsignerinformationofotherclassesinthesamepackageatorg.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1228)[:2.2.0.GA]atorg.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:905)[:2.2.0.GA]atorg.jboss.system.server.profileservice.deployers.MainDeployerPlugin.checkComplete(MainDeployerPlugin.java:87)[:6.0.0.Final]atorg.jboss.profileservice.deployment.ProfileDeployerPluginRegistry.checkAllComplete(ProfileDeployerPluginRegistry.java:107)[:0.2.2]atorg.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:135)[:6.0.0.Final]atorg.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:56)[:6.0.0.Final]atorg.jboss.bootstrap.impl.base.server.AbstractServer.startBootstraps(AbstractServer.java:827)[jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]atorg.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask.run(AbstractServer.java:417)[jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]atjava.lang.Thread.run(Thread.java:662)[:1.6.0_31]{noformat}SinceIcouldnotfindanyinformationaboutthisproblem,itmightberelatedtooneoftheplug-insweareusing:{noformat}Name↓ Version Enabled Pinnedmailer 1.4 true falseexternal-monitor-job 1.1 true falseldap 1.2 true truepam-auth 1.0 true falseant 1.1 true falsejavadoc 1.0 true falsecvs 2.7 true truejmeter 0.3.0 true falsetoken-macro 1.5.1 true falsemaven-plugin 1.499 true falsem2-extra-steps 1.1.7 true falsegroovy 1.12 true falsepostbuild-task 1.8 true falsegoogleanalytics 1.3 true falsem2release 0.9.1 true falsetwitter 0.6 true falsedownstream-ext 1.7 true falsebatch-task 1.16 true falsescis-ad 1.2 true falsechucknorris 0.5 true falsedashboard-view 2.4 true falsecobertura 1.8 true falsexunit 1.52 true falseperformance 1.8 true falseanalysis-core 1.48 true falseemail-ext 2.25 true falsePrioritySorter 1.3 true falsesubversion 1.45 true trueconfigurationslicing 1.36 true falsemaven-metadata-plugin 1.0.0 true falseperfpublisher 7.97 true falsedeploy 1.9 true falsedynamic-axis 1.0.1 true falsejob-poll-action-plugin 1.0 true falsem2-repo-reaper 1.0 true falsematrixtieparent 1.1 true falseruby-runtime 0.10 true falsepathignore 0.6 true falsetasks 4.35 true falsecheckstyle 3.32 true falsefindbugs 4.45 true falseviolations 0.7.11 true falsepmd 3.33 true falsewarnings 4.21 true falseci-game 1.19 true falseinsight-ci 2.3.3 true falsemaven-repo-cleaner 1.2 true falseparameterized-trigger 2.16 true falsegit 1.1.26 true falsegit-server 1.1 true falsescriptler 2.5.1 true falsepublish-over-ssh 1.9 true falsedry 2.33 true falseanalysis-collector 1.34 true falseemma 1.29 true falseandroid-lint 2.0.2 true falsedynamicparameter 0.2.0 true falsejira 1.35 true falseenvinject 1.82 true falsematrix-reloaded 1.1.0 true falseclone-workspace-scm 0.5 true falsexvnc 1.11 true falsesonatype-ci 1.3 true falsegroovyaxis 0.3 true falsecopyartifact 1.25 true falsetranslation 1.10 true trueport-allocator 1.5 true falsemeasurement-plots 0.1 true falseandroid-emulator 2.8 true falsetemplate-project 1.3 true falseplot 1.5 true falselocale 1.2 true falseartifactory 2.1.4 true falselastfailureversioncolumn 1.1 true falsetestng-plugin 1.1 true falsetestlink 3.1.8 true falsessh-slaves 0.22 true truelastsuccessversioncolumn 1.1 true false{noformat}
[JIRA] (JENKINS-16775) Deployment fails with java.lang.SecurityException: class org.kohsuke.args4j.XmlParser$ArgumentImpl's signer information does not match signer information of other classes in
Thomas Poisl updated JENKINS-16775 Deployment fails with java.lang.SecurityException: class org.kohsuke.args4j.XmlParser$ArgumentImpls signer information does not match signer information of other classes in the same package Change By: Thomas Poisl (12/Feb/13 12:52 PM) Priority: Critical Blocker This message is automatically generated by JIRA. 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-16776) surefire-reports not detected for android-maven-plugin
Richard Mortimer
created JENKINS-16776
surefire-reports not detected for android-maven-plugin
Issue Type:
Bug
Affects Versions:
current
Assignee:
Richard Mortimer
Components:
maven2
Created:
12/Feb/13 1:20 PM
Description:
Recent Jenkins releases have stopped detecting the test results produced by android-maven-plugin. This seems to be due to the refactoring done as part of the fix for JENKINS-8334.
After digging into the failure the problem is due to the reportsDir fallback code that gets executed if the mojo does not support a reportsDirectory config value.
Specifically (from SurefireArchiver.java and now TestMojo.java)
if (reportsDir == null) {
// if test mojo doesn't have such config value, still almost all
// default to target/surefire-reports
reportsDir = new File(pom.getBasedir(),
pom.getBuild().getDirectory()+File.separator+"surefire-reports");
return true;
}
The code was moved between files during the fix but was not altered. It looks like the maven-android-plugin code is now falling through to that
and exposing a bug in the old code.
Basically pom.getBuild().getDirectory() returns a full path to the build directory and not just the bare directory name (usually "target").
See http://stackoverflow.com/questions/9318935/get-project-build-directory-from-mavenproject
I have tested a proposed fix (pull request coming soon) and it works in my environment.
Environment:
Ubuntu 12.04 Jenkins 1.500
Project:
Jenkins
Priority:
Major
Reporter:
Richard Mortimer
This message is automatically generated by JIRA.
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-16777) ArrayIndexOutOfBoundsException when trying to publish the Jacoco report
Mario Hochreiter created JENKINS-16777 ArrayIndexOutOfBoundsException when trying to publish the Jacoco report Issue Type: Bug Affects Versions: current Assignee: Ognjen Bubalo Components: jacoco Created: 12/Feb/13 1:21 PM Description: JaCoCo plugin Collecting JaCoCo coverage data... JaCoCo plugin */target/.exec;/target/classes;*/src/main/java; locations are configured JaCoCo plugin Number of found exec files: 1 JaCoCo plugin Saving matched execfiles: /var/jenkins/workspace/fxtb-dev-Trade/target/jacoco.exec JaCoCo plugin Saving matched class directories: /var/jenkins/workspace/fxtb-dev-Trade/target/classes JaCoCo plugin Saving matched source directories: /var/jenkins/workspace/fxtb-dev-Trade/src/main/java JaCoCo plugin Loading inclusions files.. ERROR: Publisher hudson.plugins.jacoco.JacocoPublisher aborted due to exception java.lang.ArrayIndexOutOfBoundsException: 0 at hudson.plugins.jacoco.ExecutionFileLoader.analyzeStructure(ExecutionFileLoader.java:117) at hudson.plugins.jacoco.ExecutionFileLoader.loadBundleCoverage(ExecutionFileLoader.java:137) at hudson.plugins.jacoco.JacocoBuildAction.getJacocoReports(JacocoBuildAction.java:249) at hudson.plugins.jacoco.JacocoBuildAction.loadRatios(JacocoBuildAction.java:332) at hudson.plugins.jacoco.JacocoBuildAction.load(JacocoBuildAction.java:313) at hudson.plugins.jacoco.JacocoPublisher.perform(JacocoPublisher.java:363) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:807) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:782) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:994) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:729) at hudson.model.Run.execute(Run.java:1541) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Performing Post build task... Project: Jenkins Priority: Major Reporter: Mario Hochreiter This message is automatically generated by JIRA. 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-16316) global variable not updated
SCM/JIRA link daemon commented on JENKINS-16316 global variable not updated Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/plugins/envinject/EnvInjectComputerListener.java src/main/java/org/jenkinsci/plugins/envinject/service/EnvInjectEnvVars.java http://jenkins-ci.org/commit/envinject-plugin/9e27cf40040a15cf67c1fc64bab90d28f2bc43e4 Log: Fix reopen JENKINS-16316 You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. 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-16754) $JOB_NAME is set to some autogenerated string instead of the project name
Gregory Boissinot commented on JENKINS-16754 $JOB_NAME is set to some autogenerated string instead of the project name Could you try to isolate the problem? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-16770) missing build title in /rssAll when build has no test result
Richard Mortimer commented on JENKINS-16770 missing build title in /rssAll when build has no test result See pull request https://github.com/jenkinsci/jenkins/pull/703 This message is automatically generated by JIRA. 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-16766) Claim plugin no longer renders HTML in Reason field after upgrade from 1.7 to 2.0
SCM/JIRA link daemon commented on JENKINS-16766 Claim plugin no longer renders HTML in Reason field after upgrade from 1.7 to 2.0 Code changed in jenkins User: ki82 Path: .gitignore src/main/java/hudson/plugins/claim/AbstractClaimBuildAction.java src/main/java/hudson/plugins/claim/ClaimBuildAction.java src/main/java/hudson/plugins/claim/ClaimListener.java src/main/java/hudson/plugins/claim/ClaimTestAction.java src/main/java/hudson/plugins/claim/ClaimTestDataPublisher.java src/main/java/hudson/plugins/claim/ClaimedBuildsReport.java src/main/resources/hudson/plugins/claim/AbstractClaimBuildAction/badge.jelly src/main/resources/hudson/plugins/claim/AbstractClaimBuildAction/summary.jelly src/main/resources/hudson/plugins/claim/ClaimTestDataPublisher/config.jelly http://jenkins-ci.org/commit/claim-plugin/a2f12da452cd3116436b1fc335f85aa1d69d541f Log: Reverted merge 7e8a50d6c631a9e0849327a01e23a7142c6b45f9 by huybrechts because of JENKINS-16766 You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. 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-16571) Optimize http requests for static resources in the analysis plugins
SCM/JIRA link daemon commented on JENKINS-16571 Optimize http requests for static resources in the analysis plugins Code changed in jenkins User: Ulli Hafner Path: pom.xml src/main/java/hudson/plugins/analysis/core/AbstractProjectAction.java src/main/java/hudson/plugins/analysis/core/AbstractResultAction.java src/main/java/hudson/plugins/analysis/core/BuildResult.java http://jenkins-ci.org/commit/analysis-core-plugin/5c7bcfb3959873569d545c3adbcf682791af4a95 Log: JENKINS-16571 Prefix all static icon URLs with RESOURCE_PREFIX. You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. 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-16774) URLTrigger gives severe error message instead of detecting change
SCM/JIRA link daemon commented on JENKINS-16774 URLTrigger gives severe error message instead of detecting change Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/lib/envinject/service/EnvInjectActionRetriever.java http://jenkins-ci.org/commit/envinject-lib/5675c2ae27644e85eabd14237603a995c90d5a99 Log: Fix JENKINS-16774 You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. 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-16766) Claim plugin no longer renders HTML in Reason field after upgrade from 1.7 to 2.0
Christian Åkerström resolved JENKINS-16766 as Fixed Claim plugin no longer renders HTML in Reason field after upgrade from 1.7 to 2.0 Change By: Christian Åkerström (12/Feb/13 1:49 PM) Status: InProgress Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-16766) Claim plugin no longer renders HTML in Reason field after upgrade from 1.7 to 2.0
Christian Åkerström closed JENKINS-16766 as Fixed Claim plugin no longer renders HTML in Reason field after upgrade from 1.7 to 2.0 Change By: Christian Åkerström (12/Feb/13 1:50 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-2548) Node does not come back online after disk space cleared
Marc Günther resolved JENKINS-2548 as Fixed Node does not come back online after disk space cleared Fixed by pull request 514: https://github.com/jenkinsci/jenkins/pull/514 Change By: Marc Günther (12/Feb/13 1:52 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-12882) Master stays offline if once low disk space occured
Marc Günther resolved JENKINS-12882 as Fixed Master stays offline if once low disk space occured Fixed by pull request 514: https://github.com/jenkinsci/jenkins/pull/514 Change By: Marc Günther (12/Feb/13 1:52 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-12021) Slave node does not made online if it gets above a certain threshold
Marc Günther resolved JENKINS-12021 as Fixed Slave node does not made online if it gets above a certain threshold Fixed by pull request 514: https://github.com/jenkinsci/jenkins/pull/514 Change By: Marc Günther (12/Feb/13 1:52 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-16774) URLTrigger gives severe error message instead of detecting change
Magnus Jacobsson updated JENKINS-16774 URLTrigger gives severe error message instead of detecting change Change By: Magnus Jacobsson (12/Feb/13 1:59 PM) Component/s: envinject Component/s: urltrigger This message is automatically generated by JIRA. 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-16571) Optimize http requests for static resources in the analysis plugins
SCM/JIRA link daemon
commented on JENKINS-16571
Optimize http requests for static resources in the analysis plugins
Code changed in jenkins
User: Ulli Hafner
Path:
pom.xml
src/main/resources/hudson/plugins/analysis/collector/dashboard/WarningsTablePortlet/portlet.jelly
http://jenkins-ci.org/commit/analysis-collector-plugin/441ec6184e3d27141bbfd5217d14e49d37a7886c
Log:
JENKINS-16571 Use ${resUrl} rather than rootUrl for static icon URLs.
You received this message because you are subscribed to the Google Groups "Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
This message is automatically generated by JIRA.
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-16571) Optimize http requests for static resources in the analysis plugins
SCM/JIRA link daemon resolved JENKINS-16571 as Fixed Optimize http requests for static resources in the analysis plugins Change By: SCM/JIRA link daemon (12/Feb/13 2:09 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-16571) Optimize http requests for static resources in the analysis plugins
SCM/JIRA link daemon
commented on JENKINS-16571
Optimize http requests for static resources in the analysis plugins
Code changed in jenkins
User: Ulli Hafner
Path:
src/main/resources/result/main.jelly
src/main/resources/util/graphtype.jelly
src/main/resources/util/health.jelly
src/main/resources/util/thresholds.jelly
http://jenkins-ci.org/commit/analysis-core-plugin/2be77cf07e08012b3574c64839d5c96244c914cc
Log:
FIXED JENKINS-16571 Use ${resUrl} for static icon URLs.
You received this message because you are subscribed to the Google Groups "Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
This message is automatically generated by JIRA.
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-16775) Deployment fails with java.lang.SecurityException: class org.kohsuke.args4j.XmlParser$ArgumentImpl's signer information does not match signer information of other classes in
Thomas Poisl
updated JENKINS-16775
Deployment fails with java.lang.SecurityException: class org.kohsuke.args4j.XmlParser$ArgumentImpls signer information does not match signer information of other classes in the same package
Change By:
Thomas Poisl
(12/Feb/13 3:02 PM)
Description:
WearerunningJenkinsinJBoss6.0.0here,butdeploymentofJenkins1.500or1.501failswiththefollowingerror:{noformat}DEPLOYMENTSINERROR:Deploymentvfs:///srv/jboss/server/default/deploy/jenkins.warisinerrorduetothefollowingreason(s):java.lang.SecurityException:classorg.kohsuke.args4j.XmlParser$ArgumentImplssignerinformationdoesnotmatchsignerinformationofotherclassesinthesamepackageatorg.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1228)[:2.2.0.GA]atorg.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:905)[:2.2.0.GA]atorg.jboss.system.server.profileservice.deployers.MainDeployerPlugin.checkComplete(MainDeployerPlugin.java:87)[:6.0.0.Final]atorg.jboss.profileservice.deployment.ProfileDeployerPluginRegistry.checkAllComplete(ProfileDeployerPluginRegistry.java:107)[:0.2.2]atorg.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:135)[:6.0.0.Final]atorg.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:56)[:6.0.0.Final]atorg.jboss.bootstrap.impl.base.server.AbstractServer.startBootstraps(AbstractServer.java:827)[jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]atorg.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask.run(AbstractServer.java:417)[jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]atjava.lang.Thread.run(Thread.java:662)[:1.6.0_31]{noformat}SinceIcouldnotfindanyinformationaboutthisproblem,itmightberelatedtooneoftheplug-insweareusing:{noformat}Name↓ Version Enabled Pinnedmailer 1.4 true falseexternal-monitor-job 1.1 true falseldap 1.2 true truepam-auth 1.0 true falseant 1.1 true falsejavadoc 1.0 true falsecvs 2.7 true truejmeter 0.3.0 true falsetoken-macro 1.5.1 true falsemaven-plugin 1.499 true falsem2-extra-steps 1.1.7 true falsegroovy 1.12 true falsepostbuild-task 1.8 true falsegoogleanalytics 1.3 true falsem2release 0.9.1 true falsetwitter 0.6 true falsedownstream-ext 1.7 true falsebatch-task 1.16 true falsescis-ad 1.2 true falsechucknorris 0.5 true falsedashboard-view 2.4 true falsecobertura 1.8 true falsexunit 1.52 true falseperformance 1.8 true falseanalysis-core 1.48 true falseemail-ext 2.25 true falsePrioritySorter 1.3 true falsesubversion 1.45 true trueconfigurationslicing 1.36 true falsemaven-metadata-plugin 1.0.0 true falseperfpublisher 7.97 true falsedeploy 1.9 true falsedynamic-axis 1.0.1 true falsejob-poll-action-plugin 1.0 true falsem2-repo-reaper 1.0 true falsematrixtieparent 1.1 true falseruby-runtime 0.10 true falsepathignore 0.6 true falsetasks 4.35 true falsecheckstyle 3.32 true falsefindbugs 4.45 true falseviolations 0.7.11 true falsepmd 3.33 true falsewarnings 4.21 true falseci-game 1.19 true falseinsight-ci 2.3.3 true falsemaven-repo-cleaner 1.2 true falseparameterized-trigger 2.16 true falsegit 1.1.26 true falsegit-server 1.1 true falsescriptler 2.5.1 true falsepublish-over-ssh 1.9 true falsedry 2.33 true falseanalysis-collector 1.34 true falseemma 1.29 true falseandroid-lint 2.0.2 true falsedynamicparameter 0.2.0 true falsejira 1.35 true falseenvinject 1.82 true falsematrix-reloaded 1.1.0 true falseclone-workspace-scm 0.5 true falsexvnc 1.11 true falsesonatype-ci 1.3 true falsegroovyaxis 0.3 true falsecopyartifact 1.25 true falsetranslation 1.10 true trueport-allocator 1.5 true falsemeasurement-plots 0.1 true falseandroid-emulator 2.8 true falsetemplate-project 1.3 true falseplot 1.5 true falselocale 1.2 true falseartifactory 2.1.4 true falselastfailureversioncolumn 1.1 true falsetestng-plugin 1.1 true falsetestlink 3.1.8 true falsessh-slaves 0.22 true truelastsuccessversioncolumn 1.1 true false
rebuild 1.17 true false
{noformat}
This message is automatically generated by JIRA.
If you think it was sent incorrectly,
[JIRA] (JENKINS-16518) Warning summary gone after plugin update
SCM/JIRA link daemon commented on JENKINS-16518 Warning summary gone after plugin update Code changed in jenkins User: Ulli Hafner Path: pom.xml src/main/resources/hudson/plugins/analysis/core/MavenResultAction/summary.jelly http://jenkins-ci.org/commit/analysis-core-plugin/9590aa5ca31cd27ecd6a2c5e51fba1d89032d222 Log: FIXED JENKINS-16518 Restored missing summary view in Maven 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-16518) Warning summary gone after plugin update
SCM/JIRA link daemon resolved JENKINS-16518 as Fixed Warning summary gone after plugin update Change By: SCM/JIRA link daemon (12/Feb/13 3:19 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-15959) Adding detail to the 'Fixed Warnings' screen
SCM/JIRA link daemon resolved JENKINS-15959 as Fixed Adding detail to the Fixed Warnings screen Change By: SCM/JIRA link daemon (12/Feb/13 3:19 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-15959) Adding detail to the 'Fixed Warnings' screen
SCM/JIRA link daemon commented on JENKINS-15959 Adding detail to the Fixed Warnings screen Code changed in jenkins User: Ulli Hafner Path: src/main/resources/result/fixed.jelly http://jenkins-ci.org/commit/analysis-core-plugin/1081a0146c70a999e3961557bfa2510c5a1ccdf4 Log: FIXED JENKINS-15959 Added some more details to fixed warnings view. Compare: https://github.com/jenkinsci/analysis-core-plugin/compare/2be77cf07e08...1081a0146c70 You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. 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-16288) CheckStyle Plugin for Jenkins
Ulli Hafner resolved JENKINS-16288 as Incomplete CheckStyle Plugin for Jenkins Please reopen if you have more details on this issue. Change By: Ulli Hafner (12/Feb/13 3:20 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16760) Sauce Connect no longer works
R. Tyler Croy assigned JENKINS-16760 to Ross Rowe Sauce Connect no longer works This was incorrectly automatically assigned earlier. Hilfe Ross! Change By: R. Tyler Croy (12/Feb/13 3:49 PM) Assignee: KohsukeKawaguchi RossRowe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-16776) surefire-reports not detected for android-maven-plugin
Richard Mortimer commented on JENKINS-16776 surefire-reports not detected for android-maven-plugin See pull request https://github.com/jenkinsci/jenkins/pull/704 This message is automatically generated by JIRA. 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-16776) surefire-reports not detected for android-maven-plugin
SCM/JIRA link daemon commented on JENKINS-16776 surefire-reports not detected for android-maven-plugin Code changed in jenkins User: Richard Mortimer Path: changelog.html maven-plugin/src/main/java/hudson/maven/reporters/TestMojo.java maven-plugin/src/test/java/hudson/maven/reporters/TestMojoTest.java http://jenkins-ci.org/commit/jenkins/981366696199a73980fcc9218b93afe15faad189 Log: FIXED JENKINS-16776 surefire-reports not detected for android-maven-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16776) surefire-reports not detected for android-maven-plugin
SCM/JIRA link daemon resolved JENKINS-16776 as Fixed surefire-reports not detected for android-maven-plugin Change By: SCM/JIRA link daemon (12/Feb/13 4:08 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-16776) surefire-reports not detected for android-maven-plugin
SCM/JIRA link daemon commented on JENKINS-16776 surefire-reports not detected for android-maven-plugin Code changed in jenkins User: Christoph Kutzinski Path: changelog.html maven-plugin/src/main/java/hudson/maven/reporters/TestMojo.java maven-plugin/src/test/java/hudson/maven/reporters/TestMojoTest.java http://jenkins-ci.org/commit/jenkins/1d3521c73cbcea86e1ea0acc1215861bd4c87070 Log: Merge pull request #704 from oldelvet/jenkins-16776 FIXED JENKINS-16776 surefire-reports not detected for android-maven-plugin Compare: https://github.com/jenkinsci/jenkins/compare/adeed34c6c56...1d3521c73cbc You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. 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-16776) surefire-reports not detected for android-maven-plugin
kutzi commented on JENKINS-16776 surefire-reports not detected for android-maven-plugin I still struggle to understand why it used to work before my refactoring. Can you explain why? This message is automatically generated by JIRA. 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-16778) Timestamper makes the build fail if the slave if put offline during the build.
Vincent Latombe created JENKINS-16778 Timestamper makes the build fail if the slave if put offline during the build. Issue Type: Bug Assignee: stevengbrown Components: timestamper Created: 12/Feb/13 4:17 PM Description: If a slave is put offline during a running build, the timestamper plugin issues a NPE at the end of the build, marking the build as failed. The stacktrace is the following 17:11:18 Looks like the node went offline during the build. Check the slave log for the details.FATAL: null 17:11:18 java.lang.NullPointerException 17:11:18 at hudson.plugins.timestamper.TimestampFormatter.init(TimestampFormatter.java:71) 17:11:20 at hudson.plugins.timestamper.TimestamperConfig$1.get(TimestamperConfig.java:59) 17:11:20 at hudson.plugins.timestamper.TimestamperConfig$1.get(TimestamperConfig.java:54) 17:11:20 at hudson.plugins.timestamper.TimestamperConfig.formatter(TimestamperConfig.java:148) 17:11:20 at hudson.plugins.timestamper.annotator.TimestampAnnotatorFactory.newInstance(TimestampAnnotatorFactory.java:51) 17:11:20 at hudson.console.ConsoleAnnotator._for(ConsoleAnnotator.java:143) 17:11:20 at hudson.console.ConsoleAnnotator.initial(ConsoleAnnotator.java:133) 17:11:20 at hudson.console.AnnotatedLargeText.createAnnotator(AnnotatedLargeText.java:138) 17:11:20 at hudson.console.AnnotatedLargeText.writeHtmlTo(AnnotatedLargeText.java:155) 17:11:20 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:605) 17:11:20 at hudson.model.Run.execute(Run.java:1543) 17:11:20 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) 17:11:20 at hudson.model.ResourceController.execute(ResourceController.java:88) 17:11:20 at hudson.model.Executor.run(Executor.java:236) Project: Jenkins Priority: Major Reporter: Vincent Latombe This message is automatically generated by JIRA. 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-16776) surefire-reports not detected for android-maven-plugin
Richard Mortimer
commented on JENKINS-16776
surefire-reports not detected for android-maven-plugin
I didn't look into that too deeply. I can only assume that somehow reportsDirectory is set for android-maven-plugin (although I can't find it in my copy of the source - which is about 6 months old) and hence it never fell through to the fallback mechanism.
That seems to just have been luck because the code does hardcode the output as follows in AbstractInstrumentationMojo.java
String directory = new StringBuilder()
.append(project.getBuild().getDirectory())
.append("/surefire-reports")
.toString();
This message is automatically generated by JIRA.
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-16779) PROPFILE token does not evaluate in the Editable E-mail Notification for the email-ext plugin
Kavita Tiwari
created JENKINS-16779
PROPFILE token does not evaluate in the Editable E-mail Notification for the email-ext plugin
Issue Type:
Bug
Affects Versions:
current
Assignee:
Alex Earl
Components:
email-ext, token-macro
Created:
12/Feb/13 4:55 PM
Description:
The PROPFILE token is not evaluating in the Editable E-mail Notification for the e-mail-ext plugin.
For example, when I put this in the Default Content of the e-mail:
${PROPFILE,file="props.cfg",property="TESTING_VAR"}
The value of "TESTING_VAR" is not displayed in the e-mail. Instead, this is displayed:
${PROPFILE,file="props.cfg",property="TESTING_VAR"}
This PROPFILE token works when I put it in the "Set Build Name" field for the build-name-setter plugin.
So the build-name-setter plugin is able to consume the PROPFILE token, but the e-mail-ext plugin does not seem to be consuming it properly.
I am running Jenkins 1.480.2 with email-ext - 2.24.1.
Due Date:
19/Feb/13 12:00 AM
Project:
Jenkins
Priority:
Minor
Reporter:
Kavita Tiwari
This message is automatically generated by JIRA.
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-16779) PROPFILE token does not evaluate in the Editable E-mail Notification for the email-ext plugin
Alex Earl commented on JENKINS-16779 PROPFILE token does not evaluate in the Editable E-mail Notification for the email-ext plugin PROPFILE is not an email-ext token, so it won't be consumed. This message is automatically generated by JIRA. 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-16250) change of checkstyle-result.xml folder by changing outputFile parameter leading to zero warnings in trend graph
SCM/JIRA link daemon commented on JENKINS-16250 change of checkstyle-result.xml folder by changing outputFile parameter leading to zero warnings in trend graph Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/analysis/core/FilesParser.java http://jenkins-ci.org/commit/analysis-core-plugin/7e79c797876da4c70d75ba913f7506718a33e13a Log: JENKINS-16250 Introduced new constructor to parse a single file only. Compare: https://github.com/jenkinsci/analysis-core-plugin/compare/1081a0146c70...7e79c797876d You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. 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-15959) Adding detail to the 'Fixed Warnings' screen
SCM/JIRA link daemon commented on JENKINS-15959 Adding detail to the Fixed Warnings screen Code changed in jenkins User: Ulli Hafner Path: src/main/resources/result/fixed_de.properties http://jenkins-ci.org/commit/analysis-core-plugin/ccb17f9e870d6a2253c509948ff13bd4ef214fb7 Log: JENKINS-15959 Added German localization. This message is automatically generated by JIRA. 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-15078) Be able to set Instance Name
SCM/JIRA link daemon commented on JENKINS-15078 Be able to set Instance Name Code changed in jenkins User: Kevin P. Fleming Path: src/main/java/hudson/plugins/ec2/EC2Computer.java src/main/java/hudson/plugins/ec2/EC2Slave.java src/main/java/hudson/plugins/ec2/SlaveTemplate.java http://jenkins-ci.org/commit/ec2-plugin/88222567e84ae42c602d5ac8430a95957ea083e3 Log: Give Jenkins nodes useful names. EC2 slave nodes will now include their template name and EC2 instance identifiers in the node name used throughout the Jenkins UI. Addresses JENKINS-15078. This message is automatically generated by JIRA. 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-16777) ArrayIndexOutOfBoundsException when trying to publish the Jacoco report
Ognjen Bubalo commented on JENKINS-16777 ArrayIndexOutOfBoundsException when trying to publish the Jacoco report Hi Mario, Thanks for the report. It is an exception to catch, but you have a mistake in your configuration. The Path to exec files should be: */target/*.exec Cheers, Ogi This message is automatically generated by JIRA. 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-16696) Integration test results not displayed since 1.500
Guillaume Bilodeau updated JENKINS-16696 Integration test results not displayed since 1.500 Result of running mvn help:effective-pom on the test project. Change By: Guillaume Bilodeau (12/Feb/13 5:59 PM) Attachment: effective-pom.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-16696) Integration test results not displayed since 1.500
Guillaume Bilodeau edited a comment on JENKINS-16696 Integration test results not displayed since 1.500 Result of running mvn help:effective-pom on the test project attached to this 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-12207) get warnings in log
William Roberts commented on JENKINS-12207 get warnings in log This is caused by job classes which aren't in the standard set (i.e. FreeStyleProject, MavenModuleSet, MatrixProject), for example a MultiJob. It should be possible to fix this by assuming that Job implements SubTask and therefore has a getAssignedLabel() method. This message is automatically generated by JIRA. 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-16696) Integration test results not displayed since 1.500
kutzi commented on JENKINS-16696 Integration test results not displayed since 1.500 If you have no problem with trying a snapshot build you might want to try the Jenkins build attached to this https://ci.jenkins-ci.org/job/jenkins_main_trunk/2263/ Exchanging the maven plugin should be enough, but make sure that it's 'pinned'. This message is automatically generated by JIRA. 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-16696) Integration test results not displayed since 1.500
kutzi commented on JENKINS-16696 Integration test results not displayed since 1.500 You didn't change the goal configuration for the failsafe plugin? Like changing it from verify to integration-test? This message is automatically generated by JIRA. 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-16776) surefire-reports not detected for android-maven-plugin
dogfood commented on JENKINS-16776 surefire-reports not detected for android-maven-plugin Integrated in jenkins_main_trunk #2267 Result = SUCCESS This message is automatically generated by JIRA. 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-16780) release build fails to deploy new SNAPSHOT pom artifact with 409 error
Kc Singh created JENKINS-16780 release build fails to deploy new SNAPSHOT pom artifact with 409 error Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: maven Created: 12/Feb/13 7:10 PM Description: release:perform is successful. But after that maven kicks clean up process and tries to commit the new snapshot in released version's snapshot repo in artifactory and fails with 409 error code. This release build released version 1.1.16. Then pom is incremented to 1.1.17-SNAPSHOT and during cleanup process, it tried to deploy 1.1.17-SNAPSHOT in 1.1.16-SNAPSHOT of lib-snapshot-local and failed with 409 error code. This test project has a parent which has ear and war modules within it. Parent pom fails to deploy. Here is the stack trace: INFO INFO Building jar: C:\Documents and Settings\n98743\.jenkins\workspace\jenkins release test\target\checkout\ear\target\release-test-through-jenkins-ear-1.1.16.ear INFO INFO INFO INFO maven-javadoc-plugin:2.9:jar (attach-javadocs) @ release-test-through-jenkins-ear INFO INFO INFO INFO maven-source-plugin:2.1.2:jar-no-fork (attach-sources) @ release-test-through-jenkins-ear INFO INFO No sources in project. Archive not created. INFO INFO INFO INFO maven-source-plugin:2.1.2:jar (attach-sources) @ release-test-through-jenkins-ear INFO INFO INFO INFO maven-source-plugin:2.1.2:jar (attach-sources) @ release-test-through-jenkins-ear INFO INFO INFO INFO maven-source-plugin:2.1.2:jar (attach-sources) @ release-test-through-jenkins-ear INFO INFO No sources in project. Archive not created. INFO INFO INFO INFO maven-install-plugin:2.3.1:install (default-install) @ release-test-through-jenkins-ear INFO INFO Installing C:\Documents and Settings\n98743\.jenkins\workspace\jenkins release test\target\checkout\ear\target\release-test-through-jenkins-ear-1.1.16.ear to C:\Documents and Settings\n98743\.m2\repository\com\es\release-test-through-jenkins-ear\1.1.16\release-test-through-jenkins-ear-1.1.16.ear INFO INFO Installing C:\Documents and Settings\n98743\.jenkins\workspace\jenkins release test\target\checkout\ear\pom.xml to C:\Documents and Settings\n98743\.m2\repository\com\es\release-test-through-jenkins-ear\1.1.16\release-test-through-jenkins-ear-1.1.16.pom INFO INFO INFO INFO maven-deploy-plugin:2.7:deploy (default-deploy) @ release-test-through-jenkins-ear INFO Uploading: http://servername:8080/artifactory/libs-release-local/com/es/release-test-through-jenkins-ear/1.1.16/release-test-through-jenkins-ear-1.1.16.ear INFO Uploaded: http://servername:8080/artifactory/libs-release-local/com/es/release-test-through-jenkins-ear/1.1.16/release-test-through-jenkins-ear-1.1.16.ear (3507 KB at 18652.8 KB/sec) INFO Uploading: http://servername:8080/artifactory/libs-release-local/com/es/release-test-through-jenkins-ear/1.1.16/release-test-through-jenkins-ear-1.1.16.pom INFO Uploaded: http://servername:8080/artifactory/libs-release-local/com/es/release-test-through-jenkins-ear/1.1.16/release-test-through-jenkins-ear-1.1.16.pom (2 KB at 25.7 KB/sec) INFO Downloading: http://servername:8080/artifactory/libs-release-local/com/es/release-test-through-jenkins-ear/maven-metadata.xml INFO Downloaded: http://servername:8080/artifactory/libs-release-local/com/es/release-test-through-jenkins-ear/maven-metadata.xml (637 B at 19.4 KB/sec) INFO Uploading: http://servername:8080/artifactory/libs-release-local/com/es/release-test-through-jenkins-ear/maven-metadata.xml INFO Uploaded: http://servername:8080/artifactory/libs-release-local/com/es/release-test-through-jenkins-ear/maven-metadata.xml (609 B at 19.2 KB/sec) INFO INFO INFO INFO Reactor Summary: INFO INFO INFO INFO release-test-through-jenkins .. SUCCESS 6.781s INFO INFO release-test-through-jenkins-webapp ... SUCCESS 5.187s INFO INFO release-test-through-jenkins-ear .. SUCCESS 1.453s INFO INFO
[JIRA] (JENKINS-16780) release build fails to deploy new SNAPSHOT pom artifact with 409 error
Kc Singh updated JENKINS-16780 release build fails to deploy new SNAPSHOT pom artifact with 409 error Change By: Kc Singh (12/Feb/13 7:16 PM) Due Date: 12/Feb/13 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16766) Claim plugin no longer renders HTML in Reason field after upgrade from 1.7 to 2.0
pickgr1 commented on JENKINS-16766 Claim plugin no longer renders HTML in Reason field after upgrade from 1.7 to 2.0 Thank you for such a quick fix! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16760) Sauce Connect no longer works
Ross Rowe started work on JENKINS-16760 Sauce Connect no longer works Change By: Ross Rowe (12/Feb/13 8:01 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-16696) Integration test results not displayed since 1.500
Guillaume Bilodeau commented on JENKINS-16696 Integration test results not displayed since 1.500 FailSafe is only bound to the integration-test goal right now, not the verify goal. I could bind it to both, although I must admit that I don't know what would be the impact of doing that. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-16696) Integration test results not displayed since 1.500
Guillaume Bilodeau
edited a comment on JENKINS-16696
Integration test results not displayed since 1.500
FailSafe is only bound to the integration-test goal right now, not the verify goal. I could bind it to both, although I must admit that I don't know what would be the impact of doing that.
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-failsafe-plugin/artifactId
version${maven-failsafe-plugin.version}/version
configuration
includes
include**/*AT.java/include
/includes
excludes
exclude**/*Test.java/exclude
/excludes
parallelclasses/parallel
threadCount4/threadCount
perCoreThreadCounttrue/perCoreThreadCount
/configuration
executions
execution
goals
goalintegration-test/goal
/goals
/execution
/executions
/plugin
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16781) Job and Project naming convention
Joris van der Pol created JENKINS-16781 Job and Project naming convention Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: core Created: 12/Feb/13 8:20 PM Description: Both 'Job' and 'Project' are used, but is unclear what the difference is. A new Job seems to create a Project and one can delete a Project but not a Job. One concept should be used in my opinion unless the difference is clearly distinguishable. Environment: Windows 7 Project: Jenkins Labels: job Priority: Trivial Reporter: Joris van der Pol This message is automatically generated by JIRA. 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-16782) Alignment master and slaves names in build executor status
Joris van der Pol created JENKINS-16782 Alignment master and slaves names in build executor status Issue Type: Improvement Affects Versions: current Assignee: Unassigned Attachments: build_executor_status.png Components: core Created: 12/Feb/13 8:24 PM Description: The names of master and slaves is not aligned in the build executor status panel. See the attachment. Environment: Windows 7 Project: Jenkins Priority: Trivial Reporter: Joris van der Pol This message is automatically generated by JIRA. 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-16614) Align master and slaves in Build Executer Status
Joris van der Pol closed JENKINS-16614 as Duplicate Align master and slaves in Build Executer Status I realised too late I already mentioned this before. Change By: Joris van der Pol (12/Feb/13 8:25 PM) Status: Open Closed Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-16760) Sauce Connect no longer works
Ross Rowe commented on JENKINS-16760 Sauce Connect no longer works I'm just deployed version 1.45 which should fix the NullPointerException. We recently updated the plugin to suppress spaces in the key used to represent the browser, so I think you might need to reselect the browser combination in the Jenkins Job configuration. Cheers, Ross This message is automatically generated by JIRA. 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-16696) Integration test results not displayed since 1.500
Guillaume Bilodeau commented on JENKINS-16696 Integration test results not displayed since 1.500 Maybe the problem was introduced before 1.500 - the last version I tried was 1.491 and it was working fine. This message is automatically generated by JIRA. 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-15158) Sometimes starts the wrong instance
SCM/JIRA link daemon commented on JENKINS-15158 Sometimes starts the wrong instance Code changed in jenkins User: Kevin P. Fleming Path: src/main/java/hudson/plugins/ec2/EC2Cloud.java src/main/resources/hudson/plugins/ec2/EC2Cloud/computerSet.jelly src/main/resources/hudson/plugins/ec2/SlaveTemplate/config.jelly src/test/java/hudson/plugins/ec2/SlaveTemplateTest.java http://jenkins-ci.org/commit/ec2-plugin/803dfea25551d92453e99fd39e7e366d41007592 Log: Change primary template identification to be its name, not its AMI. Many useful configurations will have multiple slave templates that use the same AMI (but differ in other aspects). This patch changes various parts of the code to properly identify templates by their names (in the 'description' field) instead of their AMI. As an example, the manual slave provisioning button, before this patch, would allow the user to select a template from a drop-down list, but then launched the slave using the template's AMI, which could have resulted in the wrong template being used for the launch. This patch also changes the global config page so that the 'description' field is the first field in each template definition, to emphasize its importance. Addresses JENKINS-7960 and JENKINS-15158. This message is automatically generated by JIRA. 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-7960) EC2 Nodes which share an AMI ID get the wrong labels
SCM/JIRA link daemon commented on JENKINS-7960 EC2 Nodes which share an AMI ID get the wrong labels Code changed in jenkins User: Kevin P. Fleming Path: src/main/java/hudson/plugins/ec2/EC2Cloud.java src/main/resources/hudson/plugins/ec2/EC2Cloud/computerSet.jelly src/main/resources/hudson/plugins/ec2/SlaveTemplate/config.jelly src/test/java/hudson/plugins/ec2/SlaveTemplateTest.java http://jenkins-ci.org/commit/ec2-plugin/803dfea25551d92453e99fd39e7e366d41007592 Log: Change primary template identification to be its name, not its AMI. Many useful configurations will have multiple slave templates that use the same AMI (but differ in other aspects). This patch changes various parts of the code to properly identify templates by their names (in the 'description' field) instead of their AMI. As an example, the manual slave provisioning button, before this patch, would allow the user to select a template from a drop-down list, but then launched the slave using the template's AMI, which could have resulted in the wrong template being used for the launch. This patch also changes the global config page so that the 'description' field is the first field in each template definition, to emphasize its importance. Addresses JENKINS-7960 and JENKINS-15158. This message is automatically generated by JIRA. 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-7960) EC2 Nodes which share an AMI ID get the wrong labels
Francis Upton resolved JENKINS-7960 as Fixed EC2 Nodes which share an AMI ID get the wrong labels Fixed by patch from Kevin Fleming Change By: Francis Upton (12/Feb/13 9:13 PM) Status: Open Resolved Assignee: KohsukeKawaguchi FrancisUpton 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-15158) Sometimes starts the wrong instance
Francis Upton resolved JENKINS-15158 as Fixed Sometimes starts the wrong instance Fixed by patch from Kevin Fleming Change By: Francis Upton (12/Feb/13 9:14 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-16779) PROPFILE token does not evaluate in the Editable E-mail Notification for the email-ext plugin
Kavita Tiwari
commented on JENKINS-16779
PROPFILE token does not evaluate in the Editable E-mail Notification for the email-ext plugin
When I look at the "Content Token Reference" help for the email-ext plugin this appears:
snippit from Content Token Reference
Token Macro Plugin Tokens
${BUILD_NUMBER}
Expands to the current build number, a sequential auto-incrementing unique number that identifies the build, such as "125"
${ENV,var="VARIABLENAME"}
Expands to an environment variable (specified here as VARIABLENAME) from the build environment. Note that this does not include any variables set by the build scripts themselves, only those set by Jenkins and other plugins.
${PROPFILE,file="FILENAME",property="PROPERTYNAME"}
Expands to the value of a property in a property file. The filename is relative to the build workspace root.
snippit from Content Token Reference
It shows PROPFILE as a token-macro plugin token that can be used by the email-ext plugin. The other tokens listed above work (BUILD_NUMBER and ENV). As such, I figured that it could be used by the email-ext plugin.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-10405) Post-receive hook doesn't work
Kevin Fleming commented on JENKINS-10405 Post-receive hook doesnt work I too just ran into this issue, and while I'm not using any authentication that got in the way, I did have to change the repository URLs in my jobs to end with ".git" in order for the Webhook-provided URL to be matched up. Once I made this change I was able to use the 'Jenkins (GitHub plugin)' service hook in GitHub just fine. This message is automatically generated by JIRA. 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-16779) PROPFILE token does not evaluate in the Editable E-mail Notification for the email-ext plugin
Alex Earl commented on JENKINS-16779 PROPFILE token does not evaluate in the Editable E-mail Notification for the email-ext plugin What version of the token-macro plugin do you have installed? I had forgotten about the token macro plugin, sorry for the confusion. This message is automatically generated by JIRA. 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-16779) PROPFILE token does not evaluate in the Editable E-mail Notification for the email-ext plugin
Kavita Tiwari commented on JENKINS-16779 PROPFILE token does not evaluate in the Editable E-mail Notification for the email-ext plugin No worries. I'm using token-macro - 1.5.1. Looking at the release notes for the token-macro plugin, it "Added macro for retrieving properties from property files in the build workspace." in Version 1.3. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-15730) Persisting too much
Christian Wolfgang resolved JENKINS-15730 as Fixed Persisting too much Change By: Christian Wolfgang (12/Feb/13 9:46 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-15870) Wrong port numbers in hyperlinks, case 8211
Christian Wolfgang updated JENKINS-15870 Wrong port numbers in hyperlinks, case 8211 Change By: Christian Wolfgang (12/Feb/13 9:48 PM) Summary: Wrongportnumbersinhyperlinks ,case8211 This message is automatically generated by JIRA. 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-16779) PROPFILE token does not evaluate in the Editable E-mail Notification for the email-ext plugin
Alex Earl commented on JENKINS-16779 PROPFILE token does not evaluate in the Editable E-mail Notification for the email-ext plugin Can you try upgrading 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-15870) Wrong port numbers in hyperlinks, case 8211
Christian Wolfgang commented on JENKINS-15870 Wrong port numbers in hyperlinks, case 8211 Ok, good point, I will look at it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-15160) earliest git hash passed by parameterized build trigger when downstream job was triggered multiple times
Gergely Nagy commented on JENKINS-15160 earliest git hash passed by parameterized build trigger when downstream job was triggered multiple times Thank you very much for this - it would fix an important regression for me (my long running tests are flooding the queue with the current version). Any way to release it soon? This message is automatically generated by JIRA. 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-15160) earliest git hash passed by parameterized build trigger when downstream job was triggered multiple times
Gergely Nagy edited a comment on JENKINS-15160 earliest git hash passed by parameterized build trigger when downstream job was triggered multiple times Thank you very much for this - it would fix an important regression for me (my long running tests are flooding the queue with the current version - this started to happen with the latest upgrade). Any way to release it soon? This message is automatically generated by JIRA. 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-15160) earliest git hash passed by parameterized build trigger when downstream job was triggered multiple times
hlau commented on JENKINS-15160 earliest git hash passed by parameterized build trigger when downstream job was triggered multiple times Indeed I'm also still having this problem. Have to manually kill some of the jobs in the long queue. Quite a hassle. Please release the fix soon. This message is automatically generated by JIRA. 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.
