Repository navigation
RC-352 Update ruling tests for the relocated sonar-server fixture - #6436
romainbrenguier wants to merge 1 commit into
Conversation
Ruling Diff SummaryDetected changes in 368 rule files: 52108 issues removed, 52108 issues added. NoSonar (
|
Code Review
|
| Auto-apply | Compact | Unblock |
|
|
|
Was this helpful? React with 👍 / 👎 | Gitar
|
| @@ -1 +1 @@ | |||
| Subproject commit 616f3f5a7dca9c5858fb35d5eeff64b28b6524c1 | |||
| Subproject commit d4109b185897249a62b854248ad449215f0b5676 | |||
There was a problem hiding this comment.
⚠️ Bug: Submodule pinned to unmerged ruling_java PR branch commit
its/sources now points to d4109b185897249a62b854248ad449215f0b5676. That is the head of the move-sonar-server branch of SonarSource/ruling_java#18, which is still open and is not in master's history (branches-where-head, PR #18). If #18 is squash- or rebase-merged and the branch is then deleted, this SHA can no longer be fetched from master, and git submodule update fails for every ruling CI run. Once #18 lands, re-point the submodule to the merge commit that ends up on ruling_java master, then merge this PR.
Was this helpful? React with 👍 / 👎
| // sonar-server (v.6.5) | ||
| String projectName = "sonar-server"; | ||
| MavenBuild build = test_project(projectName) |
There was a problem hiding this comment.
💡 Quality: AGENTS.md still lists sonarqube-6.5 as a ruling project
This PR renames the ruling project to sonar-server: the fixture moves, the expected baselines move to expected/sonar-server, and projectName in JavaRulingTest.sonarqube_server changes. AGENTS.md:299 still lists sonarqube-6.5 among the ruling projects. The same section says <projectKey> is the project's folder name under its/sources/ and that expected files live in expected/<project>/. Following it now leads to a directory and key prefix that no longer exist. That list is the documented ruling project names, so it should be updated to sonar-server.
Replace the stale project name in AGENTS.md.:
Ruling tests validate that rule fixes don't break existing true positives. They run the analyzer against real-world Java projects (`guava`, `commons-beanutils`, `eclipse-jetty`, `sonar-server`, `jboss-ejb3-tutorial`, `regex-examples`, `mall`) and compare results to expected baselines.
- Apply fix
Check the box to apply the fix or reply for a change | Was this helpful? React with 👍 / 👎





Summary
its/sourcessubmodule to the sonar-server fixture relocation in RC-352 Move sonar-server ruling project to the repository root ruling_java#18.sonar-serverfixture and use its new project key.expected/sonar-serverand update their project keys without changing expected issue locations.Dependency
Merge SonarSource/ruling_java#18 first.
Validation
git diff --cached --checkpasses.Part of RC-352