Skip to content

Disable SonarQube scan until SonarCloud is configured - #79

Merged
fey merged 1 commit into
mainfrom
ci-disable-sonar-until-configured
Aug 3, 2026
Merged

Disable SonarQube scan until SonarCloud is configured#79
fey merged 1 commit into
mainfrom
ci-disable-sonar-until-configured

Conversation

@fey

@fey fey commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Why

Node CI has never been green in this repo — every run (including pushes to main) fails on the SonarQube Scan step with:

Project not found. Please check the 'sonar.projectKey' and 'sonar.organization' properties, the 'SONAR_TOKEN' environment variable...

make install, make lint and make test-coverage all pass; only the scan is broken — the hexlet-boilerplates_nodejs-package project does not exist in SonarCloud (or the token has no access). This keeps every dependabot PR permanently red (#77, #78).

What

Comment the scan step out the same way php-package does, with a note on what is required to re-enable it. sonar-project.properties is left in place — it is correct and will be used once the SonarCloud side exists.

🤖 Generated with Claude Code

Node CI has never passed in this repo: install, lint and
test-coverage succeed, but the SonarQube step fails with
"Project not found" for hexlet-boilerplates_nodejs-package —
the SonarCloud project does not exist (or SONAR_TOKEN has no
access to it). Comment the step out the same way php-package
does until the SonarCloud side is set up.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@fey
fey merged commit 11ad564 into main Aug 3, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant