Hi all,
I'm playing around with some fairly straight line jobs hooked up via the paramterized trigger plugin. I'm building the jobs via the Job DSL plugin, but I don't believe this will have an effect here. When I try to trigger my sample root job in my pipeline, I'm getting the following exception: At revision 119303 [workspace] $ powershell.exe "& 'C:\Users\EDDIES~1\AppData\Local\Temp\3\hudson7036549510980740414.ps1'" hello FATAL: nulljava.lang.NullPointerException <http://stacktrace.jenkins-ci.org/search?query=java.lang.NullPointerException> at hudson.plugins.parameterizedtrigger.ResultCondition$3.isMet(ResultCondition.java:19) <http://stacktrace.jenkins-ci.org/search/?query=hudson.plugins.parameterizedtrigger.ResultCondition$3.isMet&entity=method> at hudson.plugins.parameterizedtrigger.BuildTriggerConfig.perform2(BuildTriggerConfig.java:330) <http://stacktrace.jenkins-ci.org/search/?query=hudson.plugins.parameterizedtrigger.BuildTriggerConfig.perform2&entity=method> at hudson.plugins.parameterizedtrigger.BlockableBuildTriggerConfig.perform2(BlockableBuildTriggerConfig.java:57) <http://stacktrace.jenkins-ci.org/search/?query=hudson.plugins.parameterizedtrigger.BlockableBuildTriggerConfig.perform2&entity=method> at hudson.plugins.parameterizedtrigger.TriggerBuilder.perform(TriggerBuilder.java:85) <http://stacktrace.jenkins-ci.org/search/?query=hudson.plugins.parameterizedtrigger.TriggerBuilder.perform&entity=method> at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) <http://stacktrace.jenkins-ci.org/search/?query=hudson.tasks.BuildStepMonitor$1.perform&entity=method> at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractBuild$AbstractBuildExecution.perform&entity=method> at hudson.model.Build$BuildExecution.build(Build.java:199) <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Build$BuildExecution.build&entity=method> at hudson.model.Build$BuildExecution.doRun(Build.java:160) <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Build$BuildExecution.doRun&entity=method> at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533) <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractBuild$AbstractBuildExecution.run&entity=method> at hudson.model.Run.execute(Run.java:1745) <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Run.execute&entity=method> at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.FreeStyleBuild.run&entity=method> at hudson.model.ResourceController.execute(ResourceController.java:89) <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.ResourceController.execute&entity=method> at hudson.model.Executor.run(Executor.java:240) <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Executor.run&entity=method> The job I'm testing out here does a simple subversion checkout, then runs a 'hello' powershell script. It then triggers a bunch of downstream jobs, the exact list is: trunk/full_build_trunk,trunk/unit_tests_trunk,trunk/DB_migration_tests_trunk,trunk/DB_integration_tests_trunk I've stepped through the plugin code on github, and it seems that the build object being passed most of the way through this stack trace is null. Any ideas on what I can do to try to address this? Would this be better off in the dev google group? The parameterized trigger plugin is version 2.25, and jenkins itself is 1.579 Cheers, Eddie -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
