You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
STORY: Establish Java service quality gates and SonarQube strategy #1
Establish a repeatable quality-gate strategy for Java services that works locally, in CI, in the local SIT environment, and later with SonarQube Cloud when the organization repositories become public.
Scope
Standardize Maven verify as the developer and CI quality-gate command.
Add local formatting and test gates before deeper static analysis.
Provide a local SonarQube option for learning and quality dashboard practice.
Provide a local SIT SonarQube deployment option for integrated environment practice.
Define the later migration path to SonarQube Cloud for public repositories.
Acceptance criteria
Developers can run one command locally to execute the service quality gate.
GitHub Actions can run the same quality gate without custom per-service logic.
SonarQube local/SIT usage is documented as engineering tooling, not banking runtime infrastructure.
SonarQube Cloud integration is planned for the public repository phase.
The approach avoids paid dependencies during private development.
Activity
ramioooz commentedon Aug 2, 2026
Moved from Sprint 0 to Sprint 6 because SonarQube is observability and quality tooling, not a prerequisite for local SIT platform operation.