-
Notifications
You must be signed in to change notification settings - Fork 24
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
hack: add go-version-check.sh script #315
Merged
mergify
merged 3 commits into
samba-in-kubernetes:master
from
phlogistonjohn:jjm-go-vers-2
Aug 28, 2023
Merged
hack: add go-version-check.sh script #315
mergify
merged 3 commits into
samba-in-kubernetes:master
from
phlogistonjohn:jjm-go-vers-2
Aug 28, 2023
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
synarete
reviewed
Aug 24, 2023
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.
OK, but few style comments
phlogistonjohn
force-pushed
the
jjm-go-vers-2
branch
from
August 24, 2023 12:39
a2f3495
to
e1496d1
Compare
Go 1.20 was recently released so this gets us back on a supported golang version when building via the container. Signed-off-by: John Mulligan <[email protected]>
phlogistonjohn
force-pushed
the
jjm-go-vers-2
branch
from
August 24, 2023 12:45
e1496d1
to
1132c6e
Compare
anoopcs9
requested changes
Aug 28, 2023
This script validates the Dockefile (or other specified container files) or shows the list of current supported golang version images. The goal is to ensure we are continually using a supported Go version and not falling behind. Signed-off-by: John Mulligan <[email protected]>
Add a new check-dockerfile-go-version makefile target and include it in the check target. This runs the recently added script to validate the version of golang used to build in container. The downside of this approach is that PRs & other work unrelated to Golang may periodically break when Go issues a new major release. Let's try this for now and if it ends up getting really annoying we can try to do some other form of automation to alert us to the need of a version bump that doesn't interfere with unrelated work. Signed-off-by: John Mulligan <[email protected]>
phlogistonjohn
force-pushed
the
jjm-go-vers-2
branch
from
August 28, 2023 14:11
1132c6e
to
2cc8d55
Compare
synarete
approved these changes
Aug 28, 2023
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.
Good catch by @anoopcs9 -- LGTM now
anoopcs9
approved these changes
Aug 28, 2023
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related to, but not blocked on, #314
Add a script that validates the Dockefile (or other specified container files) or shows the list of current supported golang version images. The goal is to ensure we are continually using a supported Go version and not falling behind.
Add a new check-dockerfile-go-version makefile target and include it in the check target. This runs the recently added script to validate the version of golang used to build in container.
The downside of this approach is that PRs & other work unrelated to Golang may periodically break when Go issues a new major release.
Let's try this for now and if it ends up getting really annoying we can try to do some other form of automation to alert us to the need of a version bump that doesn't interfere with unrelated work.