Document runner capacity increase in the provisioning log
All checks were successful
CD / Promote to Int (push) Successful in 9s
CI / Lint, typecheck, test (push) Successful in 2m48s
CI / Auth e2e pack (push) Successful in 3m46s
CI / Import/export fidelity gate (push) Successful in 43s
CI / Build container images (push) Has been skipped
CD / Build and push images (push) Successful in 1m0s
CD / Deploy to Test (push) Successful in 11s
CD / Smoke tests against Test (push) Successful in 1m3s
All checks were successful
CD / Promote to Int (push) Successful in 9s
CI / Lint, typecheck, test (push) Successful in 2m48s
CI / Auth e2e pack (push) Successful in 3m46s
CI / Import/export fidelity gate (push) Successful in 43s
CI / Build container images (push) Has been skipped
CD / Build and push images (push) Successful in 1m0s
CD / Deploy to Test (push) Successful in 11s
CD / Smoke tests against Test (push) Successful in 1m3s
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EwZ4jR4KFAPvpjWevfUGX1
This commit is contained in:
parent
514cdf5ead
commit
6e56403102
@ -147,3 +147,7 @@ The pipeline pushes images to the Gitea container registry
|
||||
commented out), act_runner `one-dorfteich` registered, old VPS runner
|
||||
and stacks stopped (kept as rollback reserve). `DEPLOY_HOST` in
|
||||
`cd.yml` and the `DEPLOY_HOST_KEY` secret updated accordingly.
|
||||
- 2026-07-11 (later): act_runner capacity raised from 1 to 4 in
|
||||
`/home/deploy/act_runner/config.yaml` — ONE has the headroom, so the
|
||||
independent CI jobs now run in parallel (the CD chain stays sequential
|
||||
via `needs:`).
|
||||
|
||||
Loading…
Reference in New Issue
Block a user