-
Bug
-
Resolution: Fixed
-
Major
-
None
GitHubCommitNotifier is throwing a (very helpful) exception which causes the build to fail. This started this morning without things being changed on our end.
At first I thought it was due to the upgrade to 1.570 but even after downgrading to 1.569 it did not resolve the issue.
The exception that is being thrown in the console is:
15:09:57 Publishing Clover coverage report...
15:09:57 Publishing Clover XML report...
15:09:57 Publishing Clover coverage results...
15:09:57 Recording test results
15:09:58 ERROR: Publisher com.cloudbees.jenkins.GitHubCommitNotifier aborted due to exception
15:09:58 java.lang.NullPointerException
15:09:58 at com.cloudbees.jenkins.GitHubCommitNotifier.perform(GitHubCommitNotifier.java:53)
15:09:58 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
15:09:58 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:772)
15:09:58 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:736)
15:09:58 at hudson.model.Build$BuildExecution.post2(Build.java:183)
15:09:58 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:685)
15:09:58 at hudson.model.Run.execute(Run.java:1757)
15:09:58 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
15:09:58 at hudson.model.ResourceController.execute(ResourceController.java:88)
15:09:58 at hudson.model.Executor.run(Executor.java:234)
- is related to
-
JENKINS-25312 GitHubCommitNotifier: Make the build result configurable on commit update failure
- Resolved