You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have tested a new jenkins-slave-zap that uses newer versions of the plugins and, unsurprisignly, it does not work with older versions of the Sonarube ZAP plugin.
We need to test this with the newer version and, if it works right, we will need to make sure the jenkins-slave-zap image is appropriately taged and versioned so that the right one can be picked depending on the version of sonarqube/zap being used in the pipeline.
I have tested executing a scan with an updated version of the jenkins-slave-zap and, unfortunately, the report doesn't seem to be displaying the stats in the projects homepage.
There is a discussion on the SonarQube forums that seems to highlight the same issue we're experiencing, although with different plugins/scanners.
The suggestions/solutions don't seem consistent and do not apply to our configuration as far as i can tell, I haven't anyway tried them all (at least yet) for lack of time.
There appears to be an issue with the summary report not showing up that we'll have to address. You have to drill into the issues to see the results.
Refer to this link for details and examples:
#14 (comment)
The text was updated successfully, but these errors were encountered: