템플릿 안에 프로젝트 계층이 아닌 메시징 플랫폼(src/platforms/messaging,
19개 모듈)이 있다. 소유자 결정(2026-11-07)은 라이브러리를 별도 repo에서
관리하고 템플릿은 버전으로 받는 것이다. 라이브러리는 이력째
messaging-library로 옮겨 dev.cakit.messaging 1.0.0으로 Gitea Packages에
게시했다(태그 v1.0.0 = 8c6045e, release run 28).
- 받는 법: src/settings.gradle에 exclusiveContent 저장소(group dev.cakit와
그 아래는 Gitea에서만, 나머지는 Maven Central에서만). 카탈로그
messagingLibrary = "1.0.0"과 쓰는 모듈 여섯.
- 쓰는 leaf: adapter:outbound:messaging, adapter:outbound:messaging-kafka,
adapter:inbound:messaging(admin exclude 좌표를 새 group으로), 시험만
composition:outbox-relay와 app-bootstrap architectureTest. import와
auto-configuration 이름 문자열 dev.caskeleton.messaging →
dev.cakit.messaging, 시험 stand-in도 같은 FQCN으로.
- persistence-jpa migration 시험이 라이브러리 소스 폴더를 경로
(../../../platforms/…)로 읽던 것을, 카탈로그 버전의 jar를 전용 구성
messagingMigrations(non-transitive)로 받아 db/migration을 풀어 읽게
했다. classpath에 올리면 그 leaf 시험의 Flyway가 메시징 migration까지
볼 수 있어 버렸다.
- registry: 메시징 19행을 지우고 library_groups ["dev.cakit"]와 쓰는 세
행의 allowed_libraries. 분리 전 프로젝트 edge 검사가 지키던 약속이
앞 커밋의 라이브러리 edge 검사로 그대로 남는다.
- 계약 테스트: MessagingPublicSurfaceContractTest는 라이브러리로 옮겼고,
MessagingAuthorityContractTest는 이 repo의 app.messaging 주인 하나만
본다(라이브러리 쪽 하나는 그 repo가 본다).
- system caller 규칙(ApplicationBoundaryArchitectureTest)의 「프로젝트
타입」에 dev.cakit.을 더했다. 메시지 handler가 구현하는 MessageHandler가
라이브러리 타입이 되면서, 그대로 두면 manual 09의 handler가
SYSTEM_CALLERS_HAVE_ONLY_PROJECT_SUPERTYPES에 걸리고 MessageHandler로
주입받는 endpoint를 USER_TRANSPORTS_DO_NOT_REACH_SYSTEM_CALLERS가
따라가지 못한다(구조 리뷰가 찾음).
- 순서 시험: 이름 정렬로도 라이브러리 root가 먼저 오게 되어 bridge 시험이
afterName을 지키지 못했다. stand-in을 맨 뒤 순서로 두고, inbox 쪽
beforeName을 지키는 시험을 더했다.
- 지움: src/platforms(와 빈 폴더), messaging-certification.yml, 카탈로그의
avro·cloudevents·protobuf 4.33.2, SpotBugs 제외의 메시징 줄,
check-repo-layout.py의 platforms. 편집 훅이 계층 leaf의 dev.cakit import를
알린다.
- lockfile: 바뀐 줄은 dev.cakit.messaging 좌표 추가 45줄뿐이다(외부
의존성 집합은 그대로, 설계 16절 H6).
버린 대안: 라이브러리 jar를 persistence-jpa testRuntimeOnly로 올려
classpath에서 읽기(위 이유). 템플릿에 docs/messaging 사본을 남기기
(라이브러리 문서와 갈라진다. 다음 커밋이 문서를 그 repo로 가리킨다).
위험: 캐시가 빈 빌드(새 기계, 이미지 builder)는 git.learn.hyeonworks.com에
닿아야 한다. 공개 owner라 토큰은 필요 없다(익명 200 확인). 이 커밋만으로는
살아 있는 문서가 지운 경로를 부른다(check-docs는 다음 커밋에서 통과).
검증: desktop에서 이 트리로 RED·GREEN(system caller 고정 시험 2건, 순서
시험 2건은 수정 전·제약 제거 시 실패, 수정 후 통과). 전체 게이트는
PR 본문.
BREAKING CHANGE: src/platforms/messaging과 project(':messaging:…') 경로가
없어졌다. dev.cakit.messaging:<모듈>:1.0.0 좌표로 받고 import를
dev.caskeleton.messaging → dev.cakit.messaging으로 바꾼다
(docs/upgrade/2026-11-maturity-review.md B-57~B-59).
Refs: design-docs repo-structure/05-library-repos.md 4·8·10·13절
250 lines
14 KiB
YAML
250 lines
14 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.
|
|
# Since 2026-11-08 messagingCertificationTest and the messaging starter's integrationTest run in the
|
|
# messaging-library repository, not here; the measurement above predates that.
|
|
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
|
|
- 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
|
|
|
|
# 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
|