Skip to content
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(ci/windows): Downgrade MSVC build tools #2836

Closed

Conversation

tens0rfl0w
Copy link
Contributor

Goal of this PR

Github Actions running on 'windows-latest' get shipped with VS 2022 C++ x64/x86 build tools v14.41-17.11 which includes various breaking changes that make building on the CI pipeline fail.

How is this PR achieving the goal

Github Actions doesn't allow to use older image versions, so we downgrade VS build tools to v14.40-17.10 manually as a temporary fix. This only downgrades necessary components to avoid increasing the build time any further.

This can be reverted once the build tool chain got updated.

This PR applies to the following area(s)

CI, Building

Successfully tested on

Game builds: Not applicable

Platforms: Github Actions - Windows Latest

Checklist

  • Code compiles and has been tested successfully.
  • Code explains itself well and/or is documented.
  • My commit message explains what the changes do and what they are for.
  • No extra compilation warnings are added by these changes.

Fixes issues

/

Github Actions running on 'windows-latest' get shipped with VS 2022 C++ x64/x86 build tools v14.41-17.11 which includes various breaking changes.

This manually downgrades VS build tools to v14.40-17.10 as a temporary fix till the build tool chain is updated.
@github-actions github-actions bot added the triage Needs a preliminary assessment to determine the urgency and required action label Oct 3, 2024
@FabianTerhorst
Copy link
Contributor

Does that mean we don't need this pull request anymore with #2837?

@tens0rfl0w
Copy link
Contributor Author

Does that mean we don't need this pull request anymore with #2837?

Correct, once 2837 got merged this workaround isn't needed anymore.

@FabianTerhorst
Copy link
Contributor

Ok then this probably can be closed, because merging both at the same time won't be needed.

@tens0rfl0w
Copy link
Contributor Author

Superseded by #2837

@tens0rfl0w tens0rfl0w closed this Oct 4, 2024
@tens0rfl0w tens0rfl0w deleted the fix/ci/windows-msvc-downgrade branch October 4, 2024 15:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage Needs a preliminary assessment to determine the urgency and required action
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants