-
Notifications
You must be signed in to change notification settings - Fork 545
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix release automation #3426
Fix release automation #3426
Conversation
You should also delete this file since (a) it doesn't seem to be used anymore and (b) will be confusing (it currently hasn't been touched in 3 years and has "0.19.0" in it) https://github.com/operator-framework/operator-lifecycle-manager/blob/master/OLM_VERSION |
@jmazzitelli I agree with you. I'm planning to look into it, but will probably do that in a separate PR. |
/hold Need to fix the release job for non-tag scenarios: |
Signed-off-by: Mikalai Radchuk <[email protected]>
ae23339
to
3c385f6
Compare
@@ -60,7 +59,8 @@ jobs: | |||
PKG: github.com/operator-framework/operator-lifecycle-manager | |||
|
|||
- name: Generate quickstart release manifests | |||
run: make release ver=${{ env.IMAGE_TAG }} IMAGE_REPO=quay.io/operator-framework/olm | |||
if: startsWith(github.ref, 'refs/tags') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Adding this condition back (was removed in #3293). This step pulls an image and we don't have an image when running against anything other than a tag.
/unhold Should be good now |
5a01f50
Description of the change:
Our release automation is broken after refactoring in #3280: we are no longer passing a real version number from the release workflow.
Fixes #3419
Architectural changes:
None
Testing remarks:
Need to create a new tag to trigger the workflow
Reviewer Checklist
/doc
[FLAKE]
are truly flaky and have an issue