Determine if Secure jobs are configured based on CI configuration alone
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
A previous issue was played with allowed Secure jobs to be found for a pipeline #13662 (closed). To determine if Secure jobs will run in the future, the issue searched for artifacts:reports:{sast | dast | ...} entries in the latest run pipeline for the project.
While the above technical solution works for the majority of cases, it does not work in all cases. There are times when a project has CI configured and has never run a pipeline. One example of this is when a project is imported using a URL.
This issue determines whether or not Secure jobs are configured based on the contents of the .gitlab-ci.yml file. Note there may also be a requirement to use environment variables, as variables such as SAST_DISABLED will disable the Secure job.