chore: build and publish workflow (PROJQUAY-2556) #912
Conversation
|
Can one of the admins verify this patch? |
flavianmissi
force-pushed
the
build-workflow
branch
from
febd66d
to
5af449d
Compare
| env: | ||
| BRANCH_PREFIX: redhat- # IMPORTANT! this must match the .on.push.branches prefix! | ||
| REGISTRY: quay.io/projectquay | ||
| REPO_NAME: ${{ github.event.repository.name }} |
There was a problem hiding this comment.
Is this quay, or quay/quay. In either case, is ${{ env.REGISTRY }}/${{ env.REPO_NAME }}:${{ env.TAG }} below correct?
Otherwise LGTM
There was a problem hiding this comment.
TL;DR: If built from redhat-3.5 branch for example, then ${{ env.REGISTRY }}/${{ env.REPO_NAME }}:${{ env.TAG }} is evaluated to quay.io/projectquay/quay:3.5-unstable.
REPO_NAME is evaluated to quay. Check this out https://github.com/flavians-test-org/build-me/runs/3755985838?check_suite_focus=true, and expand the Echo repository name step.
The workflow used there is nearly identical the one in this PR: https://github.com/flavians-test-org/build-me/actions/runs/1291052126/workflow#L15
And the generated tags for my tests: https://quay.io/repository/fmissi/build-me?tag=latest&tab=tags
No description provided.