Files
clean-architecture-backend-…/.github/workflows/notification-platform.yml
T
DongHyeonka de070e16a7 ci: 다른 단계가 이미 돌리는 workflow job을 지운다
workflow 15개 가운데 모듈 모양 파일들이 PR·main·nightly 단계가 이미
계획하는 Gradle 태스크를 한 번 더 돌린다(설계 design-docs
repo-structure/03-ci.md 3.1절 「중복」).

- fileserver-pr.yml 다섯 job: 모두 leaf `test`나 그 부분집합이다.
  `ci`가 매 PR 돌린다.
- fileserver-nightly.yml의 --rerun-tasks job 셋: 같은 `test`의
  부분집합이다. NFS job만 남긴다.
- jpa-nightly.yml의 failure·query plan·security·pool job: 모두
  integration()·performance() lane이라 :integrationCheck·
  :performanceCheck가 돈다. PostgreSQL major 행렬만 남긴다.
- notification-platform.yml의 pr job: `ci`와 :integrationCheck의
  태스크다. 경로 필터가 docs/adr/로 옮긴 알림 ADR을 보지 못했다.
  chaos job만 남긴다.
- object-storage-qualification.yml의 MinIO job 둘: integration lane이다.
  보호된 AWS job만 남긴다.
- link-check.yml: 문서 검사라 main 단계로(소유자 결정 2026-09-16).
  integration-main.yml의 links job으로 옮긴다.

fileserver 지원 매트릭스는 지운 job id 대신 그 증거를 실제로 만드는
테스트 클래스·모듈 test·남은 job을 적고, FileserverDocumentation
CoverageTest가 행마다 그 이름이 있는지 본다. job이 사라진 시험 문장
(PoolLaneClaimTest의 nightly job 검사, lychee 경로 필터 검사)은
지우거나 새 위치로 맞춘다.

위험: PR에서 경로로 켜지던 컨테이너 lane(notification의 실 PostgreSQL
두 lane, MinIO)은 이제 main push와 nightly에서만 돈다. 어댑터 컨테이너
lane을 main 단계로 옮긴 소유자 결정(2026-11-07 ②)과 같은 쪽이다.

검증: 기준 2959eff0의 desktop worktree에서 workflow의 Gradle 명령 50개를
--dry-run해 태스크 집합을 만들었다. 지운·옮긴 job 27개의 태스크는 모두
:ci·:mainCheck·:integrationCheck·:performanceCheck·:releaseCheck 계획
안에 있다(단계 집계 밖 0). 로그 desktop ~/t2a-backend-ci-logs/wave1-base/.
python3 scripts/check-docs.py, check-work-docs.py 통과.

Refs: design-docs repo-structure/03-ci.md 7.3절 Wave 1
2026-11-08 17:00:49 +09:00

78 lines
4.0 KiB
YAML

name: notification-platform
# The notification platform's chaos tier: the fault, race and restart suites run again on their own,
# nightly, because they are the ones a single green run says least about.
#
# The pull-request tier that used to be here is gone. Its seven steps ran `:application-core:test`,
# the notification leaves' `test` and `check`, and `jpaPlatformContractTest`/`jpaPlatformMigrationTest`
# — tasks the pull-request `ci` and `:integrationCheck` already run — and its path filter could not
# see the notification ADRs once they moved to docs/adr/. NotificationReleaseGateTest holds those in
# the notification leaf's `test`, which `ci` runs on every pull request.
on:
schedule:
- cron: '0 17 * * *'
workflow_dispatch:
permissions:
contents: read
concurrency:
group: notification-platform-${{ github.ref }}
cancel-in-progress: true
jobs:
nightly-chaos:
name: chaos (ambiguity, restart recovery, callback burst)
runs-on: ubuntu-latest
timeout-minutes: 60
steps:
- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2
- uses: ./.github/actions/setup-gradle-java
# This job is named for ambiguity, restart recovery and callback burst. It used to run a
# unit-test filter and then `test` — neither of which restarts anything or bursts anything —
# so the job name was the only place those three properties existed.
- name: Ambiguity and fault harness
working-directory: src
run: ./gradlew :adapter:outbound:notification:test --tests '*ChaosSecurity*' --tests '*CrossProviderContractSuite*' --console=plain
- name: Concurrency and rotation races
working-directory: src
run: ./gradlew :adapter:outbound:notification:test --tests '*ConcurrencyTest' --tests '*ProviderRuntimeStateTest' --console=plain
- name: Restart recovery and lease fencing (real PostgreSQL)
working-directory: src
run: ./gradlew :adapter:outbound:persistence-jpa:jpaPlatformContractTest :adapter:outbound:persistence-jpa:jpaPlatformFailureTest --console=plain
- name: Notification regression suite
working-directory: src
run: >-
./gradlew
:application-core:test
:adapter:outbound:notification:test
:adapter:outbound:persistence-jpa:test
:adapter:inbound:web-notification:test
:composition:notification-platform:test
--console=plain
# A filter that matches nothing passes. Each --tests filter above names a class that exists
# today; if one is renamed the job must fail rather than quietly stop covering it.
- name: Every named suite actually ran
working-directory: src
run: |
set -euo pipefail
for suite in ChaosSecurity CrossProviderContractSuite ConcurrencyTest ProviderRuntimeStateTest; do
if ! find . -path '*/build/test-results/*' -name "*${suite}*.xml" | grep -q .; then
echo "no test results for ${suite}: the filter matched nothing and the job passed vacuously" >&2
exit 1
fi
done
# There is no provider-sandbox job. It ran only on workflow_dispatch and could not succeed by
# any path: with no credentials its first step exit 1-ed, and with credentials the only test it
# ran was ProviderSandboxSmokeTest, whose body is an unconditional fail() saying a real sandbox
# call is not implemented. Its credential check read secrets.NOTIFICATION_SANDBOX_CREDENTIALS,
# which nothing in this repository consumes — the test reads NOTIFICATION_SANDBOX_ENABLED — so
# any non-empty string satisfied it and was then dropped.
#
# The unimplemented state is still stated in two places that do not depend on a workflow:
# ProviderSandboxSmokeTest itself, and the unsatisfied provider-wire-qualified claim in
# docs/notification/evidence-manifest.json, which NotificationEvidenceVerifierTest enforces in
# the notification leaf's tests. When a real sandbox call is implemented, the job comes back with it.