[MGNLTEST-213] Enable SonarQube to use (on some) "core" projects Created: 05/Apr/22 Updated: 05/Jun/23 Resolved: 16/May/23 |
|
| Status: | Closed |
| Project: | Magnolia Test Framework |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Neutral |
| Reporter: | Christoph Meier | Assignee: | Maxime Michel |
| Resolution: | Done | Votes: | 0 |
| Labels: | foundation_team | ||
| Σ Remaining Estimate: | Not Specified | Remaining Estimate: | Not Specified |
| Σ Time Spent: | 0.5d | Time Spent: | 0.5d |
| Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
| Issue Links: |
|
||||||||||||||||||||||||||||||
| Sub-Tasks: |
|
||||||||||||||||||||||||||||||
| Template: |
|
||||||||||||||||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||||||||||||||||
| Task DoD: |
[X]*
Doc/release notes changes? Comment present?
[X]*
Downstream builds green?
[X]*
Solution information and context easily available?
[X]*
Tests
[X]*
FixVersion filled and not yet released
[X] 
Architecture Decision Record (ADR)
|
||||||||||||||||||||||||||||||
| Team: | |||||||||||||||||||||||||||||||
| Approved: |
Yes
|
||||||||||||||||||||||||||||||
| Description |
|
SonarQube is an industry standard product to track the metrics of code quality. Services is using SonarQube for the PaaS project. In a recent meeting of the "Group of interest for testing&QA" Rabbie pointed out, that ConstraintsInitially set it up in a way, that breaking a rule does not block (a commit) - but still provide the analysis. Code analysis (likely) should run on jenkins, likely with jenkins-sonar-plugin, see https://docs.sonarqube.org/latest/analysis/scan/sonarscanner-for-jenkins/ . |