Skip to content

feat: build and push branch images tagged with the branch name - #84

Open
MateoLostanlen wants to merge 9 commits into
mainfrom
feat/build-push-branch-images
Open

feat: build and push branch images tagged with the branch name#84
MateoLostanlen wants to merge 9 commits into
mainfrom
feat/build-push-branch-images

Conversation

@MateoLostanlen

@MateoLostanlen MateoLostanlen commented Jul 31, 2026

Copy link
Copy Markdown
Member
  • Adds bin/build-push-images.sh to build a PR branch of the api (pyronear/pyro-api -> alert-api), engine (pyro-engine -> pyro-engine + pyro-camera-api) or platform (new-pyro-platform -> pyro-platform-react) and push it to Docker Hub tagged with the branch name, for testing on preprod before merge. The tag drops the branch's type prefix and sanitizes invalid characters (feat/my-fix -> my-fix), so CI's :latest is never overwritten.
  • To deploy, pin the pushed tag in the sister repo (platform_react_docker_version / alert_api_docker_version in envpreprod, pyro_engine_docker_tag in the engine's host_vars) and redeploy; the Readme documents the full walkthrough.
  • Each image targets its deployment architecture: linux/amd64 for api/platform (servers), linux/arm64 for engine images (Raspberry Pi). The platform app is built with pnpm in a throwaway node:24 container before the docker build, matching CI.
  • New make build-push COMPONENT=<api|engine|platform> BRANCH=<branch> host target; requires docker with buildx and a Docker Hub login with push rights on the pyronear org. COMPONENT/BRANCH are passed via the environment so branch names cannot inject shell commands.

@MateoLostanlen MateoLostanlen changed the title feat: build and push branch images to Docker Hub as latest feat: build and push branch images tagged with the branch name Aug 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant