-
Notifications
You must be signed in to change notification settings - Fork 9
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
ci: on release check version string is the expected one #278
Conversation
Signed-off-by: Eguzki Astiz Lezaun <[email protected]>
Signed-off-by: Eguzki Astiz Lezaun <[email protected]>
Signed-off-by: Eguzki Astiz Lezaun <[email protected]>
Signed-off-by: Eguzki Astiz Lezaun <[email protected]>
5a02b09
to
8a14077
Compare
Signed-off-by: Eguzki Astiz Lezaun <[email protected]>
@@ -528,6 +528,9 @@ prepare-release: ## Generates a makefile that will override environment variable | |||
$(MAKE) bundle | |||
$(MAKE) helm-build VERSION=$(VERSION) | |||
|
|||
.PHONY: read-release-version | |||
read-release-version: ## Reads release version | |||
@echo "v$(VERSION)" |
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.
👍 Using the single version from the makefile makes sense to me. On release branches we set this as an override as part of the release process https://github.com/Kuadrant/dns-operator/blob/v0.6.0/make/release.mk#L7
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.
I know :)
I think that I will bring this release.mk approach to the other projects
What
Follow up work from #274
CI check to ensure release version in go code matches git version tag
Release version passed in by ldflag
Verification steps: create a release that should succeed.
Run prepare release for final version
v0.0.100
.Verify local changes, commit, push and tag with the typo:
Verify that the build image for release tag workflow is triggered and completes for the new tag
Verification steps: create a release that should fail.
Let's prepare a release with a typo.
Run prepare release for final version
v0.0.200
.Verify local changes, commit, push and tag with one typo: instead of tag
v0.0.200
which would be the right one, tag it withv0.0.201
.Verify that the build image for release tag workflow is triggered and fails.
Checking CI logs
So, the step named
Verify git reference name matches the release version
should fail.