[FOLIO-3100] maven projects with subprojects report 0% coverage in Sonarcloud Created: 31/Mar/21 Updated: 03/Aug/21 |
|
| Status: | Open |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Bug | Priority: | TBD |
| Reporter: | John Malconian | Assignee: | John Malconian |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: | DevOps Sprint 114, DevOps Sprint 115, DevOps Sprint 113 |
| Development Team: | FOLIO DevOps |
| Description |
|
The Sonarqube scanner invoked during the Jenkins build pipeline can not find coverage reports generated by unit tests when repositories contain Maven sub-projects and, therefore, does not import coverage reports into Sonarcloud. This results in 0% code coverage as reported by Sonarcloud. This impacts mod-source-record-storage but could impact other repositories with multiple Maven subprojects. |