Skip to content

Add update-sonarqube job #2243

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
JunAr7112 wants to merge 1 commit into from
+20 −0
Closed

Add update-sonarqube job #2243

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .gitignore
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,7 @@ testbin/*
*~
*.DS_Store
.vscode
.scannerwork/
Comment thread
rajathagasthya marked this conversation as resolved.

# Credentials and runtime environment
kubeconfig
Expand Down
19 changes: 19 additions & 0 deletions .nvidia-ci.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -162,6 +162,25 @@ update-nspect:
NSPECT_CLIENT_ID: "${NSPECT_PROD_CLIENT_ID}"
NSPECT_CLIENT_SECRET: "${NSPECT_PROD_CLIENT_SECRET}"

update-sonarqube:
stage: ngc-publish
needs:
- job: update-nspect
optional: true
- job: update-nspect-staging
optional: true
image:
name: sonarsource/sonar-scanner-cli:11
entrypoint: [""]
variables:
SONAR_USER_HOME: "${CI_PROJECT_DIR}/.sonar"
GIT_DEPTH: "0"
rules:
- if: $CI_COMMIT_BRANCH == 'main'
allow_failure: true
script:
- sonar-scanner -Dsonar.host.url="${SONAR_HOST_URL}" -Dsonar.projectKey=gpu-operator -Dsonar.projectName=gpu-operator -Dsonar.sources=.
Copy link
Copy Markdown
Contributor

@cdesiniotis cdesiniotis Apr 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What does this do exactly? Is this performing a static analysis scan and uploading the results somewhere? What commit SHA is SonarQube scanning?

With prior static analysis tools, we were able to schedule regular scans without having to add jobs to our CI. Can we do that with SonarQube and avoid having to add CI changes to all of our repositories?

Copy link
Copy Markdown
Contributor Author

@JunAr7112 JunAr7112 Apr 6, 2026 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes this is performing the scan and updating the sonar gpu-operator dashboard with the results. Unfortunately, the SonarQube dashboard does not provide a way to schedule regular scans; we need to trigger with CI/CD. I can try to see if I can move the scan command into the pre-existing NSPECT job if that is preferred.


.publish-images:
stage: ngc-publish
extends:
Expand Down