Fix Sonar analysis by using JDK 21 - #367
Conversation
|
Warning Review limit reached
Next review available in: 55 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
WalkthroughThe Sonar analysis workflow now explicitly installs Temurin JDK 21 through ChangesSonar Analysis Workflow
Estimated code review effort: 1 (Trivial) | ~2 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/gradlew-sonar-analysis.yml:
- Line 41: Update the actions/setup-java step in the workflow to reference a
reviewed 40-character commit SHA instead of the mutable `@v4` tag, and add an
inline comment identifying the corresponding action version for traceability.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 43a4afb0-b40a-4646-8b3b-d78873466a20
📒 Files selected for processing (1)
.github/workflows/gradlew-sonar-analysis.yml
Signed-off-by: amanbh321 <Aman.Bahuguna@iiitb.ac.in>
5479c3f to
418d66e
Compare
Root cause: gradlew-sonar-analysis.yml did not explicitly configure a JDK, so Sonar analysis ran with the GitHub runner's default Java 17. SonarCloud now requires Java 21+ for analysis.
Fix: Added an explicit actions/setup-java step to configure Temurin JDK 21 before running ./gradlew build sonarqube
Summary by CodeRabbit