Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: checkmarx-plugin
-
Labels:None
-
Environment:checkmarx-plugin 8.1.0-1
jenkins 2.8
-
Similar Issues:
Description
Appears when listing the build history and trying to create the trend graph.
I consistently get NPEs in the logs from the CxScanResult.java class, whenever the "owner" variable is referenced. Please ensure the owner object is NOT null in the code:
public final AbstractBuild<?, ?> owner;
Example:
Caused by: java.lang.NullPointerException
at com.checkmarx.jenkins.CxScanResult.getPreviousResult(CxScanResult.java:225)
at com.checkmarx.jenkins.CxProjectResult.buildDataSet(CxProjectResult.java:176)
at com.checkmarx.jenkins.CxProjectResult.doGraph(CxProjectResult.java:131)
Another side affect is all of the buids are listed as failed with timestamp Dec 31, 1969, even though the scan was successful in the console log.
Attachments
Activity
This bug was solved on a new plugin
You can download this version from:
http://download.checkmarx.com/8.0.1/Plugins/CxJenkins-8.0.1.3.zip
Checkmarx Support
added a comment - This bug was solved on a new plugin
You can download this version from:
http://download.checkmarx.com/8.0.1/Plugins/CxJenkins-8.0.1.3.zip Same issue with the version you provided.
I noticed in the build files, eg:
jobs/job-name/builds/30/build.xml
there is a
<logger>
element that is breaking the parsing. If I remove that from the xml of all the builds, it is parsing fine with the graph.
Any idea why that logger is in this file, and how to turn it off?
When I install a fresh jenkins (identical versions of jenkins and plugin), the build files do not have that element and is working fine.
thanks.
Gerald Killeen
added a comment - Same issue with the version you provided.
I noticed in the build files, eg:
jobs/job-name/builds/30/build.xml
there is a
<logger>
element that is breaking the parsing. If I remove that from the xml of all the builds, it is parsing fine with the graph.
Any idea why that logger is in this file, and how to turn it off?
When I install a fresh jenkins (identical versions of jenkins and plugin), the build files do not have that element and is working fine.
thanks. Are you using "upgrade" method for the plugin or - uninstall and new installation of the plugin?
Checkmarx Support
added a comment - Are you using "upgrade" method for the plugin or - uninstall and new installation of the plugin? I have done an uninstall/reinstall of the plugin about 1 month ago, as well as upgrades.
If you have proper upgrade steps please provide them.
Thanks.
Gerald Killeen
added a comment - I have done an uninstall/reinstall of the plugin about 1 month ago, as well as upgrades.
If you have proper upgrade steps please provide them.
Thanks. I dont have any special instructions but you wrote that if installing all from fresh - all is OK, so i thought of an issue with the upgrade procedure against uninstall-new install procedure.. - If you are now completely uninstalls the Cx Plugin (new version that we sent you) and install it again from scratch - the logger issue still exists?
Checkmarx Support
added a comment - I dont have any special instructions but you wrote that if installing all from fresh - all is OK, so i thought of an issue with the upgrade procedure against uninstall-new install procedure.. - If you are now completely uninstalls the Cx Plugin (new version that we sent you) and install it again from scratch - the logger issue still exists? 
An issue for Dev - Plugin was opened.