-
Notifications
You must be signed in to change notification settings - Fork 88
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
Use fleet-server binary version for cloude2e images #3314
Use fleet-server binary version for cloude2e images #3314
Conversation
Use the fleet-server binary version with snapshot flag when building the cloude2e test image instead of the stack version so fleet-server builds will not fail on version bumps.
@@ -286,7 +286,7 @@ release-manager-release: ## - Builds a snapshot release. The Go version defined | |||
## get-version : Get the Fleet server version | |||
.PHONY: get-version | |||
get-version: | |||
@echo $(DEFAULT_VERSION) | |||
@echo $(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.
$VERSION
differs from $DEFAULT_VERSION
as it may include snapshot or other version indicators.
The only other target (besides cloude2e) that uses get-version
is the buildkite dra target, which should filter out the snapshot indicator
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.
LGTM 🚀
|
Use the fleet-server binary version with snapshot flag when building the cloude2e test image instead of the stack version so fleet-server builds will not fail on version bumps. (cherry picked from commit 8f7dcc9)
Use the fleet-server binary version with snapshot flag when building the cloude2e test image instead of the stack version so fleet-server builds will not fail on version bumps. (cherry picked from commit 8f7dcc9)
Use the fleet-server binary version with snapshot flag when building the cloude2e test image instead of the stack version so fleet-server builds will not fail on version bumps. (cherry picked from commit 8f7dcc9) Co-authored-by: Michel Laterman <82832767+michel-laterman@users.noreply.github.com>
Use the fleet-server binary version with snapshot flag when building the cloude2e test image instead of the stack version so fleet-server builds will not fail on version bumps. (cherry picked from commit 8f7dcc9) Co-authored-by: Michel Laterman <82832767+michel-laterman@users.noreply.github.com>
Use the fleet-server binary version with snapshot flag when building the cloude2e test image instead of the stack version so fleet-server builds will not fail on version bumps.
What is the problem this PR solves?
Bumping fleet-server versions causes the cloude2e test to fail
How does this PR solve the problem?
Use the fleet-server binary version with snapshot flag when building the cloude2e test image instead of the stack version so fleet-server builds will not fail on version bumps.