Skip to content

[CI] No workflow builds the backend Docker image, so Dockerfile/compose breakages ship undetected #889

Description

@grantfox-oss

Telegram (ask questions / claim the issue here first): https://t.me/+DOylgFv1jyJlNzM0

Why this matters

There are three workflows (ci.yml, security.yml, pr-test-gate.yml) and none runs docker build on backend/Dockerfile or docker compose build. Because backend tests run via vitest against src/, the compiled dist/ runtime path and the image are never exercised in CI - which is why a broken production image can merge green.

Acceptance criteria

  • Add a CI job that runs docker build -f backend/Dockerfile backend (and optionally docker compose build)
  • Optionally boot the image and curl /health to catch missing-runtime-file regressions
  • Run the job on PRs that touch backend/ or Docker files

Files to touch

  • .github/workflows/ci.yml
  • backend/Dockerfile
  • docker-compose.yml

Out of scope

  • Pushing images to a registry
  • Multi-arch builds

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Stellar WaveIssues in the Stellar wave programdevopsInfrastructure and CI/CDenhancementNew feature or requestgithub_actionsPull requests that update GitHub Actions codetestingTesting related tasks

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions