[FOLIO-3334] Add an option to the Jenkins Maven CI pipeline to disable Sonarqube scan Created: 03/Nov/21 Updated: 03/Nov/21 Resolved: 03/Nov/21 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | TBD |
| Reporter: | John Malconian | Assignee: | John Malconian |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: | DevOps Sprint 126 |
| Development Team: | FOLIO DevOps |
| Description |
|
Add a configurable option to Jenkinsfile for Maven CI build pipeline which will disable Sonarqube scan. Requested for vertx-pac4j but also useful when dealing with forks in general and other special circumstances. |
| Comments |
| Comment by John Malconian [ 03/Nov/21 ] |
|
This option currently exists for UI modules so might as well implement something similar for Maven-based repos. SQ scans can be disabled by specifying 'runSonarqube = false' in the Jenkinsfile. Defaults to 'true'. |