Skip to content

TASK: Standardize Maven verify quality gate for Java services #2

Closed

Description

@ramioooz

Parent: STORY: Establish Java service quality gates and SonarQube strategy

Objective

Make Maven verify the standard local and CI quality-gate command for Java services.

Scope

  • Add Spotless formatting checks to the Maven lifecycle.
  • Ensure ./mvnw verify runs formatting checks and the test suite.
  • Add JaCoCo coverage report generation when the service has meaningful test coverage.
  • Update GitHub Actions to use ./mvnw verify instead of ad hoc commands.
  • Document the local developer workflow.

Acceptance criteria

  • ./mvnw spotless:apply can format code locally.
  • ./mvnw verify fails on formatting violations or failing tests.
  • CI runs the same command used by developers.
  • The first implementation is applied to customer-service, then standardized for future services.

Activity

  1. self-assigned this
    on Jun 24, 2026
  2. added
    quality-gateQuality gate, code quality, and static analysis work
    ciContinuous integration and workflow automation
    toolingShared developer tooling and engineering platform work
    on Jun 24, 2026
  3. added theissue type on Jun 29, 2026
  4. ramioooz commented on Aug 2, 2026

    @ramioooz
    MemberAuthor

    Reclassified to Sprint 6 - Operational Resilience and Observability. Maven quality gates are cross-service engineering-quality work, not a local Kubernetes SIT deliverable.

  5. ramioooz commented on Sep 4, 2026

    @ramioooz
    MemberAuthor

    CI adoption wave opened:\n- Auth Service: https://github.com/digital-bank-java/auth-service/pull/8\n- Notification Service: https://github.com/digital-bank-java/notification-service/pull/8\n- Payment Service: https://github.com/digital-bank-java/payment-service/pull/8\n\nThe three PRs are independent and may merge in parallel; no delay is required. Each replaces only the inline Maven verification job and preserves the repository's existing Helm validation and container smoke checks. No redundant tests were added because this is CI wiring only.

  6. ramioooz commented on Sep 5, 2026

    @ramioooz
    MemberAuthor

    Completion evidence: the cross-service Maven quality-gate rollout is merged across the Java services. The repositories use the standardized verify lifecycle with Spotless, tests, and JaCoCo where applicable; CI retains the existing Helm/container checks without redundant jobs. No SonarQube implementation is included because that work was explicitly deferred.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

ciContinuous integration and workflow automationquality-gateQuality gate, code quality, and static analysis worktoolingShared developer tooling and engineering platform work

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions