-
Notifications
You must be signed in to change notification settings - Fork 0
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
Node.js MacStadium tasks #17
Comments
Something seems wrong with the VPN we use to access/adminster the orka cluster. I got in there today to begin work on adding support to the testing ephemeral images so that they have a mountable disk to store the ccache, and the VPN will only connect for about a minute before disconnecting. I opened up a support request with MacStadium. |
VPN Issue is solved. Next up:
|
This was discussed in the build WG meeting, and so that everybody is aware, this is top priority for ryan's available cycles from the build teams perspective (other than short term fires) as it is blocking a number of PR's and V8 upgrades in the Node.js project. |
@bensternthal thanks for the update and great to hear! |
For visiblity this (or possibly unrelated issues with MacOS infra) is now blocking the ability of the project to get out v20 releases. It was blocked eariler by an issue @ryanaslett resolved last week, but there is some new issue so the v20 release has been blocked for 2 weeks and the build team has been getting questions. The new issue is nodejs/build#4012. It would be great if we could get daily updates on that issue so that people in the project can see what's been done and progress being made. It's understood that problems may not be able to be fixed immediately, but in absence of that having progress info is a real help. |
@bensternthal in terms of https://github.com/openjs-foundation/cross-project-council/blob/main/project-resources/requesting_LFIT_support.md, still working out what we should do when. Is opening a JIRA as outlined in "What to do in an emergency" appropriate for nodejs/build#4012 ? |
@mhdawson The docs are up-to-date with regards to what to do in an emergency. I would say if you are unable to reach Ryan via slack or if it's not during USA working hours, Jira is appropriate. |
Opening a ticket here and marking it critical will now actually send us a slack message too |
Final provisioning and cut over
Documentation
Decommission old machines
The text was updated successfully, but these errors were encountered: