SAST include not working on new projects

How to Use GitLab Self-managed
1

We have existing groups and projects where SAST scans are working using the default yml when enabling SAST:

stages:

  • test
    sast:
    stage: test
    include:
  • template: Security/SAST.gitlab-ci.yml

However, when new projects are created under the same pre-existing group the scan is no longer getting invoked. I compared new and old projects and don’t see any configuration(s) that would prevent it from working on new.

Any suggestions?

Current version:

gitlab-ce[15.8.1]

2

Are the pipelines triggered or not at all?
Do the new projects have .gitlab-ci.yml?
Do you have AutoDevOps turned off?

1 Like
3

Hi and thanks for following up!

Pipeline does not trigger at all

Yes they have .gitlab-ci.yml

Yes AutoDevOps it is turned off

4

If you try to open the Pipeline Editor what does it say?

1 Like
5

Hello,
Forgive my insanely delayed reply got pulled into other priorities. To follow up on this here is what the UI shows when I try to run the pipeline manually:

image
image1851×259 14.1 KB

The contents of .gitlab-ci.yml is the system default when enabling SAST:
stages:

  • test

sast:

stage: test

include:

  • template: Security/SAST.gitlab-ci.yml