[JIRA] (JENKINS-59178) Nullpointer exception in IssuesAggregator.updateMap

[kent.granstrom@comhem.se (JIRA)]

Kent Granström created an issue

Jenkins / JENKINS-59178 Nullpointer exception in IssuesAggregator.updateMap Issue Type: Bug Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-09-02 09:50 Environment: Windows server 2016, Jenkins 2.189 Priority: Major Reporter: Kent Granström Running a multi-config job and "flexible publish" and in that matching strings for configuration resulting in that one of those executes MSTest. The resulting file(s) is then parsed by the "Record compiler warnings and static analysis" -plugin". Both individual configurations results in "success" but the main part always results in FAILURE with the following in the log: 00:08:21.581 FATAL: null*00:08:21.583* java.lang.NullPointerException*00:08:21.583* at io.jenkins.plugins.analysis.core.steps.IssuesAggregator.updateMap(IssuesAggregator.java:87)00:08:21.583 at io.jenkins.plugins.analysis.core.steps.IssuesAggregator.endRun(IssuesAggregator.java:64)00:08:21.583 at hudson.matrix.DefaultMatrixExecutionStrategyImpl.notifyEndBuild(DefaultMatrixExecutionStrategyImpl.java:222)00:08:21.583 at hudson.matrix.DefaultMatrixExecutionStrategyImpl.run(DefaultMatrixExecutionStrategyImpl.java:165)00:08:21.583 at hudson.matrix.MatrixBuild$MatrixBuildExecution.doRun(MatrixBuild.java:375)00:08:21.583 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)00:08:21.583 at hudson.model.Run.execute(Run.java:1815)00:08:21.583 at hudson.matrix.MatrixBuild.run(MatrixBuild.java:323)00:08:21.583 at hudson.model.ResourceController.execute(ResourceController.java:97)00:08:21.583 at hudson.model.Executor.run(Executor.java:429) Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[kent.granstrom@comhem.se (JIRA)]

Kent Granström updated an issue

Jenkins / JENKINS-59178 Nullpointer exception in IssuesAggregator.updateMap

Change By: Kent Granström Running a multi-config job and "flexible publish" and in that matching strings for configuration resulting in that one of those executes MSTest. The resulting file(s) is then parsed by the "Record compiler warnings and static analysis" -plugin". Both individual configurations results in "success" but the main part always results in FAILURE with the following in the log: {noformat} * 00:08:21.581 * FATAL: null * 00:08:21.583 * java.lang.NullPointerException*00:08:21.583*  at io.jenkins.plugins.analysis.core.steps.IssuesAggregator.updateMap(IssuesAggregator.java:87) * 00:08:21.583 *   at io.jenkins.plugins.analysis.core.steps.IssuesAggregator.endRun(IssuesAggregator.java:64) * 00:08:21.583 *   at hudson.matrix.DefaultMatrixExecutionStrategyImpl.notifyEndBuild(DefaultMatrixExecutionStrategyImpl.java:222) * 00:08:21.583 *   at hudson.matrix.DefaultMatrixExecutionStrategyImpl.run(DefaultMatrixExecutionStrategyImpl.java:165) * 00:08:21.583 *   at hudson.matrix.MatrixBuild$MatrixBuildExecution.doRun(MatrixBuild.java:375) * 00:08:21.583 *   at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) * 00:08:21.583 *   at hudson.model.Run.execute(Run.java:1815) * 00:08:21.583 *   at hudson.matrix.MatrixBuild.run(MatrixBuild.java:323) * 00:08:21.583 *   at hudson.model.ResourceController.execute(ResourceController.java:97) * 00:08:21.583 *   at hudson.model.Executor.run(Executor.java:429) Running a multi-config job and "flexible publish" and in that matching strings for configuration resulting in that one of those executes MSTest. The resulting file(s) is then parsed by the "Record compiler warnings and static analysis" -plugin". Both individual configurations results in "success" but the main part always results in FAILURE with the following in the log:{noformat}

Add Comment

[kent.granstrom@comhem.se (JIRA)]

Kent Granström updated an issue

Jenkins / JENKINS-59178 Nullpointer exception in IssuesAggregator.updateMap Change By: Kent Granström

Running a multi-config job and "flexible publish" and in that matching strings for configuration resulting in that one of those executes MSTest. The resulting file(s) is then parsed by the "Record compiler warnings and static analysis" -plugin". Both individual configurations results in "success" but the main part always results in FAILURE with the following in the log:

{noformat} 00:08:21.581 FATAL: null 00:08:21.583 java.lang.NullPointerException*00:08:21.583* at io.jenkins.plugins.analysis.core.steps.IssuesAggregator.updateMap(IssuesAggregator.java:87) 00:08:21.583 at io.jenkins.plugins.analysis.core.steps.IssuesAggregator.endRun(IssuesAggregator.java:64) 00:08:21.583 at hudson.matrix.DefaultMatrixExecutionStrategyImpl.notifyEndBuild(DefaultMatrixExecutionStrategyImpl.java:222) 00:08:21.583 at hudson.matrix.DefaultMatrixExecutionStrategyImpl.run(DefaultMatrixExecutionStrategyImpl.java:165) 00:08:21.583 at hudson.matrix.MatrixBuild$MatrixBuildExecution.doRun(MatrixBuild.java:375) 00:08:21.583 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) 00:08:21.583 at hudson.model.Run.execute(Run.java:1815) 00:08:21.583 at hudson.matrix.MatrixBuild.run(MatrixBuild.java:323) 00:08:21.583 at hudson.model.ResourceController.execute(ResourceController.java:97) 00:08:21.583 at hudson.model.Executor.run(Executor.java:429)

Running a multi-config job and "flexible publish" and in that matching strings for configuration resulting in that one of those executes MSTest. The resulting file(s) is then parsed by the "Record compiler warnings and static analysis" -plugin". Both individual configurations results in "success" but the main part always results in FAILURE with the following in the log: {noformat}

Add Comment

[kent.granstrom@comhem.se (JIRA)]

Kent Granström updated an issue

Jenkins / JENKINS-59178 Nullpointer exception in IssuesAggregator.updateMap Change By: Kent Granström

Running a multi-config job and "flexible publish" and in that matching strings for configuration resulting in that one of those executes MSTest. The resulting file(s) is then parsed by the "Record compiler warnings and static analysis" -plugin". Both individual configurations results in "success" but the main part always results in FAILURE with the following in the log:   {noformat} 00:08:21.581 FATAL: null

00:08:21.583 java.lang.NullPointerException * 00:08:21.583 * at io.jenkins.plugins.analysis.core.steps.IssuesAggregator.updateMap(IssuesAggregator.java:87)

00:08:21.583 at io.jenkins.plugins.analysis.core.steps.IssuesAggregator.endRun(IssuesAggregator.java:64) 00:08:21.583 at hudson.matrix.DefaultMatrixExecutionStrategyImpl.notifyEndBuild(DefaultMatrixExecutionStrategyImpl.java:222) 00:08:21.583 at hudson.matrix.DefaultMatrixExecutionStrategyImpl.run(DefaultMatrixExecutionStrategyImpl.java:165) 00:08:21.583 at hudson.matrix.MatrixBuild$MatrixBuildExecution.doRun(MatrixBuild.java:375) 00:08:21.583 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) 00:08:21.583 at hudson.model.Run.execute(Run.java:1815) 00:08:21.583 at hudson.matrix.MatrixBuild.run(MatrixBuild.java:323) 00:08:21.583 at hudson.model.ResourceController.execute(ResourceController.java:97) 00:08:21.583 at hudson.model.Executor.run(Executor.java:429)

{noformat}

Add Comment

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner commented on JENKINS-59178

Re: Nullpointer exception in IssuesAggregator.updateMap Can you please also provide a snippet of the corresponding steps in your Jenkinsfile?

Add Comment

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner edited a comment on JENKINS-59178

Re: Nullpointer exception in IssuesAggregator.updateMap

Can you please also provide a snippet of the corresponding steps in your Jenkinsfile? Or are you using different tool IDs (for the warnings parsers) for the different nodes?

Add Comment

[kent.granstrom@comhem.se (JIRA)]

Kent Granström commented on JENKINS-59178

Re: Nullpointer exception in IssuesAggregator.updateMap

We are only running the warnings plugin on one of the configurations, debug/release.

Add Comment

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner commented on JENKINS-59178

Re: Nullpointer exception in IssuesAggregator.updateMap

So you job is configured using the UI and not a Jenkinsfile?

Add Comment

[kent.granstrom@comhem.se (JIRA)]

Kent Granström commented on JENKINS-59178

Re: Nullpointer exception in IssuesAggregator.updateMap

Yes. It is a traditional jenkins multi-config job.

Add Comment

[kent.granstrom@comhem.se (JIRA)]

Kent Granström commented on JENKINS-59178

Re: Nullpointer exception in IssuesAggregator.updateMap

Does anyone know if there is a workaround for this?

Add Comment

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner commented on JENKINS-59178

Re: Nullpointer exception in IssuesAggregator.updateMap

Since I can't reproduce this bug yet I just can guess: you can try to enable the warnings plugin for all configurations.

Add Comment

[kent.granstrom@comhem.se (JIRA)]

Kent Granström commented on JENKINS-59178

Re: Nullpointer exception in IssuesAggregator.updateMap

Will do that tomorrow morning. Thanks

Add Comment

[kent.granstrom@comhem.se (JIRA)]

Kent Granström commented on JENKINS-59178

Re: Nullpointer exception in IssuesAggregator.updateMap

Ulli Hafner : Have to get back to you on this one since we have serious crumb-problems with the latest version (2.193) of Jenkins itself.

Add Comment

[kent.granstrom@comhem.se (JIRA)]

Kent Granström assigned an issue to Kent Granström

Jenkins / JENKINS-59178 Nullpointer exception in IssuesAggregator.updateMap

Change By: Kent Granström Assignee: Ulli Hafner Kent Granström

Add Comment

[kent.granstrom@comhem.se (JIRA)]

Kent Granström assigned an issue to Unassigned

Jenkins / JENKINS-59178 Nullpointer exception in IssuesAggregator.updateMap

Change By: Kent Granström Assignee: Kent Granström

Add Comment

[kent.granstrom@comhem.se (JIRA)]

Kent Granström assigned an issue to Ulli Hafner

Jenkins / JENKINS-59178 Nullpointer exception in IssuesAggregator.updateMap

Change By: Kent Granström Assignee: Ulli Hafner

Add Comment

[kent.granstrom@comhem.se (JIRA)]

Kent Granström commented on JENKINS-59178

Re: Nullpointer exception in IssuesAggregator.updateMap

Have now had some more time to dig into this and it appears as it wasn't the MSTest that caused this. It was the FxCop part in the "Record compiler warnings and static analysis results" that caused the problem. It was for some reason configured in the same group as the MSTest hence it was only executed in one of the configurations (Debug in this case). Moving it to the common part so that it is executed in both configurations yields a green build.  Is it a bug that it fails the build with an exception if it is run in one branch of a multi-config job? Perhaps it is... To me it is probably something that I would look into in order to handle corner-cases..  So, what should we do with this issue? Close it or improve the plugin? Think I'll leave it to you hackers out there

Add Comment

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner started work on JENKINS-59178

Change By: Ulli Hafner Status: Open In Progress

Add Comment

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner updated an issue

Jenkins / JENKINS-59178 Nullpointer exception in IssuesAggregator.updateMap

Change By: Ulli Hafner URL: https://github.com/jenkinsci/warnings-ng-plugin/pull/195

Add Comment

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner updated JENKINS-59178

Jenkins / JENKINS-59178 Nullpointer exception in IssuesAggregator.updateMap

Change By: Ulli Hafner Status: In Progress Fixed but Unreleased Resolution: Fixed

Add Comment

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner updated JENKINS-59178

Jenkins / JENKINS-59178 Nullpointer exception in IssuesAggregator.updateMap

Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: https://github.com/jenkinsci/warnings-ng-plugin/releases/tag/warnings-ng-6.0.1

Add Comment