gitlab dont analyze gl-sast-report.json

[iluwaa]

i have job `sast: stage: test only:

• /^feature\/*/ script:
  • git checkout origin/dev
  • git merge %CI_COMMIT_SHA% --no-commit --no-ff
  • dotnet sonarscanner begin /k:%CI_PROJECT_NAME% /d:sonar.gitlab.project_id=%CI_PROJECT_PATH% /d:sonar.gitlab.commit_sha=%CI_COMMIT_SHA% /d:sonar.gitlab.ref_name=%CI_COMMIT_REF_NAME% /d:sonar.gitlab.json_mode=SAST /d:sonar.analysis.mode=preview /d:sonar.host.url=http://176.9.137.51/ /d:sonar.gitlab.disable_global_comment=True
  • dotnet build /nr:false
  • dotnet sonarscanner end artifacts: expire_in: 1 day paths: [gl-sast-report.json] tags:
  • cmd` and artifact is uploaded succesfully, but i have no any reports in gitlab.Am I doing something wrong?

[gabrie-allaigre]

Hi, gl-sast-report is complex, the master must already be a gl-sast-report.json file

[iluwaa]

but i have another job: code_quality: stage: test only:

• /^feature\/*/ script:
• git checkout origin/dev
• git merge %CI_COMMIT_SHA% --no-commit --no-ff
• dotnet sonarscanner begin /k:%CI_PROJECT_NAME% /d:sonar.gitlab.project_id=%CI_PROJECT_PATH% /d:sonar.gitlab.commit_sha=%CI_COMMIT_SHA% /d:sonar.gitlab.ref_name=%CI_COMMIT_REF_NAME% /d:sonar.gitlab.json_mode=CODECLIMATE /d:sonar.analysis.mode=preview /d:sonar.host.url=http://176.9.137.51/
• dotnet build /nr:false
• dotnet sonarscanner end artifacts: expire_in: 1 days paths:
• codeclimate.json tags:
• cmd

and have result No changes to code quality