-
Notifications
You must be signed in to change notification settings - Fork 0
BuildTriggerException on 0.2.2 build #4
Description
Hi,
I just tried the 0.2.2 build and i get below exception in the UI. I can see the builds are triggered, but i just see this exception in the build config.
jetbrains.buildServer.buildTriggers.BuildTriggerException
jetbrains.buildServer.buildTriggers.BuildTriggerException
at jetbrains.buildServer.serverSide.impl.BuildTriggersChecker.callTrigger(BuildTriggersChecker.java:91)
at jetbrains.buildServer.serverSide.impl.BuildTriggersChecker.access$1100(BuildTriggersChecker.java:28)
at jetbrains.buildServer.serverSide.impl.BuildTriggersChecker$BuildTriggersGroup.processTriggers(BuildTriggersChecker.java:17)
at jetbrains.buildServer.serverSide.impl.BuildTriggersChecker.triggerBuilds(BuildTriggersChecker.java:116)
at jetbrains.buildServer.serverSide.impl.BuildServerRunner$4.doSomething(BuildServerRunner.java)
at jetbrains.buildServer.serverSide.impl.BuildServerRunner$BuildServerWorker.runAction(BuildServerRunner.java:5)
at jetbrains.buildServer.serverSide.impl.BuildServerRunner$BuildServerWorker.run(BuildServerRunner.java:41)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.NullPointerException
at org.tkirill.teamcity.bisectPlugin.BisectBuildTriggerHelper.processBisect(BisectBuildTriggerHelper.java:37)
at org.tkirill.teamcity.bisectPlugin.BisectBuildTriggerHelper.triggerBuild(BisectBuildTriggerHelper.java:28)
at org.tkirill.teamcity.bisectPlugin.BisectBuildTriggerPolicy.triggerBuild(BisectBuildTriggerPolicy.java:27)
at jetbrains.buildServer.serverSide.impl.BuildTriggersChecker$4.run(BuildTriggersChecker.java)
at jetbrains.buildServer.util.NamedThreadFactory.executeWithNewThreadName(NamedThreadFactory.java:89)
at jetbrains.buildServer.serverSide.impl.BuildTriggersChecker.callTrigger(BuildTriggersChecker.java:39)
... 7 more