[JIRA] (JENKINS-15519) BuildFlow job randomly fails with FATAL: null java.lang.NullPointerException
Ben Golding resolved JENKINS-15519 as Fixed BuildFlow job randomly fails with FATAL: null java.lang.NullPointerException JENKINS-13915 now marked fixed (in 0.8), also marking this one as fixed. Change By: Ben Golding (12/Mar/13 10:59 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-15519) BuildFlow job randomly fails with FATAL: null java.lang.NullPointerException
Ben Golding commented on JENKINS-15519 BuildFlow job randomly fails with FATAL: null java.lang.NullPointerException (copy of my comment from JENKINS-13915) 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-15519) BuildFlow job randomly fails with FATAL: null java.lang.NullPointerException
Ulf Bamberg commented on JENKINS-15519 BuildFlow job randomly fails with FATAL: null java.lang.NullPointerException i noticed there's a similar bug report: https://issues.jenkins-ci.org/browse/JENKINS-13915 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-15519) BuildFlow job randomly fails with FATAL: null java.lang.NullPointerException
Ulf Bamberg updated JENKINS-15519 BuildFlow job randomly fails with FATAL: null java.lang.NullPointerException Change By: Ulf Bamberg (26/Nov/12 9:20 AM) Environment: build-flow 0.5jenkins 1.491 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-15519) BuildFlow job randomly fails with FATAL: null java.lang.NullPointerException
Erik Lovlie commented on JENKINS-15519 BuildFlow job randomly fails with FATAL: null java.lang.NullPointerException Same here. Stack trace is nearly the same. 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-15519) BuildFlow job randomly fails with FATAL: null java.lang.NullPointerException
Scott Sandler commented on JENKINS-15519 BuildFlow job randomly fails with FATAL: null java.lang.NullPointerException I'm seeing this issue intermittently as well, same exact stack trace. 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-15519) BuildFlow job randomly fails with FATAL: null java.lang.NullPointerException
Ulf Bamberg created JENKINS-15519 BuildFlow job randomly fails with FATAL: null java.lang.NullPointerException Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Attachments: build-cfg.txt, console-output.txt Components: build-flow Created: 15/Oct/12 7:35 AM Description: Hi, we implemented our build pipeline with build-flow. The pipeline has several parallel and serial configured jobs. Since we are using this plugin, we are noticing randomly appearing build breaks. The stacktrace starts with org.codehaus.groovy.runtime.callsite.GetEffectivePojoPropertySite.acceptGetProperty(GetEffectivePojoPropertySite.java:51), thus i'm supposing a relation between the NPE and the parameter that is set with every job i run. It's representing a global build number that is used throught the whole pipeline. The configuration and console output is attached below. The build (only the buildflow job) always breaks after the big parallel execution part. It occurs in about every fifth build. Because the build is triggered multiple times a day due to the continuous delivery pattern and lasts 30 minutes , this bug is really annoying -> high priority Project: Jenkins Labels: plugin Priority: Critical Reporter: Ulf Bamberg 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
