Skip to content

M3b: CI runs only what a change touches #7

Closed

Description

@MAOFILHO

What to build

A pull request that only touches one service runs only that service's unit tests and container build. A change to the shared package, CI itself, or the service table still runs everything. Contract tests still run for both sides of any contract a change touches (consumer order; providers payment, catalog, inventory).

This is the "build and test only what changed" half of pattern 3 (CI-CD).

Acceptance criteria

  • A change limited to one service skips the other services' test and image jobs.
  • A change to shared code, the service table or the workflow runs every job.
  • Changing the order service also runs the provider contract checks; changing a provider runs its own contract check.
  • Skipped jobs do not block merging (branch protection still passes).
  • Demonstrated with one real PR whose CI run shows the skipped legs.

Blocked by

None (can start immediately).

Activity

  1. MAOFILHO commented on Nov 16, 2026

    @MAOFILHO
    OwnerAuthor

    Demonstrated on PR #13 (CI-CD page, gateway + frontend only): CI run ran Unit tests (gateway), Container image (gateway) and Frontend (build); it skipped the other 6 services' tests and images, the contract checks and Bicep. "CI ok" passed, so the skipped jobs did not block the merge. The planner and its rules were built in #12.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    ready-for-agentFully specified, ready for an AFK agent

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions