SonarQube Server ↔ CI Scanner: Can a Scoped Project Token Replace User Credentials for Full Pipeline Analysis and Quality-Gate Checks?
We want to validate that a CI pipeline can authenticate to SonarQube and complete the full analysis cycle—including project creation or selection, branch/PR parameter handling, and quality-gate polling—using only a scoped project analysis token instead of a broad user token. The SonarQube documentation indicates project tokens are intended for least-privileg