Manual workflow for tagged versions #136
Conversation
Signed-off-by: Carlo Lobrano <[email protected]>
Signed-off-by: Carlo Lobrano <[email protected]>
|
Skipping CI for Draft Pull Request. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: clobrano 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 |
bundle/manifests/fence-agents-remediation.clusterserviceversion.yaml
Outdated
Show resolved
Hide resolved
Signed-off-by: Carlo Lobrano <[email protected]>
Signed-off-by: Carlo Lobrano <[email protected]>
Signed-off-by: Carlo Lobrano <[email protected]>
- removed unnecessary skip_range_lower input - correctly log the other inputs Signed-off-by: Carlo Lobrano <[email protected]>
Signed-off-by: Carlo Lobrano <[email protected]>
clobrano
force-pushed
the
automate-rh-community-bundle-0
branch
from
3fd8f51
to
1c4cd22
Compare
|
/lgtm |
|
@clobrano: The following tests 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. |
|
E2E tests do not test the changes of this PR. Can merge without them. |
Why we need this PR
FAR CI uses the post-release workflow for building and pushing versioned bundle images, however, the workflow cannot guess the right PREVIOUS_VERSION (when it is necessary) and it would publish manifests with wrong value of the
.spec.replacesfield.Changes made
post-releaseto thereleaseworkflow, which supports manual inputs such has PREVIOUS_VERSIONreleaseworkflow with the latest version of Medik8s shared workflow to build and push community bundlesspec.replacesfield only in OKD bundleTest plan
Tested locally with nektos/act
ECOPROJECT-1579