문제: src/ 최상위에 계층 폴더와 들여온 제품 폴더(messaging, grpc,
grpc-advanced)와 optional 빌드 폴더(optional-platforms)가 같은 높이로
놓여, 무엇이 이 애플리케이션의 계층인지 폴더만으로 안 보인다.
src/config/에는 빌드 전체 설정과 기능 하나가 주인인 데이터(jpa,
messaging, mongodb)가 섞여 있다.
고른 방법(소유자 결정 2026-11-07, 설계 가-1):
- git mv로 src/platforms/{messaging,grpc,grpc-advanced,optional-build}.
registry source_path 28행만 바꾸고 Gradle 경로(:messaging:*, :grpc:*)는
그대로다. optional 빌드의 이름(optional-platforms)도 그대로다.
- optional 빌드가 한 단계 깊어져, build-logic이 "optional 빌드의 부모 =
주 빌드"로 가정한 네 곳(registry settings, ArchitecturePlugin, 테스트
이미지 catalog, checkstyle·spotbugs 설정)을 MainBuild(위로 올라가며
registry·설정 파일을 찾음)로 바꾼다.
- settings.gradle·build.gradle의 상대 경로, workflow의 -p 값과 경로,
buf 작업 폴더를 고친다. buf breaking은 이동 전 baseline에서도 옛
경로로 비교해 이동 PR에서 건너뛰지 않는다.
- config/jpa, config/messaging, config/mongodb의 데이터를 주인 leaf의
release/로 옮기고 읽는 빌드 줄·테스트·스크립트·문서를 고친다.
- 루트 CLAUDE.md 5절에 최상위 폴더 지도를 한 줄로 적는다.
버린 대안: Gradle 루트를 저장소 루트로(가-3, CI 재편 때 다시 봄),
application-* 묶기(가-2, 파생 서비스 충돌이 큼).
위험·한계: Gradle 문서의 "이름 = 위치" 권고와 한 단계 어긋난다
(:messaging:x가 platforms/messaging/x). 옮긴 폴더를 고쳐 쓰던 파생
서비스는 이름 바뀜 충돌이 날 수 있다(B-52). docs/capability-status.md
「제거된 코드」 표와 docs/work/evidence.md의 옛 경로는 이력이라 두었다.
검증(desktop, 트리 2b3354a4, ~/t1-layout-logs/):
- ./gradlew :ci :verifyDependencyLocks --warning-mode=fail --continue
첫 실행 rc=1: MessagingAuthorityContractTest가 src/messaging을 찾아 실패
→ 경로를 고침. 두 번째 rc=1: messaging-policy
MessagingAdmissionControllerTest.aWaitingCallerIsAdmittedOnceAPermitIsReturned
(2초 대기 경쟁, 부하 7.3에서 한 번 실패, 코드 변경 없는 leaf) → --rerun
3회 모두 통과. 세 번째 rc=0
- -p platforms/optional-build ci rc=0, 두 빌드의 verifyStrictLaneStages
--dry-run rc=0, -p build-logic check rc=0
- :app-bootstrap:documentContractTest
:adapter:outbound:persistence-mongo:mongoDocumentContractTest rc=0
- ./gradlew projects(주 빌드)와 optional 빌드 projects의 프로젝트 목록이
이동 전 트리와 같다(Gradle 경로 불변)
- check-work-docs.py, 상대 링크 검사 rc=0
Refs: design-docs repo-structure/README.md 3.1, repo-structure/01-backend-layout.md 6.1
BREAKING CHANGE: src/messaging·src/grpc·src/grpc-advanced·src/optional-platforms가 src/platforms/ 아래로, src/config/{jpa,messaging,mongodb}가 주인 leaf의 release/로 옮겨졌다. optional 빌드는 -p platforms/optional-build로 부른다. docs/upgrade/2026-11-maturity-review.md B-52.
283 lines
16 KiB
YAML
283 lines
16 KiB
YAML
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. The container-backed lanes, run as the root category aggregates `:integrationCheck` and
|
|
# `:performanceCheck` rather than one workflow line per lane. A lane nobody runs is not coverage;
|
|
# it is a file that looks like coverage — and naming lanes here one by one is how fourteen of
|
|
# them came to run nowhere (review 2026-11-01 08-01). The pull-request gate's
|
|
# `verifyStrictLaneStages` now fails when a strict lane is in no stage a workflow executes. They
|
|
# are here rather than in stage 1 because every one of them starts containers or real servers,
|
|
# 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
|
|
# `:<leaf>:test` already runs, and `:<leaf>: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 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
|
|
# `--continue`: one failed lane (an external image that cannot be pulled, say) must not stop
|
|
# the other main-stage gates from reporting (review 2026-11-01 08-04).
|
|
run: ./gradlew :mainCheck --continue --warning-mode=fail --stacktrace
|
|
|
|
# Storability only: the `--dry-run` below plans `integrationCheck` without running a lane. The
|
|
# lanes run in `integration-check`.
|
|
#
|
|
# 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
|
|
}
|
|
|
|
# The integration stage: every integration-category strict lane (`:integrationCheck`).
|
|
#
|
|
# This job replaced six jobs that named lanes one by one — the MongoDB lanes, app-bootstrap's
|
|
# Testcontainers lane, the moved messaging/object-storage/sample contracts, six of the
|
|
# persistence-jpa PostgreSQL contracts and the httpclient fault injection. Naming lanes was how
|
|
# eleven persistence-jpa readiness lanes ended up running nowhere: a lane added to Gradle without a
|
|
# workflow line was declared, failed closed, and executed on no machine (review 2026-11-01 08-01).
|
|
# The aggregate is the list now. A lane joins it by declaring `integration()`, and the root
|
|
# `verifyStrictLaneStages` (pull-request gate) fails when a strict lane is in no stage a workflow
|
|
# executes.
|
|
#
|
|
# `--continue` so that one red lane does not hide the others: every failed lane is named in the
|
|
# same run. Lanes that need an input this job does not have (the Redis topology coordinates, the
|
|
# protected AWS sandbox) are `explicitOnly`; the aggregate prints which ones it left out.
|
|
# The container lanes take the build-wide `exclusiveRealServerLane` slot one at a time, so the
|
|
# job's length is the sum of the lanes. Split the aggregate across jobs when it outgrows its
|
|
# timeout rather than going back to naming lanes.
|
|
#
|
|
# Measured length (one local run of `:integrationCheck`, 2026-11-01, 37 lanes, images already
|
|
# pulled, machine load 24): 794 s for the command, of which the lanes' test JVMs took about 624 s
|
|
# in sum — mongoSecurityIntegrationTest 89, jpaPlatformContractTest 104, messagingCertificationTest
|
|
# 70, mongoCompatibilityTest 69, jpaPlatformMigrationTest 66, mongoFailoverTest 59, the eleven JPA
|
|
# readiness lanes 57 together, httpClientFailureInjectionTest 27, sample integrationTest 23,
|
|
# messaging starter integrationTest 21, the rest under 10 each — and the remainder was compilation
|
|
# and container start-up between lanes. A hosted runner adds cold image pulls (about 5 GB
|
|
# uncompressed across the PostgreSQL, MongoDB, Kafka, nginx, httpbin and Toxiproxy images) and a
|
|
# cold Gradle cache; expect 25 to 40 minutes (an estimate, not a measured hosted run). The 240-minute timeout is a ceiling for a hung container, not a budget.
|
|
integration-check:
|
|
runs-on: ubuntu-latest
|
|
timeout-minutes: 240
|
|
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: Run every integration-category strict lane
|
|
working-directory: src
|
|
run: ./gradlew :integrationCheck --continue --stacktrace
|
|
- name: Publish the integration lane reports
|
|
if: always()
|
|
uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # actions/upload-artifact@v4.6.2
|
|
with:
|
|
name: integration-check-reports
|
|
path: src/**/build/reports/tests/
|
|
if-no-files-found: warn
|
|
|
|
# The performance stage: every performance-category strict lane (`:performanceCheck`) — Tomcat and
|
|
# Jetty load, slow-client and graceful shutdown, the Hikari pool contract, the httpclient pool,
|
|
# streaming, retry and rotation bounds, the MongoDB resource budget. They measure behaviour that
|
|
# degrades gradually rather than breaking outright, which is the kind of regression a per-PR gate
|
|
# never catches. This job replaced `web-load-abuse-and-shutdown`, which despite its name ran
|
|
# `:adapter:inbound:web:test` and `webJettyCompatTest` — two lanes the pull-request and main stages
|
|
# already run — and never the load lanes (review 2026-11-01 08-01), and `httpclient-performance`.
|
|
# No assertions switch: the strict-lane convention asserts every performance lane's bounds, so this
|
|
# job and a person on a workstation run the same command and get the same bounds.
|
|
performance-check:
|
|
runs-on: ubuntu-latest
|
|
timeout-minutes: 120
|
|
env:
|
|
TESTCONTAINERS_REUSE_ENABLE: "false"
|
|
steps:
|
|
- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2
|
|
- uses: ./.github/actions/setup-gradle-java
|
|
- name: Run every performance-category strict lane
|
|
working-directory: src
|
|
run: ./gradlew :performanceCheck --continue --stacktrace
|
|
# The optional gRPC build's performance lanes (grpcPerformanceTest). A separate build, so a
|
|
# separate command; its own verifyStrictLaneStages counts this line (review 2026-11-03 RR-06-03).
|
|
- name: Run every optional-platform performance-category strict lane
|
|
if: always()
|
|
working-directory: src
|
|
run: ./gradlew -p platforms/optional-build performanceCheck --continue --stacktrace
|
|
- name: Publish the performance lane reports
|
|
if: always()
|
|
uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # actions/upload-artifact@v4.6.2
|
|
with:
|
|
name: performance-check-reports
|
|
path: src/**/build/reports/tests/
|
|
if-no-files-found: warn
|
|
|
|
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 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 platforms/optional-build 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 platforms/optional-build 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/platforms/grpc*/**/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/app-bootstrap/compose-lanes/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
|