Update SonarCloud setup to the current conventions as of Feb 2025

[laurynas-biveinis]

Summary by CodeRabbit

• Chores
  • Updated our automated quality analysis pipeline to enhance stability and accuracy during code validation.
  • Refined dependency management and tool integration to support more efficient development processes.

[coderabbitai]

Walkthrough

The pull request updates the GitHub Actions workflow for SonarCloud analysis. The modifications include reformatting the permissions section, changing dependency installation from a specific Boost version to the development package, updating the Sonar scanner action to SonarSource/[email protected], altering the compilation database command to use a Release build type with the -DSTANDALONE=ON flag, and replacing the multi-line run command with a single-line with block for specifying scan arguments.

Changes

File(s)	Change Summary
.github/workflows/sonarcloud.yml	- Reformatted the permissions section - Updated dependency installation from boost1.74 to libboost-dev - Modified the compilation database command to use the Release build type with -DSTANDALONE=ON flag - Replaced the Sonar scanner action from sonarsource/sonarcloud-github-c-cpp@v2 to SonarSource/[email protected] and restructured scan command into a with block

Sequence Diagram(s)

sequenceDiagram
    participant GHA as GitHub Actions
    participant DI as Dependency Installer
    participant DB as Compilation Database Generator
    participant SS as Sonar Scanner Action

    GHA->>DI: Install libboost-dev
    GHA->>DB: Generate compilation database\n(Release, -DSTANDALONE=ON)
    GHA->>SS: Execute Sonar scan\n(with provided arguments)

Loading

Poem

Hippity-hop in YAML lands,
Code flows smooth through careful hands.
Dependencies and flags align,
Scans and builds begin to shine.
A bunny sings of changes bright,
In workflows that now feel just right!
🐇✨

Tip

🌐 Web search-backed reviews and chat

• We have enabled web search-based reviews and chat for all users. This feature allows CodeRabbit to access the latest documentation and information on the web.
• You can disable this feature by setting web_search: false in the knowledge_base settings.
• Please share any feedback in the Discord discussion.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[laurynas-biveinis]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b6241ba and a3e4dd7.

📒 Files selected for processing (1)

• .github/workflows/sonarcloud.yml (2 hunks)

🧰 Additional context used

🪛 GitHub Check: Codacy Static Code Analysis

.github/workflows/sonarcloud.yml

[warning] 32-32: .github/workflows/sonarcloud.yml#L32
An action sourced from a third-party repository on GitHub is not pinned to a full length commit SHA. Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release.

🔇 Additional comments (3)

.github/workflows/sonarcloud.yml (3)

10-10: Permissions Configuration Update

The empty permissions object (permissions: {}) is correctly formatted and appears to conform to the updated conventions. Please ensure that this setting provides the necessary minimal permissions for your workflow.

---

25-25: Dependency Installation Update

Updating the dependency installation command to install libboost-dev is appropriate given our move away from a specific Boost version. Confirm that this package meets all your project’s requirements.

---

29-29: Compilation Database Generation Command

The updated CMake command using -DCMAKE_BUILD_TYPE=Release -DSTANDALONE=ON aligns with current best practices for generating a Release build compilation database. This should improve the relevancy of the analysis.