Context

We have a self-hosted gitlab ultimate plan (omnibus package on debian):

We’re at gitlab 13.0 and runners 13.0.

We tried to run sast, so we followed https://docs.gitlab.com/ee/user/application_security/sast/ :

• adding to .gitlab-ci.yaml:

   include:
     - template: SAST.gitlab-ci.yml
  

• including the template to the project:
  

  

  image1112×206 14.5 KB

The result of the setup above

image698×524 24.7 KB

What we expect to see

Running pipeline, we’ve added the SAST template and we have the ultimate plan, so it is expected to work properly.

We have checked:

• https://gitlab.com/gitlab-org/gitlab-foss/-/issues/62624 - but we do have the ultimate plan, so that’s not the problem
• https://gitlab.com/gitlab-org/gitlab/-/issues/32412 - is about bandit-sast job: stage parameter should be check, which is something different

What we want to know

What are we doing wrong?

OK, found it… apparently, there needs to be a test stage.

But running into a different issue now: the generated report cannot be found:

Running after_script 00:01

[34](...#L34)Uploading artifacts for failed job    00:02

[35](...#L35) Uploading artifacts...

[36](...#L36) WARNING: gl-sast-report.json: no matching files

[37](...#L37) ERROR: No files to upload

[39](...#L39) ERROR: Job failed: exit code 1

Can I ask if you found a solution to this error? or what fixed it?