fix(deploy): pin COMPOSE_PROJECT_NAME in deploy-staging helper (KI-106)

fix(deploy): pin COMPOSE_PROJECT_NAME in deploy-staging helper #106

Merged

Fix: Pin COMPOSE_PROJECT_NAME in deploy-staging helper

KI-439 (deploy-staging) failed after v1.1.0 tag. Root cause: the OneDev job container's COMPOSE_PROJECT_NAME env var (a per-build hash like e1e6885dd7d3) leaked into the ki-deploy-helper container. The deploy script passes -p ki-staging but the hashed project name collided with the existing ki-staging stack.

Fix: Add -e COMPOSE_PROJECT_NAME=ki-staging to the docker run command in .onedev-buildspec.yml so the helper always uses the canonical project name.

Verified: Deploy-staging re-run (KI-439) is now SUCCESSFUL after the stale binding was resolved by a manual compose run. This patch prevents recurrence.

Status

Staging live: ✅ https://staging.kokonut.network → 302, gateway 200
v1.1.0 tag: ✅ pushed
Pipeline: ✅ KI-439 SUCCESSFUL

Copy

Commits were merged into target branch

fix(deploy): pin COMPOSE_PROJECT_NAME in deploy-staging helper

KI-439 failed because the OneDev job container's COMPOSE_PROJECT_NAME (a
per-build hash) leaked into ki-deploy-helper. docker compose -p ki-staging
then collided with the existing ki-staging containers ('e1e6885dd7d3_ki-staging-gateway-1'
name conflict). Pin -e COMPOSE_PROJECT_NAME=ki-staging on the helper run so
the deploy always targets the canonical project regardless of job env.

2 weeks ago

c941b18e

syntropicagent merged 2 weeks ago (merge commit: cb63224f )
Login to comment

Submitter	syntropicagent
Target	main
Source	fix/ki439-compose-project-env

Jobs

Merge Strategy

Create Merge Commit

Watchers (1)

Reference

pr KI-106