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

PSA: decommissioning of Node.js 12 infrastructure #3048

Closed
1 of 2 tasks
richardlau opened this issue Oct 5, 2022 · 2 comments
Closed
1 of 2 tasks

PSA: decommissioning of Node.js 12 infrastructure #3048

richardlau opened this issue Oct 5, 2022 · 2 comments

Comments

@richardlau
Copy link
Member

richardlau commented Oct 5, 2022

According to README.md in this repository:

The Build WG will keep build configuration required for a release line for 6 months after the release goes End-of-Life, in case further build or test runs are required. After that the configuration will be removed.

Node.js 12 went End-of-Life in April so we're approaching the end of the 6 month period and in all likelihood we're not going to be building Node.js 12 again. I plan to start cleaning up really old CI infrastructure that we kept around for Node.js 12 that is no longer used.

  • Disable https://ci.nodejs.org/job/node-daily-v12.x-staging/. This has been running daily to give some indication that the builds still work. Replace this with a daily job for v14.x so we're testing the earliest infrastructure we need to keep running.
  • Identify and remove platforms from the CI that are no longer required for Node.js 14 onwards. This will help with things like Jenkins agents need newer Java (11+) #3030 where End-of-Life operating systems do not provide later versions of Java in their package repositories.
@mhdawson
Copy link
Member

Thanks for doing this.

@github-actions
Copy link

github-actions bot commented Aug 9, 2023

This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made.

@github-actions github-actions bot added the stale label Aug 9, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants