Ive looked at the stack trace, and it seems that some how there is a null added to a rule
set, as the nullpointerexception points to
RuleResult result = rule.evaluate(build);

For a null pointer to happen there, it seems that rule has to be null. Are you still seeing
this problem, and if so could help me out investigating it`? I realize that Im 3 months
late and you have probably stopped using the plugin.

thanks for picking this up...

I need to check if with the current version of Hudson and of the CI plugin the exception is present in the
log files.

will report on the findings very soon.

thanks for picking this up...

I need to check if with the current version of Hudson and of the CI plugin the exception is present in the
log files.

will report on the findings very soon.

Hello,

still experiencing the issue with Hudson 1.320 and ci-game 1.12

[TASKS] Scanning workspace files for tasks...
[TASKS] Found 0 annotations (0 new, 0 high, 0 normal, 0 low)
[TASKS] Not changing build status, since no threshold has been exceeded
[WARNINGS] Parsing warnings in console log...
[WARNINGS] Found 0 annotations (0 new, 0 high, 0 normal, 0 low)
[WARNINGS] Not changing build status, since no threshold has been exceeded
No emails were triggered.
FATAL: null
java.lang.NullPointerException
at
hudson.plugins.cigame.rules.plugins.violation.DefaultViolationRule.getTypeReportCount(DefaultViolationRule.java:50)
at
hudson.plugins.cigame.rules.plugins.violation.DefaultViolationRule.evaluate(DefaultViolationRule.java:32)
at hudson.plugins.cigame.model.ScoreCard.record(ScoreCard.java:34)
at hudson.plugins.cigame.model.ScoreCard.record(ScoreCard.java:51)
at hudson.plugins.cigame.GamePublisher.perform(GamePublisher.java:45)
at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:480)
at
hudson.model.AbstractBuild$AbstractRunner.performAllBuildStep(AbstractBuild.java:466)
at
hudson.model.AbstractBuild$AbstractRunner.performAllBuildStep(AbstractBuild.java:454)
at hudson.model.Build$RunnerImpl.cleanUp(Build.java:150)
at hudson.model.Run.run(Run.java:1132)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:93)
at hudson.model.Executor.run(Executor.java:122)

Oops, recently I couldn't leave a comment, now that works. I want to add, I have
the same problem, also the NPE in DefaultViolationRule.java:50. I recently
updated to 1.12 and it worked fine, builds got points. After some days from one
build to another the builds no longer get points. One exception: A failing build
and the build bringing it to normal got points. I have no idea to workaroiund
this problem, so at the moment in my company the people can't get scores.

Code changed in hudson
User: : redsolo
Path:
trunk/hudson/plugins/ci-game/src/main/java/hudson/plugins/cigame/rules/plugins/opentasks/DefaultOpenTasksRule.java
trunk/hudson/plugins/ci-game/src/main/java/hudson/plugins/cigame/rules/plugins/violation/DefaultViolationRule.java
trunk/hudson/plugins/ci-game/src/test/java/hudson/plugins/cigame/rules/plugins/violation/DefaultViolationRuleIntegrationTest.java
trunk/hudson/plugins/ci-game/src/test/java/hudson/plugins/cigame/rules/plugins/violation/DefaultViolationRuleTest.java
trunk/hudson/plugins/ci-game/src/test/resources/hudson/plugins/cigame/rules/plugins/violation/DefaultViolationRuleIntegrationTest.zip
http://fisheye4.cenqua.com/changelog/hudson/?cs=21343
Log:
JENKINS-3726 - Now violation rule lets the Violation action to calculate the number of warnings.