-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Upgrade to Go1.18 #13201
Upgrade to Go1.18 #13201
Conversation
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.
👍 for docs.
dbb9087
to
b3004dd
Compare
21c1a0c
to
881940f
Compare
I didn't realize I had forgotten to mark this as "draft" - sorry! |
* builds from DataDog/datadog-agent-buildimages#270 * builds from https://github.com/DataDog/datadog-agent-builders/pull/224 * already using the new macos build image
881940f
to
eae9a2a
Compare
It looks like the only two non-green things here were due to GitHub workers dying, not to Go1.18. One is CodeQL, which shouldn't depend on the Go version. The other is the MacOS tests, which have secretly been running Go1.18 for a day or two already without trouble. At any rate, I've re-run them both. Now it's time for review. |
Great work thanks ! Do you plan to setup a go workspace afterwards ? https://go.dev/doc/tutorial/workspaces |
I wasn't planning on doing so myself. However, we've been discussing having each component bundle be a distinct module, in which case go workspaces might be very useful. Are you interested in digging into that idea? |
This was not enabled before Go1.18 and appears to be failing. It can be fixed in a followup
Co-authored-by: Ahmed Mezghani <[email protected]>
This reverts commit e6f6941. This reverts DataDog/datadog-agent-buildimages#272 as well -- to be addressed in a followup.
This reverts commit e6f6941. This reverts DataDog/datadog-agent-buildimages#272 as well -- to be addressed in a followup.
What does this PR do?
Updates everything to Go1.18.5.
Motivation
Additional Notes
Possible Drawbacks / Trade-offs
Describe how to test/QA your changes
General agent QA -- at this stage, running in various clusters and looking for issues.
Reviewer's Checklist
Triage
milestone is set.major_change
label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.changelog/no-changelog
label has been applied.qa/skip-qa
label is not applied.team/..
label has been applied, indicating the team(s) that should QA this change.need-change/operator
andneed-change/helm
labels have been applied.k8s/<min-version>
label, indicating the lowest Kubernetes version compatible with this feature.