JPhor537964 (Community Member) asked a question.
Pipeline Scan Halted While Analysis Has Been Started. Any places that we could keep track or debug what else goes wrong?
Job that failed unexpectedlyFindings:
- It was veracode side to cause such issue reason being with the second retry without any configuration or code changes, the new job able to finish up the scanning/analysis
.png){kind=logo}
Hello @JPhor537964 (Community Member) ,
Thank you for reaching out to the Community.
Would you happen to have the rest of the output?
Also to enable additional detailed results in the pipeline scan, I would recommend using --verbose.
I have included this information from the help center.
https://docs.veracode.com/r/r_pipeline_scan_commands
Kind regards,
Steven
Veracode Support Engineer
hi Steven,
I don't have the details output due to verbose mode is not turned on and the issue is not reproducible. Got an answer from veracode technical support whereby tracking is not possible for pipeline scan. Will update this thread again with the details output when issue happened again.
Thanks