chore: Automate container image building #4
Conversation
Build for platform `linux/arm64` and `linux/amd64`. Add tag base on git tags: `edge` - any last build `latest` - last build base on default branch changes `vx.y.z` - build connected to the git tag `pr-xxx` - build related to PR
4426f4c to
8d797c8
Compare
| push: | ||
| branches: | ||
| - main | ||
| - master |
There was a problem hiding this comment.
I added master, as I am using it on my fork. But I am ok to remove it, let me know your preference.
There was a problem hiding this comment.
It's fine to keep both. The only reasons I know of to restrict them are to avoid being charged for too many build hours and to avoid being charged too much for container images storage. I don't think I'm in danger of either of those — these images are like 10MB and are built about 4 times every few months.
|
Amazing, I hadn't setup automated builds specifically because I thought GHA didn't support arm64 builds. GHA not supporting arm64 was the main reason the I use arm64 nodes on GCP (I don't know how, but I got them for free), so I need it built for that arch, so I've just been building it manually. So I'm really glad you found a way to make this work! |
Build for platform
linux/arm64andlinux/amd64.Add tag base on git tags:
edge- any last buildlatest- last build base on default branch changesvx.y.z- build connected to the git tagpr-xxx- build related to PRBuild images in Dockerhub and Github packages.
For DockerHub it requires secrets: DOCKER_USERNAME and DOCKER_PASSWORD
Tophat
Example of job for my fork push to master branch: https://github.com/miry/rails_app_operator/actions/runs/8868090021/job/24347314572
Example of job for my fork for new tag: https://github.com/miry/rails_app_operator/actions/runs/8868182984/job/24347505933
Results: