Repository navigation
chore: remove SonarCloud integration - #2255
Merged
Merged
Conversation
Remove the SonarCloud workflow, Gradle plugin and project settings while preserving JaCoCo coverage, SpotBugs and Spotless. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: a2e376ca-1b60-48d9-a217-6740cb920e4d
There was a problem hiding this comment.
🔵 Needs a closer look
Deleting the SonarCloud workflow removes CI execution of the main JVM unit tests and JaCoCo coverage generation, which the surviving workflows do not replace.
No open issues 🎉
What changed in this PR
Removes SonarCloud integration from Kiota Java’s Gradle configuration and CI, while leaving the existing coverage and quality-tool configuration unchanged.
Changes:
- Deletes the SonarCloud analysis workflow.
- Removes the root and subproject SonarQube plugin configuration and version-catalog entry.
- Removes SonarCloud project settings and the skip-compile property.
| File | Description |
|---|---|
settings.gradle |
Removes the Sonar skip-compile property. |
gradle/libs.versions.toml |
Removes the SonarQube plugin entry. |
build.gradle |
Removes SonarQube plugin application and SonarCloud settings. |
.github/workflows/sonarcloud.yml |
Deletes the build-and-analysis workflow. |
Review effort: Balanced
Gavin Barron (gavinbarron)
approved these changes
Nov 16, 2026
Gavin Barron (gavinbarron)
left a comment
Contributor
There was a problem hiding this comment.
Reviewed the SonarCloud workflow, Gradle plugin, configuration, and version-catalog cleanup. The independent Gradle build/test workflow remains intact. No blocking findings.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Validation
gradlew.bat --no-daemon build spotlessCheckusing Java 21 (115 tasks executed); 449 tests across 37 suites, zero failures/errors/skips; coverage reports generated.gradlew.bat --no-daemon build -Pjava8=true -Porg.gradle.java.installations.paths=<portable-JDK8>(155 tasks: 40 executed, 115 up-to-date). Java 8 compatibility projects contain no test sources; tests were exercised by the main build above.git diff --checkpasses. No surviving workflow was edited.Limitations / existing issues
actionlint -shellcheck= -pyflakes=reports the existing undefinedinputs.componentNamein the unchanged build workflow (line 37); confirmed identical against the base version.