-
Bug
-
Resolution: Fixed
-
Critical
-
None
-
Jenkins 2.135
Cppcheck 1.23 crashes with:
13:13:42 [Cppcheck] Starting the cppcheck analysis. 13:13:42 ERROR: Build step failed with exception 13:13:42 java.lang.NullPointerException 13:13:42 at org.jenkinsci.plugins.cppcheck.CppcheckPublisher.perform(CppcheckPublisher.java:387) 13:13:42 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 13:13:42 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) 13:13:42 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) 13:13:42 at hudson.model.Build$BuildExecution.post2(Build.java:186) 13:13:42 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635) 13:13:42 at hudson.model.Run.execute(Run.java:1840) 13:13:42 at hudson.matrix.MatrixRun.run(MatrixRun.java:153) 13:13:42 at hudson.model.ResourceController.execute(ResourceController.java:97) 13:13:42 at hudson.model.Executor.run(Executor.java:429) 13:13:42 Build step 'Publish Cppcheck results' marked build as failure
[JENKINS-52854] NPE with Cppcheck plugin 1.23
| Comment |
[ I've tried the nightly build (1.24-SNAPSHOT (private-5ed649ae-jenkins) )- and I have noticed one problem: bq. The help text indicate that cppcheck should generate output files with names in the form specifies the generated Cppcheck XML report files, such as '**/cppcheck-result-*.xml'. That suggestion is not compatible with the name mentioned lower in the same help text: {quote}**/cppcheck-result*.xml{quote} I suggest using the same wildcard name in both lines. ] |
| Comment | [ You are right, sorry. I'll delete it. ] |
Marco Steffan
made changes -
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Marco Steffan
made changes -
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
