[JIRA] (JENKINS-13915) NPE Exception, possibly caused by disabled jobs?
Ben Golding resolved JENKINS-13915 as Fixed NPE Exception, possibly caused by disabled jobs? This issue hasn't occurred for a while for me (I'm currently using 0.8) so marking fixed. Change By: Ben Golding (12/Mar/13 10:57 AM) Status: Open 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-13915) NPE Exception, possibly caused by disabled jobs?
Ben Golding commented on JENKINS-13915 NPE Exception, possibly caused by disabled jobs? This issue was happening on 100% of builds for me. Since updating 0.5 to 0.6 yesterday, the exception is gone. I guess more time is needed in case this is an intermittent issue as some users are reporting. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13915) NPE Exception, possibly caused by disabled jobs?
Ulf Bamberg commented on JENKINS-13915 NPE Exception, possibly caused by disabled jobs? same issue like https://issues.jenkins-ci.org/browse/JENKINS-15519 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13915) NPE Exception, possibly caused by disabled jobs?
aj2 commented on JENKINS-13915 NPE Exception, possibly caused by disabled jobs? I have also seen this with 11 parallel jobs each having their own retry block. It doesn't happen every time but enough so I can't use this plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13915) NPE Exception, possibly caused by disabled jobs?
Ben Golding commented on JENKINS-13915 NPE Exception, possibly caused by disabled jobs? Increased the priority, Build Flow is effectively unuseable for triggering our nightly builds until I can find a workaround or fix it. Any tips how to debug the root cause would be VERY much appreciated! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13915) NPE Exception, possibly caused by disabled jobs?
Ben Golding updated JENKINS-13915 NPE Exception, possibly caused by disabled jobs? Change By: Ben Golding (21/Sep/12 8:59 PM) Priority: Minor Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13915) NPE Exception, possibly caused by disabled jobs?
Ben Golding updated JENKINS-13915 NPE Exception, possibly caused by disabled jobs? Change By: Ben Golding (21/Sep/12 8:57 PM) Environment: Jenkins 1. 476 482 Build Flow 0. 4 5 Red Hat Enterprise Linux 5.5 64 bit Sun Java 1.6.0_20 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13915) NPE Exception, possibly caused by disabled jobs?
Ben Golding commented on JENKINS-13915 NPE Exception, possibly caused by disabled jobs? I also no longer have any disabled 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
[JIRA] (JENKINS-13915) NPE Exception, possibly caused by disabled jobs?
Ben Golding commented on JENKINS-13915 NPE Exception, possibly caused by disabled jobs? I am using the latest available at time of writing: Jenkins 1.476, Build Flow 0.4 The bug persists... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13915) NPE Exception, possibly caused by disabled jobs?
Ben Golding updated JENKINS-13915 NPE Exception, possibly caused by disabled jobs? Change By: Ben Golding (08/Aug/12 8:59 AM) Environment: Jenkins 1. 465 476 Build Flow 0. 3 4 Red Hat Enterprise Linux 5.5 64 bit Sun Java 1.6.0_20 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13915) NPE Exception, possibly caused by disabled jobs?
sanga commented on JENKINS-13915 NPE Exception, possibly caused by disabled jobs? Actually, have you tried updating Jenkins? As I just did that and I can't reproduce this anymore. And (though I don't precisely recall) the version was similar to yours, 1.467 I think, and now with 1.476, I don't have 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
[JIRA] (JENKINS-13915) NPE Exception, possibly caused by disabled jobs?
sanga
commented on JENKINS-13915
NPE Exception, possibly caused by disabled jobs?
I stumbled into this bug as well, with a much simpler job config, namely:
build( "do1" )
build( "do2" )
parallel (
{ build("do1") },
{ build("do2") },
)
the stack is the same, but for completeness sake:
Started by user anonymous
Building on master in workspace /var/lib/jenkins/jobs/tims-flow/workspace
Trigger job do1
do1 #4 completed
Trigger job do2
do2 #4 completed
parallel {
Trigger job do1
Trigger job do2
do1 #5 completed
do2 #5 completed
FATAL: null
java.lang.NullPointerException
at org.codehaus.groovy.runtime.callsite.GetEffectivePojoPropertySite.acceptGetProperty(GetEffectivePojoPropertySite.java:51)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callGetProperty(AbstractCallSite.java:227)
at com.cloudbees.plugins.flow.FlowDelegate$_parallel_closure3.doCall(FlowDSL.groovy:216)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233)
at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:272)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:884)
at groovy.lang.Closure.call(Closure.java:412)
at groovy.lang.Closure.call(Closure.java:425)
at org.codehaus.groovy.runtime.DefaultGroovyMethods.each(DefaultGroovyMethods.java:1377)
at org.codehaus.groovy.runtime.DefaultGroovyMethods.each(DefaultGroovyMethods.java:1349)
at org.codehaus.groovy.runtime.dgm$149.invoke(Unknown Source)
at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoMetaMethodSiteNoUnwrapNoCoerce.invoke(PojoMetaMethodSite.java:271)
at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite.call(PojoMetaMethodSite.java:53)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116)
at com.cloudbees.plugins.flow.FlowDelegate.parallel(FlowDSL.groovy:215)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233)
at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:361)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:884)
at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.callCurrent(PogoMetaClassSite.java:66)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:46)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:133)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:145)
at Script1$_run_closure1.doCall(Script1.groovy:3)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233)
at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:272)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:884)
at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.callCurrent(PogoMetaClassSite.java:66)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:46)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:133)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:141)
at Script1$_run_closure1.doCall(Script1.groovy)
at sun.reflect.Nativ
[JIRA] (JENKINS-13915) NPE Exception, possibly caused by disabled jobs?
Ben Golding
commented on JENKINS-13915
NPE Exception, possibly caused by disabled jobs?
I could reproduce this issue again today. In this case the assigned node for *_de02winterm20 jobs was disconnected (JNLP slave was not running). Notice from the log below, two *_de02winterm20 jobs are triggered but do not complete:
===
parallel {
Trigger job rsync_binmod_de02winterm31
Trigger job rsync_binmod_stormcs241
Trigger job downmerge_f2011.06
Trigger job rsync_SDR_de02winterm31
Trigger job rsync_SDR_stormcs240
Trigger job rsync_SDR_stormcs241
Trigger job rsync_binmod_de02winterm20
Trigger job checkbinmod
Trigger job rsync_binmod_stormcs240
Trigger job downmerge_main
Trigger job rsync_SDR_de02winterm20
Trigger job downmerge_g2012.06
Trigger job removebinmod
checkbinmod #68 completed
downmerge_main #143 completed
downmerge_f2011.06 #124 completed
rsync_binmod_stormcs240 #47 completed
removebinmod #66 completed
rsync_binmod_stormcs241 #350 completed
rsync_binmod_de02winterm31 #40 completed
rsync_SDR_de02winterm31 #39 completed
rsync_SDR_stormcs240 #42 completed
rsync_SDR_stormcs241 #122 completed
downmerge_g2012.06 #93 completed
FATAL: null
java.lang.NullPointerException
at org.codehaus.groovy.runtime.callsite.GetEffectivePojoPropertySite.acceptGetProperty(GetEffectivePojoPropertySite.java:51)
[... see attached console.log for full backtrace ...]
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13915) NPE Exception, possibly caused by disabled jobs?
[ https://issues.jenkins-ci.org/browse/JENKINS-13915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163191#comment-163191 ] Ben Golding commented on JENKINS-13915: --- Speculation: this is could be related to disabled jobs? The following jobs are disabled: chameleon_clean_g2012.06_windows chameleon_clean_main_windows fastmodels_clean_g2012.06_windows fastmodels_clean_main_windows These jobs appear in the console as 'Trigger job ' however there is no corresponding 'Completed #' so that could be where the problem happens. > NPE Exception, possibly caused by disabled jobs? > > > Key: JENKINS-13915 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13915 > Project: Jenkins > Issue Type: Bug > Components: build-flow > Environment: Jenkins 1.465 > Build Flow 0.3 > Red Hat Enterprise Linux 5.5 64 bit > Sun Java 1.6.0_20 >Reporter: Ben Golding >Assignee: Nicolas De Loof >Priority: Minor > Labels: plugin > Attachments: console.log, DSL.txt > > > Trying to run a moderately complex DSL (see attached DSL.txt) > causes an exception near to the end of the build (see attached console.log) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13915) NPE Exception, possibly caused by disabled jobs?
Ben Golding created JENKINS-13915: - Summary: NPE Exception, possibly caused by disabled jobs? Key: JENKINS-13915 URL: https://issues.jenkins-ci.org/browse/JENKINS-13915 Project: Jenkins Issue Type: Bug Components: build-flow Environment: Jenkins 1.465 Build Flow 0.3 Red Hat Enterprise Linux 5.5 64 bit Sun Java 1.6.0_20 Reporter: Ben Golding Assignee: Nicolas De Loof Priority: Minor Attachments: console.log, DSL.txt Trying to run a moderately complex DSL (see attached DSL.txt) causes an exception near to the end of the build (see attached console.log) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
