name: integration-main # Stage 2: is the merged state healthy. # # The question this stage answers is different from stage 1's. Stage 1 asks whether a diff is safe # and blocks a merge; stage 2 asks whether main is healthy and does not — the merge has already # happened. That difference is the point, and it is what lets a control exist without being an # obstacle: a gate here still fails loudly, it just fails after the thing it is reporting on. # # Two kinds of work live here. # # 1. The lanes that need a machine that is not simultaneously compiling something else — load, # abuse, graceful shutdown, TCP fault injection, resource bounds. They were web-nightly.yml and # httpclient-nightly.yml, two module-shaped files whose only real difference was the cadence they # shared. They now run on every push to main as well as nightly, which is strictly more often # than before. # # 2. Lanes that were registered in Gradle and invoked by nothing — the MongoDB container lanes and # app-bootstrap's Testcontainers `integrationTest` — existed, failed closed, and executed in no # workflow. A lane nobody runs is not coverage; it is a file that looks like coverage. They # are here rather than in stage 1 because every one of them either starts containers or re-runs # suites the PR gate already covers, and the pull-request budget is minutes for the whole gate. # # What is deliberately NOT here: the web "Advanced capability" nightly lane that used to exist as # web-advanced-nightly.yml (websocket-advanced-nightly.yml went with the websocket Advanced code, # deleted 2026-09-25). The web leaf's build file says it outright — "They also run inside `test`, # deliberately ... excluding them from the PR gate to make this lane look meaningful would mean the # PR gate stopped covering a fifth of the leaf" — so `webAdvancedTest` selects tagged tests that # `::test` already runs, and `::test` runs inside the root `check` on every pull request # and every push to main. The strict lane itself survives in release.yml, where its # fail-on-nothing-discovered guard is worth a job. on: push: branches: ["main"] schedule: # 03:00 UTC. Late enough that the day's merges are in, early enough that a failure is triaged # before the next working day starts. - cron: '0 3 * * *' workflow_dispatch: permissions: contents: read concurrency: group: ${{ github.workflow }}-${{ github.ref }} cancel-in-progress: false # The documentation-drift gates that used to run here are gone rather than demoted. # # They were four hand-written parsers: README shell blocks compared against the Gradle task graph, # runbook identifiers compared against every declared Java type, a leaf count written in prose # compared against the registry, and a Markdown table compared against the declared source sets. # Each was a custom parser for a file format nobody controls, and each made a documentation edit a # precondition for a build. A stale sentence is a defect, but it is not one a build can be failed # for, and link-check.yml already answers the one documentation question with a stable machine # answer: does this link resolve. jobs: # The main-branch stage of the Gradle gates (`:mainCheck`): the environment contract, full-boot # qualification, the sample web contract, the public-path baseline, the conditional transport # lanes, the messaging contract lanes and each leaf's document-contract lanes. API surfaces are # in the pull-request `check` (owner decision 20). The rest left the pull-request gate (review # 2026-09-24 BUILD, item 12); none of them is deleted. main-check: runs-on: ubuntu-latest timeout-minutes: 60 steps: - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2 - name: Require the committed public-path security baseline run: | set -euo pipefail readonly snapshot='docs/security/public-paths-snapshot.txt' if [[ ! -s "${snapshot}" ]] || ! git ls-files --error-unmatch "${snapshot}" >/dev/null 2>&1; then echo "::error::${snapshot} is missing, empty or not committed; verifyPublicPathSnapshot must not create its own baseline." exit 1 fi - uses: ./.github/actions/setup-gradle-java - name: Run the main-branch stage working-directory: src run: ./gradlew :mainCheck --warning-mode=fail --stacktrace # Two questions. Can every task in the repository-wide gates be *stored* (a property of the task # graph, so `--dry-run` answers it for all of them in seconds)? And is a stored entry *reused* while # the build still executes its work (checked on the two core leaves)? configuration-cache: runs-on: ubuntu-latest steps: - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2 - uses: ./.github/actions/setup-gradle-java - name: Require every repository-wide gate to be storable working-directory: src shell: bash run: | set -euo pipefail for gate in ci mainCheck integrationCheck releaseCheck; do echo "::group::${gate}" ./gradlew "${gate}" --dry-run \ --configuration-cache --configuration-cache-problems=fail --stacktrace output="$({ ./gradlew "${gate}" --dry-run \ --configuration-cache --configuration-cache-problems=fail --stacktrace; } 2>&1)" printf '%s\n' "${output}" echo '::endgroup::' grep -Fq 'Reusing configuration cache.' <<<"${output}" || { echo "::error::Gradle did not reuse the configuration cache for ${gate}." exit 1 } done - name: Store configuration cache for the everyday core build working-directory: src run: >- ./gradlew :domain-core:check :application-core:check --configuration-cache --configuration-cache-problems=fail --stacktrace - name: Require configuration-cache reuse working-directory: src shell: bash run: | set -euo pipefail output="$({ ./gradlew :domain-core:check :application-core:check \ --configuration-cache --configuration-cache-problems=fail --stacktrace; } 2>&1)" printf '%s\n' "${output}" grep -Fq 'Reusing configuration cache.' <<<"${output}" || { echo '::error::Gradle did not reuse the configuration cache on the second identical build.' exit 1 } # Load, abuse and graceful shutdown measure behaviour that degrades gradually rather than breaking # outright — which is exactly the kind of regression a per-PR gate never catches. web-load-abuse-and-shutdown: runs-on: ubuntu-latest timeout-minutes: 60 steps: - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2 - uses: ./.github/actions/setup-gradle-java - name: Run the load, abuse and shutdown lanes on every container working-directory: src run: >- ./gradlew :adapter:inbound:web:test :adapter:inbound:web:webJettyCompatTest --stacktrace - name: Publish the test reports if: always() uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # actions/upload-artifact@v4.6.2 with: name: web-integration-reports path: src/adapter/inbound/web/build/reports/tests/ if-no-files-found: warn # Needs a container runtime and real time (design §29). Separated from the per-PR gate rather than # made optional inside it: a lane that cannot run here fails, it does not skip. httpclient-fault-injection: runs-on: ubuntu-latest timeout-minutes: 45 steps: - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2 - uses: ./.github/actions/setup-gradle-java - name: Inject TCP faults against a real upstream working-directory: src run: >- ./gradlew :adapter:outbound:httpclient:httpClientFailureInjectionTest --stacktrace httpclient-performance: runs-on: ubuntu-latest timeout-minutes: 45 env: # A project property rather than a command-line flag, so the run command stays a plain, # verifiable task invocation while the machine-dependent bounds are still asserted. GRADLE_OPTS: -Dorg.gradle.project.performance.assertions.enabled=true steps: - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2 - uses: ./.github/actions/setup-gradle-java - name: Certify pool, streaming, retry, and rotation bounds working-directory: src run: >- ./gradlew :adapter:outbound:httpclient:httpClientPerformanceTest --stacktrace httpclient-http3-experimental: runs-on: ubuntu-latest timeout-minutes: 30 # Experimental by design (D-08): the result is reported, never used to block a merge. Registered # advisory so that "this job cannot fail the # build" is written down rather than inferred from a field two hundred lines into a workflow. continue-on-error: true steps: - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2 - uses: ./.github/actions/setup-gradle-java - name: Exercise the experimental HTTP/3 opt-in working-directory: src run: >- ./gradlew :adapter:outbound:httpclient:test -Phttp3.tests.enabled=true --stacktrace # The six Docker-backed MongoDB lanes. Until now they ran in no workflow at all: the leaf excludes # every one of their tags from `test` (build.gradle "Docker-backed lanes are excluded from the # default unit run"), `check` gains only the hermetic `mongoStableContractTest`, and the only thing # that named them was scripts/verify-mongodb-platform.sh, which nothing in .github invokes. Six # lanes that fail closed without Docker, and no machine with Docker was ever asked to run them. # # Stage 2 rather than stage 1 because each lane starts real MongoDB containers — mongo:8.0.16, # mongo:7.0.28 and a Toxiproxy in front of a three-node replica set. That is minutes per lane, and # the pull-request budget is minutes for the whole gate. # # One single-line `./gradlew ` step per lane, not one folded command running six, because # These command lines name each lane explicitly so that a lane which stops being invoked is # actually executed — a folded command would leave six matrix rows unverifiable. It also means a # red replica-set lane does not hide the compatibility lane behind it. mongo-container-lanes: runs-on: ubuntu-latest timeout-minutes: 90 env: # Reuse would hand the failover lane a replica set another lane had already faulted. TESTCONTAINERS_REUSE_ENABLE: "false" steps: - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2 - uses: ./.github/actions/setup-gradle-java - name: Single-node replica set contract lane working-directory: src run: ./gradlew :adapter:outbound:persistence-mongo:mongoReplicaSetTest --stacktrace - name: Run MongoDB integration lanes working-directory: src run: >- ./gradlew :adapter:outbound:persistence-mongo:mongoReplicaSetTest :adapter:outbound:persistence-mongo:mongoFailoverTest :adapter:outbound:persistence-mongo:mongoMigrationTest :adapter:outbound:persistence-mongo:mongoCompatibilityTest :adapter:outbound:persistence-mongo:mongoSecurityIntegrationTest :adapter:outbound:persistence-mongo:mongoPerformanceTest --stacktrace - name: Publish the MongoDB lane reports if: always() uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # actions/upload-artifact@v4.6.2 with: name: mongo-lane-reports path: src/adapter/outbound/persistence-mongo/build/reports/tests/ if-no-files-found: warn # app-bootstrap's Testcontainers lane. The leaf gave it a source set of its own precisely so that # `./gradlew :app-bootstrap:test` would not require a Docker daemon — and the consequence nobody # closed is that a source set outside `test` is also outside `check`, so the real-PostgreSQL # outbox and idempotency contracts compiled on every build and executed on none. bootstrap-integration: runs-on: ubuntu-latest timeout-minutes: 45 env: TESTCONTAINERS_REUSE_ENABLE: "false" steps: - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2 - uses: ./.github/actions/setup-gradle-java - name: Run the real-PostgreSQL integration contracts working-directory: src run: ./gradlew :app-bootstrap:integrationTest --stacktrace # Container contracts moved out of the default `test` source sets must remain executed after the # ownership split. One step per lane keeps a failure attributable to the capability that broke. moved-container-contracts: runs-on: ubuntu-latest timeout-minutes: 90 env: TESTCONTAINERS_REUSE_ENABLE: "false" steps: - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2 - uses: ./.github/actions/setup-gradle-java - name: Messaging outbox, inbox and admin-journal PostgreSQL contracts working-directory: src run: ./gradlew :messaging:messaging-reliability-jdbc-postgresql:integrationTest --stacktrace - name: Messaging starter Kafka round trip working-directory: src run: ./gradlew :messaging:messaging-spring-boot-starter:integrationTest --stacktrace - name: Object storage MinIO contract working-directory: src run: ./gradlew :adapter:outbound:objectstorage:integrationTest --stacktrace - name: Standalone sample PostgreSQL contract working-directory: src run: ./gradlew :sample-portfolio:integrationTestLaneCheck --stacktrace # These six PostgreSQL contracts moved from app-bootstrap into persistence-jpa. They are named # directly instead of relying on readiness-card membership: provider ownership and evidence # grading are different questions, and CI execution must not disappear when a card changes. jpa-provider-ownership-contracts: runs-on: ubuntu-latest timeout-minutes: 90 env: TESTCONTAINERS_REUSE_ENABLE: "false" steps: - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2 - uses: ./.github/actions/setup-gradle-java - name: Distributed lock contract working-directory: src run: ./gradlew :adapter:outbound:persistence-jpa:postgresqlDistributedLockIntegrationTest --stacktrace - name: Integer lock migration compatibility working-directory: src run: ./gradlew :adapter:outbound:persistence-jpa:postgresqlIntLockMigrationCompatibilityIntegrationTest --stacktrace - name: Outbox transactional append working-directory: src run: ./gradlew :adapter:outbound:persistence-jpa:postgresqlOutboxAppendTransactionalIntegrationTest --stacktrace - name: Outbox concurrent relay working-directory: src run: ./gradlew :adapter:outbound:persistence-jpa:postgresqlOutboxConcurrentRelayIntegrationTest --stacktrace - name: Outbox row lifecycle working-directory: src run: ./gradlew :adapter:outbound:persistence-jpa:postgresqlOutboxRowLifecycleIntegrationTest --stacktrace # The optional gRPC platform build declares one strict INTEGRATION lane — # `grpc-operation-ledger-jpa:integrationTest`, which certifies the atomic # `INSERT ... ON CONFLICT DO NOTHING` claim that durable mutation idempotency rests on against a # real PostgreSQL. It was registered in Gradle, listed in `strictTestLanes`, and invoked by # nothing: `-p optional-platforms ci` reaches `checkAll`, `qualityCheck` and the dependency # verifier, none of which runs a lane whose category is INTEGRATION, and release.yml's gRPC gate # names only the three grpc-testkit lanes. # # Stage 2 rather than stage 1 for the same reason as every other job in this file: the lane starts # a Testcontainers PostgreSQL, and the pull-request budget is minutes for the whole gate. grpc-optional-platform-integration: runs-on: ubuntu-latest timeout-minutes: 45 env: TESTCONTAINERS_REUSE_ENABLE: "false" steps: - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2 - uses: ./.github/actions/setup-gradle-java - name: Certify the gRPC operation ledger against real PostgreSQL working-directory: src run: ./gradlew -p optional-platforms integrationCheck --stacktrace - name: Publish the optional-platform lane reports if: always() uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # actions/upload-artifact@v4.6.2 with: name: grpc-optional-platform-integration-reports path: src/optional-platforms/**/build/reports/tests/ if-no-files-found: warn # Dynamic half of the compose-profile contract. Every blocking lane the matrix declares runs on # main and nightly; a partial lane run is reproduction only and cannot satisfy this job. The count # is not written here on purpose — a number in prose drifts the moment a lane is added, and the # matrix file is the thing this job reads. # # The lanes boot the qualification image (src/Dockerfile COMPOSITION=qualification: every # capability module present). The script selects it; release.yml builds the default image. compose-runtime-smoke: runs-on: ubuntu-latest timeout-minutes: 180 steps: - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2 - name: Run every blocking Compose runtime lane run: bash scripts/run-compose-runtime-smoke.sh --matrix src/config/runtime/compose-profile-contracts.json - name: Publish sanitized runtime-smoke evidence if: always() uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # actions/upload-artifact@v4.6.2 with: name: compose-runtime-smoke-evidence path: src/app-bootstrap/build/evidence/runtime-smoke if-no-files-found: warn