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

[v12.x] build: pin Windows GitHub runner to windows-2019 #42349

Closed
wants to merge 2 commits into from

Conversation

richardlau
Copy link
Member

GitHub is removing the Windows 2016 runner image on March 15, 2022.

Refs: https://github.blog/changelog/2021-10-19-github-actions-the-windows-2016-runner-image-will-be-removed-from-github-hosted-runners-on-march-15-2022/


March 15, 2022 is today 😰. They're not gone yet -- #42348 is running on them, but we'll need to move.

@nodejs-github-bot
Copy link
Collaborator

Review requested:

  • @nodejs/actions

@github-actions github-actions bot added meta Issues and PRs related to the general management of the project. v12.x labels Mar 15, 2022
@richardlau
Copy link
Member Author

Hmm, that didn't work https://github.com/nodejs/node/runs/5558888762?check_suite_focus=true 😞
It looked like Node.js 12 should be able to build with VS 2019:

node/vcbuild.bat

Lines 295 to 311 in 3901891

@rem check if VS2019 is already setup, and for the requested arch
if "_%VisualStudioVersion%_" == "_16.0_" if "_%VSCMD_ARG_TGT_ARCH%_"=="_%target_arch%_" goto found_vs2019
@rem need to clear VSINSTALLDIR for vcvarsall to work as expected
set "VSINSTALLDIR="
@rem prevent VsDevCmd.bat from changing the current working directory
set "VSCMD_START_DIR=%CD%"
set vcvars_call="%VCINSTALLDIR%\Auxiliary\Build\vcvarsall.bat" %vcvarsall_arg%
echo calling: %vcvars_call%
call %vcvars_call%
if errorlevel 1 goto msbuild-not-found
if defined DEBUG_HELPER @ECHO ON
:found_vs2019
echo Found MSVS version %VisualStudioVersion%
set GYP_MSVS_VERSION=2019
set PLATFORM_TOOLSET=v142
goto msbuild-found

@richardlau
Copy link
Member Author

Hmm, that didn't work https://github.com/nodejs/node/runs/5558888762?check_suite_focus=true 😞

Needed to change

if "_%VCINSTALLDIR%_" == "__" goto msbuild-not-found

so that it searches for VS2019 when it fails to find VS2017: 94956e0

@richardlau richardlau added the request-ci Add this label to start a Jenkins CI on a PR. label Mar 15, 2022
@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Mar 15, 2022
@nodejs-github-bot
Copy link
Collaborator

@richardlau richardlau added the fast-track PRs that do not need to wait for 48 hours to land. label Mar 15, 2022
@richardlau
Copy link
Member Author

cc @nodejs/platform-windows @nodejs/build-files

@richardlau richardlau added fast-track PRs that do not need to wait for 48 hours to land. and removed fast-track PRs that do not need to wait for 48 hours to land. labels Mar 15, 2022
@richardlau
Copy link
Member Author

richardlau commented Mar 15, 2022

Fast-track has been requested by @richardlau. Please 👍 to approve.

@nodejs-github-bot
Copy link
Collaborator

@Mesteery
Copy link
Contributor

Mesteery commented Mar 16, 2022

I'm not sure if the fast-track label/comment thing works for v12.x.

I don't think it's normal that it doesn't work.

By the way, I have modified your message so that there are no problems with ncu.

@aduh95
Copy link
Contributor

aduh95 commented Mar 16, 2022

I'm not sure if the fast-track label/comment thing works for v12.x.

I don't think it's normal that it doesn't work.

I think it is, the workflow hasn't been backported to v12.x-staging: https://github.com/nodejs/node/tree/v12.x-staging/.github/workflows

@Mesteery
Copy link
Contributor

Oh right, I thought it was the workflows of the main branch that took precedence.

richardlau added a commit that referenced this pull request Mar 16, 2022
If Visual Studio 2017 is not found, attempt to find Visual Studio 2019.

PR-URL: #42349
Refs: https://github.blog/changelog/2021-10-19-github-actions-the-windows-2016-runner-image-will-be-removed-from-github-hosted-runners-on-march-15-2022/
Reviewed-By: Mestery <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Antoine du Hamel <[email protected]>
richardlau added a commit that referenced this pull request Mar 16, 2022
GitHub is removing the Windows 2016 runner image on March 15, 2022.

Refs: https://github.blog/changelog/2021-10-19-github-actions-the-windows-2016-runner-image-will-be-removed-from-github-hosted-runners-on-march-15-2022/

PR-URL: #42349
Reviewed-By: Mestery <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Antoine du Hamel <[email protected]>
@richardlau
Copy link
Member Author

Landed in 4ee4490...a64a3ca.

@richardlau richardlau closed this Mar 16, 2022
@richardlau richardlau deleted the workflow-v12.x branch March 16, 2022 15:33
@richardlau richardlau mentioned this pull request Mar 16, 2022
richardlau added a commit that referenced this pull request Mar 16, 2022
If Visual Studio 2017 is not found, attempt to find Visual Studio 2019.

PR-URL: #42349
Refs: https://github.blog/changelog/2021-10-19-github-actions-the-windows-2016-runner-image-will-be-removed-from-github-hosted-runners-on-march-15-2022/
Reviewed-By: Mestery <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Antoine du Hamel <[email protected]>
richardlau added a commit that referenced this pull request Mar 16, 2022
GitHub is removing the Windows 2016 runner image on March 15, 2022.

Refs: https://github.blog/changelog/2021-10-19-github-actions-the-windows-2016-runner-image-will-be-removed-from-github-hosted-runners-on-march-15-2022/

PR-URL: #42349
Reviewed-By: Mestery <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Antoine du Hamel <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fast-track PRs that do not need to wait for 48 hours to land. meta Issues and PRs related to the general management of the project.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants