[JIRA] [description-setter-plugin] (JENKINS-28004) Description-Setter plugin exposes description as Environment variable which is automatically added to Ant command line and breaks build
Uwe Schindler
updated JENKINS-28004
Description-Setter plugin exposes description as Environment variable which is automatically added to Ant command line and breaks build
Change By:
Uwe Schindler
(19/Apr/15 9:18 AM)
Description:
Thenewestversionofthedescriptionsetterplugincreatesanewenvironmentvariablewiththebuilddescription(seeJENKINS-17461).Thisisperfectlyfine,butforsomestrangereason,thisdescriptionisaddedtotheAntcommandlineas-Dparameter,butitisnotconfiguredtodoso.Environmentvaraiblescreatedbythe
environment-setter
envinject
pluginarenotautomatiacllypublishedtoAntcommandline,sothereseemstobeadifferenceinhowthe
environment
envinject
pluginsetstheenvvarandthisone.IwouldexpecttheDESCRIPTION_SETTER_DESCRIPTIONenvironmentvariablejustbepublishedinsideJenkins,butnotautomaticallyaddedtothecommandlineofAnt(whichbreaksundercertaincircumstanceswithspecialchars).Thisishowitlookslike:{noformat}[description-setter]Descriptionset:Java:32bit/jdk1.7.0_80-ea-b05-client-XX:+UseParallelGC[Lucene-Solr-5.x-Linux]$/var/lib/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT_1.8.2/bin/ant-DDESCRIPTION_SETTER_DESCRIPTION=Java:32bit/jdk1.7.0_80-ea-b05-client-XX:+UseParallelGC-Dargs=-client-XX:+UseParallelGCjenkins-hourly{noformat}Asyouseeinthesecondline,itaddstheDESCRIPTION_SETTER_DESCRIPTIONtoAntscommandlinewithnoreason.Icheckedtheconfig,theenvironmentvariablespasseddownareonly-Dargs=...(createdbyenvinject),butthatsconfiguredexplicitly.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [description-setter-plugin] (JENKINS-28004) Description-Setter plugin exposes description as Environment variable which is automatically added to Ant command line and breaks build
Uwe Schindler
updated JENKINS-28004
Description-Setter plugin exposes description as Environment variable which is automatically added to Ant command line and breaks build
Change By:
Uwe Schindler
(19/Apr/15 9:19 AM)
Description:
Thenewestversionofthedescriptionsetterplugincreatesanewenvironmentvariablewiththebuilddescription(seeJENKINS-17461).Thisisperfectlyfine,butforsomestrangereason,thisdescriptionisaddedtotheAntcommandlineas-Dparameter,butitisnotconfiguredtodoso.EnvironmentvaraiblescreatedbytheenvinjectpluginarenotautomatiacllypublishedtoAntcommandline,sothereseemstobeadifferenceinhowtheenvinjectpluginsetstheenvvarandthisone.IwouldexpecttheDESCRIPTION_SETTER_DESCRIPTIONenvironmentvariablejustbepublishedinsideJenkins,butnotautomaticallyaddedtothecommandlineofAnt(whichbreaksundercertaincircumstanceswithspecialchars).Thisishowitlookslike:{noformat}[description-setter]Descriptionset:Java:32bit/jdk1.7.0_80-ea-b05-client-XX:+UseParallelGC[Lucene-Solr-5.x-Linux]$/var/lib/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT_1.8.2/bin/ant-DDESCRIPTION_SETTER_DESCRIPTION=Java:32bit/jdk1.7.0_80-ea-b05-client-XX:+UseParallelGC-Dargs=-client-XX:+UseParallelGCjenkins-hourly{noformat}Asyouseeinthesecondline,itaddstheDESCRIPTION_SETTER_DESCRIPTIONtoAntscommandlinewithnoreason.Icheckedtheconfig,theenvironmentvariablespasseddownareonly-Dargs=...(createdbyenvinject),butthatsconfiguredexplicitly.
Therearetonsofotherenvironmentvarscreatedbyenvinject(itisaquitecomplexbuild),butthosearenotappearinginAntscommandline!
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-27377) Custom view does not display job warnings, displays '0'
Ulli Hafner edited a comment on JENKINS-27377 Custom view does not display job warnings, displays 0 That would help! I have an acceptance test that should check the column but maybe in your case a different setup is used. Please also note which project type is used and how many parsers are defined. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [description-setter-plugin] (JENKINS-28004) Description-Setter plugin exposes description as Environment variable which is automatically added to Ant command line and breaks build
Uwe Schindler updated JENKINS-28004 Description-Setter plugin exposes description as Environment variable which is automatically added to Ant command line and breaks build Change By: Uwe Schindler (19/Apr/15 9:10 AM) Environment: DescriptionSetterv1.10 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-28005) I would like to preserve file commit times as part of checkout from Subversion repositories
Jay Renbaum created JENKINS-28005 I would like to preserve file commit times as part of checkout from Subversion repositories Issue Type: Improvement Assignee: Unassigned Components: subversion-plugin Created: 19/Apr/15 12:55 PM Description: All files checked out to the Jenkins workspace currently have the same timestamp, the date/time that the checkout occurred. I would like the option during Jenkins checkout from Subversion to preserve the commit date for each file. From the command-line you can use svn checkout --config-option config:miscellany:use-commit-times=yes to preserve times on checkout. Project: Jenkins Priority: Minor Reporter: Jay Renbaum This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [prioritysorter-plugin] (JENKINS-27987) Multiple build jobs are the waiting queue waiting to next available excutor, but no build jobs are running. Appears after migration from ver 1.606 to 1.6
Magnus Sandberg commented on JENKINS-27987 Multiple build jobs are the waiting queue waiting to next available excutor, but no build jobs are running. Appears after migration from ver 1.606 to 1.609 Are you using 2.12? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [description-setter-plugin] (JENKINS-28004) Description-Setter plugin exposes description as Environment variable which is automatically added to Ant command line and breaks build
Uwe Schindler created JENKINS-28004 Description-Setter plugin exposes description as Environment variable which is automatically added to Ant command line and breaks build Issue Type: Bug Assignee: huybrechts Components: description-setter-plugin Created: 19/Apr/15 9:06 AM Description: The newest version of the description setter plugin creates a new environment variable with the build description (see JENKINS-17461). This is perfectly fine, but for some strange reason, this description is added to the Ant command line as "-D" parameter, but it is not configured to do so. Environment varaibles created by the environment-setter plugin are not automatiaclly published to Ant command line, so there seems to be a difference in how the environment plugin sets the env var and this one. I would expect the DESCRIPTION_SETTER_DESCRIPTION environment variable just be published inside Jenkins, but not automatically added to the command line of Ant (which breaks under certain circumstances with special chars). This is how it looks like: [description-setter] Description set: Java: 32bit/jdk1.7.0_80-ea-b05 -client -XX:+UseParallelGC [Lucene-Solr-5.x-Linux] $ /var/lib/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT_1.8.2/bin/ant "-DDESCRIPTION_SETTER_DESCRIPTION=Java: 32bit/jdk1.7.0_80-ea-b05 -client -XX:+UseParallelGC" "-Dargs=-client -XX:+UseParallelGC" jenkins-hourly As you see in the second line, it adds the DESCRIPTION_SETTER_DESCRIPTION to Ant's command line with no reason. I checked the config, the environment variables passed down are only "-Dargs=..." (created by envinject), but thats configured explicitly. Project: Jenkins Priority: Major Reporter: Uwe Schindler This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer-plugin] (JENKINS-21767) Add alert configuration for identified causes
Andreas Mandel commented on JENKINS-21767 Add alert configuration for identified causes That would help here also. A Email address / list per category. The plugin could inform the right people if the build fails because of infrastructure issues vs. compile issues. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-27377) Custom view does not display job warnings, displays '0'
Ulli Hafner edited a comment on JENKINS-27377 Custom view does not display job warnings, displays 0 That would help! I have an acceptance test that should check the column but maybe in your case a different setup is used. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-27377) Custom view does not display job warnings, displays '0'
Ulli Hafner commented on JENKINS-27377 Custom view does not display job warnings, displays 0 That would help! I have an acceptance test\https://github.com/jenkinsci/acceptance-test-harness/blob/master/src/test/java/plugins/WarningsPluginTest.java#L200 that should check the column but maybe in your case a different setup is used. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [poll-mailbox-trigger-plugin] (JENKINS-27575) Please add possibility to handle the attachment of mail to this plugin
Jason Swager commented on JENKINS-27575 Please add possibility to handle the attachment of mail to this plugin I think this would be a very nice feature as well. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28002) Error 503 when cancelling job
Sylvain ANGLADE commented on JENKINS-28002 Error 503 when cancelling job Good evening and thank you for your return. to be more precise jenkins completely crash when canceling an ongoing job for more than two hours. I have to restart the server via /etc/init.d/jenkins restart command This bug is not systematic, but I met 4 times during the last week. When I try to have a threadDump I have this error message appears Thread Dump Failed to retrieve thread dump java.util.concurrent.TimeoutException at java.util.concurrent.FutureTask.get(FutureTask.java:201) at hudson.remoting.LocalChannel$2.get(LocalChannel.java:81) at jenkins.model.Jenkins.getAllThreadDumps(Jenkins.java:3014) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) 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.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) 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.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) 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.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95) 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.JellyFacet$1.dispatch(JellyFacet.java:95) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at
[JIRA] [subversion-plugin] (JENKINS-28005) I would like to preserve file commit times as part of checkout from Subversion repositories
Daniel Beck resolved JENKINS-28005 as Duplicate I would like to preserve file commit times as part of checkout from Subversion repositories Change By: Daniel Beck (19/Apr/15 7:51 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudformation-plugin] (JENKINS-28007) CloudFormation Plugin should use password fields for secret information
Matt Firtion created JENKINS-28007 CloudFormation Plugin should use password fields for secret information Issue Type: Improvement Assignee: edovale Components: cloudformation-plugin Created: 19/Apr/15 6:50 PM Description: The CloudFormation Plugin should use a password field when entering the AWS Secret Key to prevent users from accessing this information that may not need to know the key. Project: Jenkins Priority: Minor Reporter: Matt Firtion This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudformation-plugin] (JENKINS-28007) CloudFormation Plugin should use password fields for secret information
Matt Firtion started work on JENKINS-28007 CloudFormation Plugin should use password fields for secret information Change By: Matt Firtion (19/Apr/15 8:00 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/d/optout.
[JIRA] [core] (JENKINS-28002) Error 503 when cancelling job
Daniel Beck commented on JENKINS-28002 Error 503 when cancelling job To clarify, Jenkins crashes and the entire process needs to be restarted? Or is it one request that doesn't get a response? The log message is standard for all aborted builds AFAICT, so it doesn't tell us anything. A thread dump may be helpful just before you get the 503 response: https://wiki.jenkins-ci.org/display/JENKINS/Obtaining+a+thread+dump This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudformation-plugin] (JENKINS-28007) CloudFormation Plugin should use password fields for secret information
Matt Firtion assigned JENKINS-28007 to Matt Firtion CloudFormation Plugin should use password fields for secret information Change By: Matt Firtion (19/Apr/15 8:00 PM) Assignee: edovale MattFirtion This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudformation-plugin] (JENKINS-28007) CloudFormation Plugin should use password fields for secret information
Matt Firtion commented on JENKINS-28007 CloudFormation Plugin should use password fields for secret information I can submit a PR for this change. This change does not encrypt the values in config.xml, only masks the values in the UI. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28002) Error 503 when cancelling job
Daniel Beck commented on JENKINS-28002 Error 503 when cancelling job Try using the kill -3 or another alternative method to get the thread dump, preferably before Jenkins crashes. Is it always the same job that's aborted and then crashes Jenkins? Or is it any of those which run 2+ hours? Please attach a full list of installed plugins and their versions, and config.xml files of the affected (Jenkins-crashing) 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/d/optout.
[JIRA] [docker-plugin] (JENKINS-28008) Docker-Plugin fail to connect remote Docker host
Praveen Kumar
created JENKINS-28008
Docker-Plugin fail to connect remote Docker host
Issue Type:
Bug
Assignee:
Kanstantsin Shautsou
Components:
docker-plugin
Created:
20/Apr/15 5:56 AM
Description:
I have docker deployed on a different host (not on master) and it able to connect through API.
curl -X GET http://10.3.8.250:2375/images/json
[{"Created":1428916329,"Id":"610a453f85bd1f07755464c0a6e2f824a6bf931bb5ca49db2eb4c65049ba342a","ParentId":"1e67e7e1283aba9e54e2116ce020a9faec9b5e222d7f9181ab41447addbafd12","RepoTags":["jenkins-slave:latest"],"Size":0,"VirtualSize":697878553}
But when am setting up docker cloud it will show below traceback.
ERROR
A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened.
Stack trace
javax.servlet.ServletException: java.lang.NumberFormatException: For input string: "0-dev"
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:168)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533)
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231)
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428)
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
at
[JIRA] [description-setter-plugin] (JENKINS-28006) description setter postbuild step pollutes build history in matrix projects
felix schwitzer created JENKINS-28006 description setter postbuild step pollutes build history in matrix projects Issue Type: Bug Assignee: huybrechts Attachments: buildsetterscreen.png Components: description-setter-plugin Created: 19/Apr/15 2:24 PM Description: In a matrix project there is an option in the postbuild step to set the build-description in the parent build. The documentation says Also set the description on a multi-configuration build. The first description found for any of the invididual builds will be used as description for the multi-configuration build. This only applies to multi-configuration projects. I set the build description to the actual git-branch built. With v1.10 now this information is shown as often as configurations are used. This is not what I'm expecting, the description text should be there only once (as documented). This my be related to JENKINS-26671 Environment: description-setter-plugin 1.10 with jenkins 1.607 Project: Jenkins Priority: Major Reporter: felix schwitzer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
