[MSMRC-2463] SonarQube enablement #110
Open
+91
−0
Conversation
This file contains 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.
High level summary
MSMRC-2463 SonarQube enablement
This PR introduces configuration template files for setting up SonarQube in your projects.
Additional information
The following templates are included:
sonar-project.properties: Contains project-specific SonarQube settings like source paths, exclusions, and coverage reports.
sonar.yaml: GitHub Actions workflow to automate SonarQube scans, upload coverage reports, and perform quality gate checks on pull requests.
Why This Is Needed
SonarQube has been enabled by security for this project to ensure consistent and automated static code analysis. It helps identify bugs, vulnerabilities, and code smells early in the development process.
This setup will:
Improve code quality across projects.
Highlight potential security risks and technical debt.
Automate the process of scanning code and monitoring quality gates, ensuring all code changes meet required standards.
Adjustments need to be made to files to fit you project requirements.