RE: Nullpointer in log rotator
Thorough testing only occurs in the LTS branch. If you don’t want to do some testing of your own before rolling out a Jenkins upgrade I would recommend that you switch from the bleeding edge to LTS. /James From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Pawel Sent: 10 October 2012 13:03 To: jenkinsci-users@googlegroups.com Subject: Re: Nullpointer in log rotator Same issue for me. I have first updated to 484, which introduced nasty bug with Maven installations being removed, so I installed 485, which makes plenty of my builds fail because of NPE. Is anyone testing the releases in some real environment before giving them to users? ** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmas...@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 **
possible bug in cas plugin?
Dear List, i'm writing because i noticed this error: Oct 11, 2012 11:05:36 AM hudson.ExpressionFactory2$JexlExpression evaluate WARNING: Caught exception evaluating: descriptor.getPropertyType(instance,field).itemTypeDescriptorOrDie. Reason: java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor176.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) 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:72) 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.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.WhenTag.doTag(WhenTag.java:46) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) 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.tags.core.ChooseTag.doTag(ChooseTag.java:38) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) 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:119) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) 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:119) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.WhenTag.doTag(WhenTag.java:46) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) 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.tags.core.ChooseTag.doTag(ChooseTag.java:38) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) 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:119) 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:119) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at
Re: possible bug in cas plugin?
Sorry for the half email.. but the combination of tab+space in gmail is terrible. I just added to the previous mail (see the mentioned part) the missing part of statcktrace. Thank you Federico 2012/10/11 fridodev frido...@gmail.com Dear List, i'm writing because i noticed this error: Oct 11, 2012 11:05:36 AM hudson.ExpressionFactory2$JexlExpression evaluate WARNING: Caught exception evaluating: descriptor.getPropertyType(instance,field).itemTypeDescriptorOrDie. Reason: java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor176.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) 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:72) 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.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.WhenTag.doTag(WhenTag.java:46) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) 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.tags.core.ChooseTag.doTag(ChooseTag.java:38) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) 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:119) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) 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:119) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.WhenTag.doTag(WhenTag.java:46) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) 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.tags.core.ChooseTag.doTag(ChooseTag.java:38) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) 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:119) at
Re: Nullpointer in log rotator
484 was marked as LTS [or LTS candidate?] some time ago. It looks like it isn't anymore. On Thursday, 11 October 2012 10:12:35 UTC+2, teilo wrote: Thorough testing only occurs in the LTS branch. If you don’t want to do some testing of your own before rolling out a Jenkins upgrade I would recommend that you switch from the bleeding edge to LTS. /James *From:* jenkins...@googlegroups.com javascript: [mailto: jenkins...@googlegroups.com javascript:] *On Behalf Of *Pawel *Sent:* 10 October 2012 13:03 *To:* jenkins...@googlegroups.com javascript: *Subject:* Re: Nullpointer in log rotator Same issue for me. I have first updated to 484, which introduced nasty bug with Maven installations being removed, so I installed 485, which makes plenty of my builds fail because of NPE. Is anyone testing the releases in some real environment before giving them to users? -- ** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postm...@nds.com javascript: and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 **
Jenkins Plugin - Remote Jboss Deploy Problem
Hello Olivier. I am trying to make the Deploy work on my environment, but I get the Cargo errror... The deploy is remote ** *ERROR: Publisher hudson.plugins.deploy.DeployPublisher aborted due to exceptionorg.codehaus.cargo.container.ContainerException http://stacktrace.jenkins-ci.org/search?query=org.codehaus.cargo.container.ContainerException: Failed to create deployer with implementation class org.codehaus.cargo.container.jboss.JBoss5xRemoteDeployer for the parameters (container [id = [jboss5x]], deployer type [remote]). at org.codehaus.cargo.generic.spi.AbstractGenericHintFactory.createImplementation(AbstractGenericHintFactory.java:157) http://stacktrace.jenkins-ci.org/search/?query=org.codehaus.cargo.generic.spi.AbstractGenericHintFactory.createImplementationentity=method . at hudson.model.Executor.run(Executor.java:236) http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Executor.runentity=method Caused by: java.lang.reflect.InvocationTargetException http://stacktrace.jenkins-ci.org/search?query=java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at org.codehaus.cargo.generic.deployer.DefaultDeployerFactory.createInstance(DefaultDeployerFactory.java:206) at org.codehaus.cargo.generic.spi.AbstractGenericHintFactory.createImplementation(AbstractGenericHintFactory.java:153) ... 19 more Caused by: org.codehaus.cargo.util.CargoException: Cannot locate the JBoss deployer class! Make sure the jboss-deployer for your JBoss version as well as all required JBoss JARs are in CARGO's classpath. More information on: http://cargo.codehaus.org/JBoss+Remote+Deployer at org.codehaus.cargo.container.jboss.JBoss5xRemoteDeployer.init(JBoss5xRemoteDeployer.java:91) ... 25 more Caused by: java.lang.ClassNotFoundException: org.codehaus.cargo.tools.jboss.JBossDeployer at java.net.URLClassLoader$1.run(URLClassLoader.java:217) * I am trying to fix this but with no success... I did what they told in (*http://cargo.codehaus.org/JBoss+Remote+Deployer)*. I tried creating a lib dir in jenkins server, putting 3 jars inside ( jboss-client, jboss-integration, jboss-profileservice-client) . Then I passed the -cp arg ponting to this lib dir with the jenkins.war execution ... ( java jenkins.war -jar -cp /jenkins/lib/ ) but I still get the problem... My Jboss version is 5.1 Jenkins 1.48 ... They tell to use this jars - JBoss deployment manager JARs - JBoss remoting client JARs I dont know if I used the right ones... If anyonce can help me finding the problem I would appreciate a lot! Regards Cesar
Jenkins Deploy Plugin - Remote Jboss Problem
Hello! I am trying to make the Deploy work on my environment, but I get the Cargo errror... The deploy is remote ** *ERROR: Publisher hudson.plugins.deploy.DeployPublisher aborted due to exceptionorg.codehaus.cargo.container.ContainerException http://stacktrace.jenkins-ci.org/search?query=org.codehaus.cargo.container.ContainerException: Failed to create deployer with implementation class org.codehaus.cargo.container.jboss.JBoss5xRemoteDeployer for the parameters (container [id = [jboss5x]], deployer type [remote]). at org.codehaus.cargo.generic.spi.AbstractGenericHintFactory.createImplementation(AbstractGenericHintFactory.java:157) http://stacktrace.jenkins-ci.org/search/?query=org.codehaus.cargo.generic.spi.AbstractGenericHintFactory.createImplementationentity=method . at hudson.model.Executor.run(Executor.java:236) http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Executor.runentity=method Caused by: java.lang.reflect.InvocationTargetException http://stacktrace.jenkins-ci.org/search?query=java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at org.codehaus.cargo.generic.deployer.DefaultDeployerFactory.createInstance(DefaultDeployerFactory.java:206) at org.codehaus.cargo.generic.spi.AbstractGenericHintFactory.createImplementation(AbstractGenericHintFactory.java:153) ... 19 more Caused by: org.codehaus.cargo.util.CargoException: Cannot locate the JBoss deployer class! Make sure the jboss-deployer for your JBoss version as well as all required JBoss JARs are in CARGO's classpath. More information on: http://cargo.codehaus.org/JBoss+Remote+Deployer at org.codehaus.cargo.container.jboss.JBoss5xRemoteDeployer.init(JBoss5xRemoteDeployer.java:91) ... 25 more Caused by: java.lang.ClassNotFoundException: org.codehaus.cargo.tools.jboss.JBossDeployer at java.net.URLClassLoader$1.run(URLClassLoader.java:217) * I am trying to fix this but with no success... I did what they told in (*http://cargo.codehaus.org/JBoss+Remote+Deployer)*. I tried creating a lib dir in jenkins server, putting 3 jars inside ( jboss-client, jboss-integration, jboss-profileservice-client) . Then I passed the -cp arg ponting to this lib dir with the jenkins.war execution ... ( java jenkins.war -jar -cp /jenkins/lib/ ) but I still get the problem... My Jboss version is 5.1 Jenkins 1.48 ... They tell to use this jars - JBoss deployment manager JARs - JBoss remoting client JARs I dont know if I used the right ones... If anyonce can help me finding the problem I would appreciate a lot! Regards Cesar
Re: What is the difference between multi configuration job and matrix based job?.
I hope that the following makes sense: Multi configuration Job: Allows you to create separate jobs to run sequentially or concurrently as build steps. Each Job will be its own Job. Matrix: You have the same 1 job that needs to be run on different machines. I think that the best thing to do is to create test jobs to C what the Matrix and MultiJobs do. Anyone out there ... please correct me if I am wrong! Mgimza On Thu, Oct 11, 2012 at 9:07 AM, Varghese Renny varghesekre...@gmail.comwrote: I am not understanding it from wiki. Please explain it with examples. Regards, varghese
Null pointer in M2ReleaseBuildWrapper
Hello, I get this exception at end of perform maven release build. This is a feature from M2 Release Plugin En attente que Jenkins finisse de récupérer les données channel stopped ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-users@googlegroups.com java.lang.NullPointerException at org.jvnet.hudson.plugins.m2release.M2ReleaseBuildWrapper$2.isSuccessfulReleaseBuild(M2ReleaseBuildWrapper.java:270) at org.jvnet.hudson.plugins.m2release.M2ReleaseBuildWrapper$2.tearDown(M2ReleaseBuildWrapper.java:209) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:817) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:589) at hudson.model.Run.execute(Run.java:1516) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) project=hudson.maven.MavenModuleSet@9046f8[cmiiappjavasimpledemoTmp] project.getModules()=[hudson.maven.MavenModule@1d9d7ab[cmiiappjavasimpledemoTmp/com.alcatel.proserv.cmII:cmIIappJavaSimpleDemo][cmiiappjavasimpledemoTmp/com. alcatel.proserv.cmII:cmIIappJavaSimpleDemo][relativePath:]] project.getRootModule()=hudson.maven.MavenModule@1d9d7ab[cmiiappjavasimpledemoTmp/com.alcatel.proserv.cmII:cmIIappJavaSimpleDemo][cmiiappjavasimpledemoTmp/co m.alcatel.proserv.cmII:cmIIappJavaSimpleDemo][relativePath:] FATAL: null configuration : Plugin version is 0.10.0. Jenkins is 1.485. java jre 1.6.0_35 windows xp additionnal infos : - mvn release:perform (in dos command line) succeeds. - I have first installed plugin 0.9.1. I got quite the same NPE. I though issue could be similar to http://issues.jenkins-ci.org/browse/JENKINS-10042 and decided to try 0.10.0 - I can provide more information on demand. In help in order to fix this issue is welcome ! Thanks in advance. Thierry
Re: Null pointer in M2ReleaseBuildWrapper
*Hello,* getProject*().*getBuilds*() is returning a list which contains a null entry which is just not good.* *This appears on first inspection to be a Jenkins core issue – can you try with earlier cores to track down when this was introduced?* * **/James* On Thursday, 11 October 2012 15:47:16 UTC+1, Thierry wrote: Hello, I get this exception at end of perform maven release build. This is a feature from M2 Release Plugin En attente que Jenkins finisse de récupérer les données channel stopped ERROR: Processing failed due to a bug in the code. Please report this to jenkins...@googlegroups.com javascript: java.lang.NullPointerException at org.jvnet.hudson.plugins.m2release.M2ReleaseBuildWrapper$2.isSuccessfulReleaseBuild(M2ReleaseBuildWrapper.java:270) at org.jvnet.hudson.plugins.m2release.M2ReleaseBuildWrapper$2.tearDown(M2ReleaseBuildWrapper.java:209) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:817) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:589) at hudson.model.Run.execute(Run.java:1516) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) project=hudson.maven.MavenModuleSet@9046f8[cmiiappjavasimpledemoTmp] project.getModules()=[hudson.maven.MavenModule@1d9d7ab[cmiiappjavasimpledemoTmp/com.alcatel.proserv.cmII:cmIIappJavaSimpleDemo][cmiiappjavasimpledemoTmp/com. alcatel.proserv.cmII:cmIIappJavaSimpleDemo][relativePath:]] project.getRootModule()=hudson.maven.MavenModule@1d9d7ab[cmiiappjavasimpledemoTmp/com.alcatel.proserv.cmII:cmIIappJavaSimpleDemo][cmiiappjavasimpledemoTmp/co m.alcatel.proserv.cmII:cmIIappJavaSimpleDemo][relativePath:] FATAL: null configuration : Plugin version is 0.10.0. Jenkins is 1.485. java jre 1.6.0_35 windows xp additionnal infos : - mvn release:perform (in dos command line) succeeds. - I have first installed plugin 0.9.1. I got quite the same NPE. I though issue could be similar to http://issues.jenkins-ci.org/browse/JENKINS-10042 and decided to try 0.10.0 - I can provide more information on demand. In help in order to fix this issue is welcome ! Thanks in advance. Thierry
Re: Null pointer in M2ReleaseBuildWrapper
Hi, On 11/10/2012 15:58, teilo wrote: *Hello,* getProject*().*getBuilds*() is returning a list which contains a null entry which is just not good.* *This appears on first inspection to be a Jenkins core issue – can you try with earlier cores to track down when this was introduced?* This is almost certainly related to https://issues.jenkins-ci.org/browse/JENKINS-15465 RunList returning null from its elements in 1.485 It looks like a bug in the lazy loading of build records. Richard ***/James* On Thursday, 11 October 2012 15:47:16 UTC+1, Thierry wrote: Hello, I get this exception at end of perform maven release build. This is a feature from M2 Release Plugin En attente que Jenkins finisse de récupérer les données channel stopped ERROR: Processing failed due to a bug in the code. Please report this to jenkins...@googlegroups.com javascript: java.lang.NullPointerException at org.jvnet.hudson.plugins.m2release.M2ReleaseBuildWrapper$2.isSuccessfulReleaseBuild(M2ReleaseBuildWrapper.java:270) at org.jvnet.hudson.plugins.m2release.M2ReleaseBuildWrapper$2.tearDown(M2ReleaseBuildWrapper.java:209) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:817) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:589) at hudson.model.Run.execute(Run.java:1516) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) project=hudson.maven.MavenModuleSet@9046f8[cmiiappjavasimpledemoTmp] project.getModules()=[hudson.maven.MavenModule@1d9d7ab[cmiiappjavasimpledemoTmp/com.alcatel.proserv.cmII:cmIIappJavaSimpleDemo][cmiiappjavasimpledemoTmp/com. alcatel.proserv.cmII:cmIIappJavaSimpleDemo][relativePath:]] project.getRootModule()=hudson.maven.MavenModule@1d9d7ab[cmiiappjavasimpledemoTmp/com.alcatel.proserv.cmII:cmIIappJavaSimpleDemo][cmiiappjavasimpledemoTmp/co m.alcatel.proserv.cmII:cmIIappJavaSimpleDemo][relativePath:] FATAL: null configuration : Plugin version is 0.10.0. Jenkins is 1.485. java jre 1.6.0_35 windows xp additionnal infos : - mvn release:perform (in dos command line) succeeds. - I have first installed plugin 0.9.1. I got quite the same NPE. I though issue could be similar to http://issues.jenkins-ci.org/browse/JENKINS-10042 http://issues.jenkins-ci.org/browse/JENKINS-10042 and decided to try 0.10.0 - I can provide more information on demand. In help in order to fix this issue is welcome ! Thanks in advance. Thierry
Re: Build Flow plugin saves empty DSL
Have you had a chance to reproduce this yet? Thanks! On Wednesday, October 3, 2012 10:31:36 AM UTC-4, Nicolas De loof wrote: I will try to reproduce your issue, but being at JavaOne can't do it before next week 2012/10/3 dhyix dhe...@gaic.com javascript: Editing a Build Flow always saves an empty DSL. I configure it, enter in: build(job). Then after saving, if I reconfigure it or look at the config file in the filesystem the dsl is always empty. Is there something I'm missing? I have a new install of Jenkins version 1.484 and I've added the Build Flow plugin version 0.5 to it. That's it. Thanks!
Re: Performance problems on Jenkins master(very long minor gc with stop-the-world)
Are you still facing this issue? On Tue, Oct 9, 2012 at 3:23 PM, icarusnine icar...@gmail.com wrote: Hello. We have a very large Jenkins set up that includes on master node with 100+ slaves and 1000+ jobs. We have reasons for keeping just a single master node so it isn't possible split our Hudson master. Now, we are experiencing performance problems(minor gc happens frequently and it is performed over 1~2 minutes and it made stop-the-world.) However, full gc is performed within 20~30 seconds. Our heap size is over 100G so it is hard to generate and analysis heap dump. Does anyone have any experience with very large Hudson installations like this? Is there any advice for tuning or recommendations for this issue? Also, please do let me know if there is any other data that I can provide that would help with analysis. Thanks for any help you can provide. Jenkins info Core ver : 1.424.6 WAS : weblogic 10.3.2 JAVA : jdk1.6.0.34 JVM OPTION : -Xms180g -Xmx180g -XX:NewSize=140g -XX:MaxNewSize=140g -XX:PermSize=1024m -XX:MaxPermSize=1024m -XX:-UseGCOverheadLimit -XX:+UseParallelGC -XX:SurvivorRatio=8 -verbosegc -Xloggc:app_gc.log -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -Djava.awt.headless=true Server spec CPU : Intel(R) Xeon(R) CPU E5-2690 2.90GHz * 4 (32 core) RAM : 256GB Gc log 60286.042: [GC [PSYoungGen: 8655292K-8714K(40587584K)] 25909185K-17262608K(208359744K), 0.0248360 secs] [Times: user=0.38 sys=0.01, real=0.03 secs] 60286.067: [Full GC (System) [PSYoungGen: 8714K-0K(40587584K)] [ParOldGen: 17253893K-17228395K(167772160K)] 17262608K-17228395K(208359744K) [PSPermGen: 194622K-194622K(2097152K)], 1.8638320 secs] [Times: user=33.26 sys=0.23, real=1.86 secs] 60748.860: [GC [PSYoungGen: 39173056K-532623K(40528512K)] 56401451K-17761019K(208300672K), 0.0837520 secs] [Times: user=1.19 sys=0.00, real=0.08 secs] 61243.483: [GC [PSYoungGen: 39705679K-29759K(40658432K)] 56934075K-17272524K(208430592K), 0.0558890 secs] [Times: user=0.49 sys=0.00, real=0.05 secs] 61805.663: [GC [PSYoungGen: 39346943K-28331K(40601792K)] 56589708K-17275705K(208373952K), 0.0544110 secs] [Times: user=0.49 sys=0.01, real=0.06 secs] 62383.664: [GC [PSYoungGen: 39345515K-33640K(40776640K)] 56592889K-17284373K(208548800K), 0.0592330 secs] [Times: user=0.49 sys=0.00, real=0.06 secs] .. 85842.953: [GC [PSYoungGen: 38973565K-1818337K(40038592K)] 80709421K-44276973K(207810752K), 22.0442750 secs] [Times: user=2.44 sys=503.41, real=22.04 secs] 85976.095: [GC [PSYoungGen: 40038561K-1904445K(37126592K)] 82497204K-46320890K(204898752K), 49.0663710 secs] [Times: user=2.88 sys=1117.05, real=49.06 secs] 86147.499: [GC [PSYoungGen: 37126456K-1721075K(38582592K)] 81542901K-48037517K(206354752K), 39.6267960 secs] [Times: user=2.81 sys=904.88, real=39.62 secs] 86265.898: [GC [PSYoungGen: 36943219K-1147657K(38796608K)] 83259661K-49166685K(206568768K), 43.2677960 secs] [Times: user=6.13 sys=985.33, real=43.26 secs] 86435.957: [GC [PSYoungGen: 36592456K-748179K(38591488K)] 84611484K-49915859K(206363648K), 34.1037910 secs] [Times: user=2.48 sys=780.02, real=34.10 secs] 86560.263: [GC [PSYoungGen: 36192756K-448475K(38982464K)] 85360436K-50343633K(206754624K), 27.3025220 secs] [Times: user=1.64 sys=623.52, real=27.29 secs] 86594.685: [GC [PSYoungGen: 36402298K-106372K(38914816K)] 86297455K-50438940K(206686976K), 15.7548480 secs] [Times: user=1.88 sys=359.23, real=15.76 secs]
Proper use of labels to have Jenkins build on nodes which are idle.
Hi All I am stuck with a problem here. I have N number of builds which can run on any machine/slave. I have M number of slaves and each has 2 executors. I want to make sure that a build, when it is triggered, runs one a machine which has all executors free/idle. The second executors should be used only if all the first executors are busy running builds. I have tried multiple Label options and plugins. I dont want to have a situation where I have a dummy/trigger job starting a build. Please help. -mastkis
publish artifacts *after* the build
It looks like there are lots of ways to publish artifacts as part of the build ( https://wiki.jenkins-ci.org/display/JENKINS/Plugins#Plugins-Artifactuploaders) but I don't see anything that works with existing builds. Our use case is that we: * use jenkins to build/test after every commit * manually test generated .exe files downloading from our jenkins server * when necessary, we manually scp the the artifacts (from jenkins build folder) to a remote server. It would be great to replace this step with a button in the jenkins UI. Is there a plugin that will SCP(or whatever) Build Artifacts from a previous build? thanks ryan
RE: publish artifacts *after* the build
Ryantxu said: It looks like there are lots of ways to publish artifacts as part of the build (https://wiki.jenkins-ci.org/display/JENKINS/Plugins#Plugins-Artifactuploaders) but I don't see anything that works with existing builds. Our use case is that we: * use jenkins to build/test after every commit * manually test generated .exe files downloading from our jenkins server * when necessary, we manually scp the the artifacts (from jenkins build folder) to a remote server. It would be great to replace this step with a button in the jenkins UI. Is there a plugin that will SCP(or whatever) Build Artifacts from a previous build? Look at https://wiki.jenkins-ci.org/display/JENKINS/Promoted+Builds+Plugin. Here's an excerpt about common use cases: Artifact storage -- you may not want to push an artifact to your main artifact repository on each build. With build promotions, you can push only when an artifact meets certain criteria. For example, you might want to push it only after an integration test is run. Manual Promotions - You can choose a group of people who can run a promotion manually. This gives a way of having a sign off within the build system. For example, a developer might validate a build and approve it for QA testing only when a work product is completed entirely. Then another promotion can be added for the QA hand off to production. HTH, Todd Greer Director of Development, Affinegy, Inc.
New to jenkins
Hi All, I'm new to jenkins and sonar. So can anyone help me regarding sonar and jenkins integration. 1.How ro integrate sonar and jenkins. Regards, Hamoodh
problems when integrate cygwin's bash script into jenkins
Hello All, I run into this problem. I have cygwin and Jenkins installed on my pc. And I have a bash script ci.sh If I click the mintty.exe from the desktop to start the terminal and run the script. It would run ok. but if I invoke the bash.exe from Jenkins. The java part in the script always report some fatal error as following, both under condition of invoking Bash.exe with --login -i or not. I google around and I see some similar reports as my problem but not a solution. Could anybody provide some information on this? Thanks a lot Br, Tony Zhang, Tz GSM Team @ Beijing, China # # A fatal error has been detected by the Java Runtime Environment: # # EXCEPTION_ACCESS_VIOLATION (0xc005) at pc=0x7c910a19, pid=6176, tid=7720 # # JRE version: 6.0_21-b07 # Java VM: Java HotSpot(TM) Client VM (17.0-b17 mixed mode windows-x86 ) # Problematic frame: # C [ntdll.dll+0x10a19] # # An error report file with more information is saved as: # E:\cygwin\home\zhiqunwa\workspace33\o\hs_err_pid6176.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug.
Re: ERROR: Could not send email as a part of the post-build
Hi Alex, still this issue and one more issue persists even after upgrading email-ext to latest 2.24.1 i have created jire issue with details. JENKINS-15502 - Email-ext issues: attachments feature creating issueshttps://issues.jenkins-ci.org/browse/JENKINS-15502 please let me know if need more information to fix this issue: and hope this issue will be fixed soon. regards, Hiteswar On Thu, Oct 11, 2012 at 2:30 PM, Alex Earl slide.o@gmail.com wrote: publishers. MIME-Version: 1.0 Content-Type: multipart/alternative; boundary=e89a8ff1c166fd555b04cbc1c39d --e89a8ff1c166fd555b04cbc1c39d Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit The exception is different from that issue. I can't debug an old version, so please upgrade and see if the problem persists. If it does, file an issue in jira with as much information as you can. Sent from my Windows Phone From: hitesh kumar Sent: 10/10/2012 10:23 PM To: jenkinsci-...@googlegroups.com; slide.o@gmail.com Cc: jenkinsci-users@googlegroups.com Subject: Re: ERROR: Could not send email as a part of the post-build publishers. Thanks Slide for reply. i am using email ext-2.22 is latest 2.24.1 having fix of it??? as per https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin below raised issue already should be fixed in 2.19 version. - JENKINS-12047 https://issues.jenkins-ci.org/browse/JENKINS-12047 ERROR: Could not send email as a part of the post-build publishers.https://issues.jenkins-ci.org/browse/JENKINS-12047 Please share your comment? On Thu, Oct 11, 2012 at 2:00 PM, Slide slide.o@gmail.com wrote: Looks like you are on an older version of email-ext. slide On Wed, Oct 10, 2012 at 9:59 PM, hitesh kumar hits...@gmail.com wrote: Hi, Please let me know if any one facing below issue and having any solution or workaround. *env:* LTS jenkins 1.447.2 email ext-2.22 ubuntu 10.04 *Job config:* -matrix job -Variants 1 2 3 -select Trigger for each configuration at editable email Notification. *ISSUE :one of variant job is not sending mail and generating below issue: other variant jobs are sending mails.* ERROR: Could not send email as a part of the post-build publishers. javax.mail.MessagingException: IOException while sending message; nested exception is: java.io.IOException at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:1141) at javax.mail.Transport.send0(Transport.java:195) at javax.mail.Transport.send(Transport.java:124) at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:282) at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:265) at hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:225) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:697) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:672) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:650) at hudson.model.Build$RunnerImpl.cleanUp(Build.java:171) at hudson.model.Run.run(Run.java:1448) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) Caused by: java.io.IOException at hudson.remoting.FastPipedInputStream.read(FastPipedInputStream.java:175) at hudson.remoting.FastPipedInputStream.read(FastPipedInputStream.java:151) at javax.activation.DataHandler.writeTo(DataHandler.java:293) at javax.mail.internet.MimeBodyPart.writeTo(MimeBodyPart.java:1476) at javax.mail.internet.MimeBodyPart.writeTo(MimeBodyPart.java:865) at javax.mail.internet.MimeMultipart.writeTo(MimeMultipart.java:462) at com.sun.mail.handlers.multipart_mixed.writeTo(multipart_mixed.java:103) at javax.activation.ObjectDataContentHandler.writeTo(DataHandler.java:869) at javax.activation.DataHandler.writeTo(DataHandler.java:302) at javax.mail.internet.MimeBodyPart.writeTo(MimeBodyPart.java:1476) at javax.mail.internet.MimeMessage.writeTo(MimeMessage.java:1772) at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:1099) ... 14 more -- Website: http://earl-of-code.com --e89a8ff1c166fd555b04cbc1c39d Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable htmlheadmeta content=3Dtext/html; charset=3Dutf-8 http-equiv=3DCont= ent-Type/headbodydivdiv style=3Dfont-family: Calibri,sans-serif; = font-size: 11pt;The exception is different from that issue. I can't debug= an old version, so please upgrade and see if the problem persists. If it d= oes, file an issue in jira with as much information as you can.brbrSent= from my Windows Phonebr/div/divhrspan style=3Dfont-family:
RE: New to jenkins
There’s some good documentation on this on the Sonar website: http://docs.codehaus.org/display/SONAR/Hudson+and+Jenkins+Plugin -Jim From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of hamoodh parameswaran Sent: Thursday, October 11, 2012 9:43 PM To: jenkinsci-users@googlegroups.com Subject: New to jenkins Hi All, I'm new to jenkins and sonar. So can anyone help me regarding sonar and jenkins integration. 1.How ro integrate sonar and jenkins. Regards, Hamoodh NOTICE: All information in and attached to this email may be proprietary, confidential, privileged and otherwise protected from improper or erroneous disclosure. If you are not the sender's intended recipient, you are not authorized to intercept, read, print, retain, copy, forward, or disseminate this message.
Re: Performance problems on Jenkins master(very long minor gc with stop-the-world)
Yes, i am finding the solution of this problem. Can you help me? Is there any advice for tunning?
Re: How can jenkins master share slave nodes.
Not sure if i understand you correctly. A slave is only a logical unit, it has not to be a physical machine. You can have multiple slaves running on one host, without interfering each other. So, every master can have as many slave as you want on any hosts, as long as each slave (not host) has its own root-fs. Then it does not matter hou many hosts you have, you can have 5 *independent* jenkins master-slave cluster across your build farm, each one does not care (does not know) the existence of other clusters. You can share all the hardware resources of you 20 hosts, the slave configuration is totally orthognal. So you can share the hardware resources across 5 independent clasters, each has (theoretically) as many slaves as necessary. but if you want to share the (logical unit) *slave*, i dont think it is possible, even it is, i can not find any reason to do so. Shen Hui shenhu...@baidu.com schrieb: Hi buddy, I have 5 masters, and suppose I have a slave pool with 20 nodes. Can these 5 master share these 20 slaves; because if i separate 20 slave into 5 group(each has 4), each attached to a master, that's meaning a single master can schedule only with 4 slaves; so there is this case, some groups are busing, and other may be idle. i'd like these 20 slaves can share jobs schedule among these 5 masters. Can anybody help me on this? Appreciate very much. -- View this message in context: http://jenkins.361315.n4.nabble.com/How-can-jenkins-master-share-slave-nodes-tp4642699.html Sent from the Jenkins users mailing list archive at Nabble.com. -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
Re: Proper use of labels to have Jenkins build on nodes which are idle.
Hi Kishore Use Job Priority Sorter Plugin and Labels Intelligently, you should be able to solve your problem. Thanks, Krishna Chaitanya On Thu, Oct 11, 2012 at 1:22 PM, mastkis mast...@gmail.com wrote: Hi All I am stuck with a problem here. I have N number of builds which can run on any machine/slave. I have M number of slaves and each has 2 executors. I want to make sure that a build, when it is triggered, runs one a machine which has all executors free/idle. The second executors should be used only if all the first executors are busy running builds. I have tried multiple Label options and plugins. I dont want to have a situation where I have a dummy/trigger job starting a build. Please help. -mastkis
Re: What is the difference between multi configuration job and matrix based job?.
Why using additional executor for slave node running multiconfiguration job? Regards, varghese
