fix(ci): provider job에 sandbox runner 요구를 적고 시작 때 namespace를 점검한다 #36
Closed
donghyeon.kang
wants to merge 0 commits from
donghyeon.kang/fix/provider-job-host-requirements AGit into main
pull from: donghyeon.kang/fix/provider-job-host-requirements
merge into: :main
:main
:fix/r9-structure-locale
:fix/r9-adapter-carryover
:test/shared-build-lock-order
:ci/dependency-cache-same-filesystem
:ci/release-tag-for-a11y-review
:ci/merge-dependency-cache
:fix/test-timeouts-measured
:fix/feature-residue-word-boundary
:fix/provider-wait-stderr
:fix/provider-job-host-requirements
:fix/ungated-vitest-spec
:fix/a11y-evidence-routes
:fix/verify-parts-diagnostics
:claude/w2-fe-ci-perf-dce080
:fix/child-process-test-timeouts
:chore/layout-rules-r2-r5
:claude/fe-b-docs-korean-645f55
:chore/ci-merge-jobs
:chore/layout-3-merge
:claude/fe-c-harness-0ae061
:chore/layout-2-sample-removal
:chore/layout-1-cleanup
:docs/review-guide-pointer
:fix/maturity-review-2026-11-06
:fix/maturity-review-2026-11-05-b
:docs/improvement-manual
:fix/maturity-review-2026-11-05
:fix/session-subject-required
:fix/ui-design-audit-2026-11-01
:fix/maturity-review-2026-09-25
:lane/D
:lane/B
:fix/src-review-round3
:refactor/domain-scalable
:develop
:feature-frontend-optional-adapter-recipes
:feature-frontend-supply-chain-verification
:feature-frontend-test-registry-evidence-hardening
:frontend-test-registry-evidence-hardening
:feature-frontend-diagnostics-telemetry-runtime
:feature-frontend-i18n-message-formatting-contract
:feature-frontend-design-system-platform
:feature-frontend-form-page-platform
:feature-frontend-reference-feature-vertical-slice
:feature-frontend-routing-release-recovery-runtime
:feature-frontend-http-query-contract-execution
:feature-frontend-application-boundary-runtime
:feature-frontend-typescript-tooling-foundation
:feature-frontend-platform-capability-review
:feature-frontend-performance-route-contract
:feature-frontend-starter-experience-quality-contract
:feature-frontend-responsive-theme-contract
:feature-frontend-ui-primitives-gallery-contract
:feature-frontend-app-shell-navigation-contract
:feature-frontend-runtime-composition-contract
:feature-frontend-ci-quality-gates-contract
:feature-web-vitals-performance-budget-contract
:feature-frontend-release-cache-rollback-contract
:feature-accessibility-baseline-contract
:feature-frontend-project-bootstrap-toolchain-contract
:feature-frontend-operational-runbook-contract
:feature-frontend-contract-compatibility-governance
:feature-frontend-contract-registry-governance
:feature-frontend-browser-security-boundary-contract
:feature-frontend-build-bundle-supply-chain-contract
:feature-tailwind-design-token-styling-contract
:feature-sample-feature-slice-contract-fixture
:feature-frontend-render-recovery-boundary-contract
:feature-routing-navigation-guard-contract
:feature-boundary-mapper-viewmodel-contract
:feature-async-ui-state-contract
:feature-frontend-observability-logging-trace-contract
:feature-frontend-storage-registry-contract
:feature-server-state-caching-contract
:feature-frontend-auth-session-integration-contract
:feature-frontend-error-classification-boundary-contract
:feature-runtime-schema-validation-contract
:feature-api-client-response-envelope-contract
:feature-frontend-env-runtime-config-contract
:feature-frontend-architecture-enforcement-lint-contract
:feature-frontend-test-taxonomy-contract
:feature-frontend-clean-architecture-layering-contract
No Reviewers
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
donghyeon.kang (동현 강)
Clear assignees
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: donghyeon.kang/clean-architecture-frontend-template#36
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
무엇을, 왜
release의 provider job 둘(vulnerability·provenance)은 FE-GATE-013과 같은 provider sandbox(systemd-run scope,
bwrap --unshare-pid/ipc/uts/net)를 돈다. 그런데 생성 workflow의 runner 요구 주석은 merge_test(FE-GATE-013)에만 있고 provider job에는 없다. provider 감독 스크립트의 시작 점검도 실행 파일이 있는지만 봐서, 비특권 user namespace를 막는 runner에서는 나중에 bwrap 원문 오류로 끝난다(round9 이월 1101/13-03, Medium·P2).고른 방법과 버린 대안
hostRequirements를 두고 provider job 둘에 FE-GATE-013과 같은 요구를 적는다. 계약이 provider job의 요구가 FE-GATE-013과 같은지 보고(갈라지면 거절), provider 밖 job은 이 칸을 쓰지 못한다. 생성기가 그 job의runs-on옆에 주석을 쓴다.scripts/check-system-test-prerequisites.ts에서 namespace 점검만 함수로 내보내고(findProviderSandboxNamespaceFailure),scripts/run-and-validate-provider.ts가 provider를 띄우기 전에 부른다. 실패하면 test:system 사전 점검과 같은 문구(제한 이름, bwrap stderr, host 설정, 고치는 법)로 멈춘다.위험과 영향
검증
system-test-prerequisites·ci-workflow-generation445개 통과.generate:ci-workflow·스냅샷 갱신,check:ci·check:types·eslint rc=0,verify:documentationPASS_SCOPED.scripts/verify.sh gate FE-GATE-013rc=0 226초(시스템 컨테이너, system 시험 115개 통과). 로그/tmp/claude-gates/w2fe2-prov1/,/tmp/claude-gates/w2fe2-prov013/.리뷰어가 볼 곳
scripts/contracts/ci-gates.ts의 provider job 요구 대조,scripts/generate-ci-workflow.ts의renderHostRequirements.scripts/run-and-validate-provider.ts의 시작 점검 위치(provider를 띄우기 전)..gitea/workflows/quality-gates.yml은 생성 파일이다.관련
docs/operations/ci-quality-gates.md비특권 user namespace 절.#40으로 병합됐다(main
ee47480c). 이 PR의 head9ebd0856가 #40 브랜치에 merge 커밋으로 들어 있고, #40의 runner merge job 셋이 그 합친 트리로 초록이었다. runner 대기를 줄이려고 이번만 쓴 방식이다(소유자 승인, 2026-11-13).Pull request closed