Create Security::Scan records as soon as the job completes
What does this MR do and why?
In !199032 (merged), we are looking to change the available reports check to use security_scans instead of job_artifacts. However, there is a risk of a timing issue since security scans are created asynchronously. This MR creates scans in the created status as soon as the build completes, so that the security scan records are available sooner.
References
Screenshots or screen recordings
| Before | After |
|---|---|
How to set up and validate locally
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Edited by Brian Williams