Commits were merged into target branch
-
2 weeks ago
-
| Submitter | syntropicagent |
| Target | main |
| Source | chore/ci-cleanup |
Jobs
Merge Strategy
Create Merge Commit
CI cleanup — tear down ki-ci stack after each build
Problem: The CI job creates a disposable compose stack (
ki-ci: database, clickhouse, cache, directus, gateway, grpc) against the host daemon via the mounted docker socket. The buildspec never tore it down, so 6 containers lingered between builds, consuming ~1-2 GB RAM 24/7. This contributed to the KI-453 deploy-staging timeout: the OneDev agent couldn't allocate a job container while the host was memory-exhausted (7.8 GB total, ~250 MB free, 4 GB swap in use).Fix: Add a cleanup step after "All CI checks complete":
|| trueensures a cleanup failure never fails the build. The.env(with secrets) exists during the build, so compose can interpolate at teardown time.Verified:
tod build check-specpasseski-cicontainers force-removed from cerberus (memory freed)Follow-up (not in this PR): the same teardown pattern could be applied to CI build-cache volume hygiene if disk (58/96 GB) becomes a concern.