-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
Jenkins LTS 2.401.1
-
-
v23.7.22.0
We do have some Jenkins Builds with a Post-Build-Action "Upload and Scan with Veracode".
Since update of the veracode plugin from 23.4.20.0 to 23.5.21.0 all of this build are marked as failed:
08:48:10 [Debug mode is on] 08:48:10 08:48:10 Can Fail Build? 08:48:10 true 08:48:10 08:48:10 Show Unstable Status for Failed Policy Evaluation? 08:48:10 true 08:48:10 08:48:10 Version information: 08:48:10 VeracodeJavaAPI v23.4.11.2 cUnknown ... 08:48:12 [2023.06.21 08:48:12.316] Creating a new analysis with name "master #410". 08:48:12 [2023.06.21 08:48:12.317] Invoking API https://analysiscenter.veracode.com/api/5.0/createbuild.do ... 08:48:13 [2023.06.21 08:48:13.896] The analysis id of the new analysis is "26930158". ... 08:48:29 [2023.06.21 08:48:29.788] Getting response status code from HTTP response message 08:48:31 [2023.06.21 08:48:31.223] Server returned HTTP response code: 200 08:48:31 [2023.06.21 08:48:31.223] Retry is not required 08:48:31 [2023.06.21 08:48:31.223] Connecting to response input stream 08:48:31 [2023.06.21 08:48:31.223] Reading response input stream 08:48:31 [2023.06.21 08:48:31.223] Close response input stream 08:48:31 [2023.06.21 08:48:31.225] 08:48:31 [2023.06.21 08:48:31.225] Scan polling interval is set to the default of 120 seconds. 08:48:31 [2023.06.21 08:48:31.226] 08:48:31 [2023.06.21 08:48:31.226] Application "XXXXX" sandbox "master" analysis "master #410" will be automatically submitted for scanning if the pre-scan verification is successful. 08:48:31 [2023.06.21 08:48:31.226] Wrapper return code 0 = Success 08:48:31 08:48:31 Build step 'Upload and Scan with Veracode' marked build as failure 08:48:31 Email was triggered for: Failure - Any 08:48:31 Email was triggered for: Always 08:48:31 Sending email for trigger: Failure - Any 08:48:36 Finished: FAILURE
The Veracode scan is started successfull. "Wait for Scan to Complete" is not marked. So the build should be marked successfull after triggering the scan.