Skip to content

TASK: Update Java service CI template for explicit test stages #8

Closed

Description

@ramioooz

Parent: STORY: Standardize Java unit and integration test phases

Objective

Make Java service CI stages explicit for unit tests, integration tests, container smoke tests, Helm validation, and future quality gates.

Scope

  • Define the desired CI stage order for Java services.
  • Decide whether the logic belongs in reusable workflows in .github or per-service workflows first.
  • Align commands with the Maven Surefire/Failsafe convention.
  • Preserve existing Docker and Helm validation behavior.

Acceptance Criteria

  • CI plan clearly separates test and verify.
  • Existing service CI behavior is preserved or intentionally migrated.
  • Future services can copy or reuse the convention.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions