ci:publish bundle image with latest tag #431
Conversation
lihongyan1
requested review from
danielmellado and
slashpai
and removed request for
a team
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: lihongyan1 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
The lack of catalog images is my fault. The publish action is faling since we moved to |
|
#432 should fix the issue. |
#432 can't fix the issue, it doesn't make sense to test a release image in olm-catalog branch. #222 is not fixed and for every PR merged to main still has pipeline error, such as the following action, failed to publish olm development |
Catalog image didn't build for a long time for issue rhobs#222 The issue suggest to use bundle image to install operator Publish bundle iamge with latest tag to refer the image easily
lihongyan1
force-pushed
the
publish-bundle-latest
branch
from
738f16a
to
45016cc
Compare
|
@lihongyan1: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
#432 fixs the issue. So I closed the pr |
Catalog image didn't build for a long time for issue #222, it suggest to use bundle image to install operator, so publish bundle iamge with latest tag, so that refer the latest image easily during test