Cirrus: Use branch-specific container tags #4503
Conversation
Automated building of container images is handled in quay.io based on changes in the master branch of this repository. However, as additional branches are made, the "latest" image (from master) diverges from their expectations. Fix this by using the branch-tagged images built by quay. For the near-term, this also implies quay.io will be configured to also build different images for each branch, and tag them appropriately. Long-term, image build automation should be combined with libpod automation - to avoid needing to maintain automation in multiple systems/locations. Signed-off-by: Chris Evich <[email protected]>
|
@mheon this is needed so automated branch-specific builds can be added for the other branches, and not break automation here (on master). |
|
/approve |
1 similar comment
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: baude, cevich, mheon The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
1 similar comment
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: baude, cevich, mheon The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci-robot
added
the
approved
|
/lgtm |
github-actions
bot
added
the
locked - please file new issue/PR
Automated building of container images is handled in quay.io based on
changes in the master branch of this repository. However, as additional
branches are made, the "latest" image (from master) diverges from their
expectations. Fix this by using the branch-tagged images built by quay.
For the near-term, this also implies quay.io will be configured to also
build different images for each branch, and tag them appropriately.
Long-term, image build automation should be combined with libpod
automation - to avoid needing to maintain automation in multiple
systems/locations.
Signed-off-by: Chris Evich [email protected]