Skip to content

kokoro: clarify that MSVC flows are MSVC 2019#1070

Merged
dneto0 merged 3 commits intogoogle:mainfrom
dneto0:msvc-2019
Jan 6, 2025
Merged

kokoro: clarify that MSVC flows are MSVC 2019#1070
dneto0 merged 3 commits intogoogle:mainfrom
dneto0:msvc-2019

Conversation

@dneto0
Copy link
Copy Markdown
Collaborator

@dneto0 dneto0 commented Dec 23, 2024

They are running MSVC, but the jobs and directories are mislabeled as MSVC 2017.

Bug: crbug.com/385757633 (internal)
Change-Id: I8bd757e6bc13e4e7f20bb3f4d4dc30236d585361

They are running MSVC, but the jobs and directories are mislabeled
as MSVC 2017.

Bug: crbug.com/385757633 (internal)
Change-Id: I8bd757e6bc13e4e7f20bb3f4d4dc30236d585361
@dneto0 dneto0 requested a review from dj2 December 23, 2024 21:11
@dneto0
Copy link
Copy Markdown
Collaborator Author

dneto0 commented Dec 23, 2024

This has to wait until a google-internal CL lands to change the targeted config file name.

Copy link
Copy Markdown
Collaborator

@dj2 dj2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we delete the 2017 folders?

Change-Id: If24a688c7c565a03e3015722ee8fa110c208b907
@dneto0
Copy link
Copy Markdown
Collaborator Author

dneto0 commented Dec 23, 2024

Should we delete the 2017 folders?

Yes. I accidentally left that out. :-)

@dneto0 dneto0 marked this pull request as ready for review December 23, 2024 21:57
Pass the visual studio version to the windows build script

Change-Id: I1cf21ed387a52f4a260211be9964d84dc446d2f4
@dneto0 dneto0 merged commit a3501fc into google:main Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants