GitHub Actions workflow for building and pushing multi-platform Docker images to Docker Hub #78
Conversation
joel-ling
changed the title
| push: true | ||
| sbom: true | ||
| tags: >- | ||
| ${{ secrets.DOCKERHUB_ORGANIZATION_NAME }}/${{ vars.IMAGE_NAME }}:master |
There was a problem hiding this comment.
Given that we have a main branch not a master branch, using the master tag feels a little weird.
There was a problem hiding this comment.
Thanks, @neilcook!
Given that we have a
mainbranch not amasterbranch, using themastertag feels a little weird.
I have changed the tag from master to main.
I guess this is hard to test without actually pushing to the main branch or tagging a release.
Not to worry, the workflows are passing in the fork (we are about to merge), albeit using alternative variables and secrets, hence pushing to a different repository on Docker Hub.
|
Confirmed that |
Merging this pull request would add two Actions workflows:
main"The first of the two workflows runs automatically whenever a tag of the following format is pushed:
v[0-9]+.[0-9]+.[0-9]+. The second is run whenever themainbranch is pushed to.Both workflows build and push images for the platforms specified by the Actions variable
PLATFORMS.Image tags are formatted as follows:
<ORGANISATION_NAME>/<IMAGE_NAME>:<MAJOR>.<MINOR>.<PATCH>(andlatest), or<ORGANISATION_NAME>/<IMAGE_NAME>:main, as may be the case.The Docker Hub organisation name, username, and access token are automatically populated with GitHub Actions Secrets, while the image name is an Actions variable of the repository.