Pipelines that include `SAST.latest.gitlab-ci.yml` have been broken
Summary
The last update of the template probably missed this keyword: extends: .sast-analyzer
in the flawfinder-sast
job
Steps to reproduce
Any pipeline with non-default stages (the test
for this issue)
include:
- template: 'Jobs/SAST.latest.gitlab-ci.yml'
stages:
- Test
- Build
...
...
sast:
before_script: []
stage: Test
Example Project
What is the current bug behavior?
The error was raised
Unable to create pipeline
flawfinder-sast job: chosen stage does not exist; available stages are .pre, Build, Test,
What is the expected correct behavior?
Relevant logs and/or screenshots
Output of checks
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
)(we will only investigate if the tests are passing)
Possible fixes
Add extends: .sast-analyzer
to the flawfinder-sast
job definition
flawfinder-sast:
extends: .sast-analyzer
script:
See MR: !151123 (closed)
Edited by Liubomyr Shkil