Skip to content

Add SonarQube analysis to CI - #8

Merged
trly merged 1 commit into
mainfrom
sonarqube-analysis-e4130c36-a1ca-4c80-b9be-4ebebc4b7547
Aug 7, 2026
Merged

Add SonarQube analysis to CI#8
trly merged 1 commit into
mainfrom
sonarqube-analysis-e4130c36-a1ca-4c80-b9be-4ebebc4b7547

Conversation

@trly

@trly trly commented Aug 7, 2026

Copy link
Copy Markdown
Collaborator

Adds SonarQube static analysis to this project, matching the setup already in place in deprecated-java-api-demo-1.

Gradle projects get the org.sonarqube plugin plus a sonar configuration block with the project key and name, and their existing build workflow now runs the sonar task with a full clone and a scanner cache. Maven projects get the sonar-maven-plugin and Sonar project properties in pom.xml, plus a dedicated analysis workflow running on JDK 17.

Analysis runs as its own step marked continue-on-error, so an unsuccessful or unconfigured scan reports on the run without failing the workflow. The SonarQube server URL and token are read from the SONAR_HOST_URL and SONAR_TOKEN repository secrets, which must be configured before analysis will actually report results.

Created by Sourcegraph agentic batch change.

@trly
trly marked this pull request as ready for review August 7, 2026 17:22
@trly
trly merged commit 7090639 into main Aug 7, 2026
1 check 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