-
Bug
-
Resolution: Fixed
-
Major
-
None
Enviroment:
.Gnu build
.Coverity analysis added as Post build action
."Mark build as unstable if matching defects are found" option selected
Everything runs fine but in the end Coverity marks build as unstable even though 0 matching defects are found. Note that this only occurs when jenkins build was already marked as unstable due to prior matching Coverity errors. But when all errors are fixed, Jenkins should go back to stable.
Here is the console output:
New snapshot ID 10191 added.
Elapsed time: 00:01:24
[Coverity] deleting intermediate directory
Cim Streams: 1
Snapsho Size: 1
[Coverity] Found snapshot IDs [10191]
[Coverity] Fetching defects for stream service
[Coverity] Found 711 defects
[Coverity] No defects matched all filters.
Coverity details: http://jenkins_server:8080/job/SERVICE_BUILD/1562/coverity_Coverity_417_ServiceProject_service
Build step 'Coverity' changed build result to UNSTABLE