[FOLIO-1613] Update CI Maven+Sonarqube configuration Created: 12/Nov/18 Updated: 03/Jun/20 Resolved: 14/Nov/18 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P2 |
| Reporter: | John Malconian | Assignee: | John Malconian |
| Resolution: | Done | Votes: | 0 |
| Labels: | ci, sprint51 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: |
| Description |
|
The methods used in the Maven builds to integrate Sonarqube with Github have been largely deprecated and is possibly impacting Sonarqube Github feedback on PRs. Update Sonarqube integration for Maven builds. |
| Comments |
| Comment by John Malconian [ 12/Nov/18 ] |
|
Looks like Sonarqube stopped reporting feedback to Github approximately 15-19 days ago, |
| Comment by John Malconian [ 14/Nov/18 ] |
|
Updated the Sonarqube scanner Maven plugin version and configuration used with Maven build pipeline in FOLIO Jenkins. Sonarqube once again "decorates" Maven PRs in GitHub as it should. In addition, the updated scanner and Sonarcloud now supports scanning and publishing results for all branches including PRs. I've made modifications to the build pipeline to enable this by default. |