|
| 1 | +# Node.js Build WorkGroup Meeting 2024-10-30 |
| 2 | + |
| 3 | +## Links |
| 4 | + |
| 5 | +* **Recording**: https://www.youtube.com/watch?v=MnMWg2sIlNI |
| 6 | +* **GitHub Issue**: https://github.com/nodejs/build/issues/3942 |
| 7 | +* **Minutes Google Doc**: https://docs.google.com/document/d/1V4iwMa_fX6CWw1C3XpjjeAWQb4iHhsb2w3MmVnDpf5g/edit?tab=t.0 |
| 8 | + |
| 9 | +## Present |
| 10 | + |
| 11 | +* Build team: @nodejs/build |
| 12 | +* Abdirahim Musse @abmusse |
| 13 | +* Michael Zasso @targos |
| 14 | +* Milad Farazmand @miladfarca |
| 15 | +* Richard Lau @richardlau |
| 16 | +* Ryan Aslett @ryanaslett |
| 17 | +* Ulises Gascon @UlisesGascon |
| 18 | + |
| 19 | + |
| 20 | + |
| 21 | +## Agenda |
| 22 | + |
| 23 | +## Announcements |
| 24 | + |
| 25 | +*Extracted from **build-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. |
| 26 | + |
| 27 | +### nodejs/build |
| 28 | + |
| 29 | +* Infrastructure for Orka (2024 and beyond) [#3686](https://github.com/nodejs/build/issues/3686) |
| 30 | + * Requested 2 new nodes that are now part of the infra |
| 31 | + * CI testing will be running on these machines from now on |
| 32 | + * Next step we can decommission the old nodes |
| 33 | + * Release CI is running already in the new cluster |
| 34 | +* New Machine requirement: Replacement for Equinix x64 servers [#3597](https://github.com/nodejs/build/issues/3597) |
| 35 | + * New strategy in place for smartOS |
| 36 | + * Need to work out plan for unencrypted |
| 37 | + * Ryan is working on it now |
| 38 | +* macOS refuses to start `node` when downloaded from the tarball [#3538](https://github.com/nodejs/build/issues/3538) |
| 39 | + * No news |
| 40 | + * Ulises plan to work on it before Christmas |
| 41 | +* Discuss state of r2 migration on Build WG meeting [#3508](https://github.com/nodejs/build/issues/3508) |
| 42 | + * We had a long standing issue for a while related to the promotion of releases. |
| 43 | + * This is fixed now for future releases |
| 44 | + * The are some issues with the aws s3 client and Cloudflare’s R2 |
| 45 | + * Someone mentioned in PR that rclone might be an alternative tool |
| 46 | + * Currently we have some missing releases in R2 (WIP manual sync) |
| 47 | + * It was requested to install GH cli: https://github.com/nodejs/build/pull/3931#issuecomment-2426435390 |
| 48 | + * We reject the idea due security concerns |
| 49 | + * Currently this server is not connected to GitHub and we don’t plan to enable this communication. |
| 50 | + |
| 51 | + |
| 52 | +## Q&A, Other |
| 53 | + |
| 54 | +* Michael did the migration of the release server |
| 55 | + * The SSH configuration was solved and the backups are working again |
| 56 | +* Investigate alternative jenkins access for backups[#3939](https://github.com/nodejs/build/issues/3939) |
| 57 | + * The backups server is using a personal token for the Jenkins connection |
| 58 | + * We thinking on moving this a service account |
| 59 | + * Discussion around current service accounts |
| 60 | + * We need to check that this info is disclosed to the security WG (threat model) |
| 61 | +* 2024 Annual OSUOSL Survey (https://github.com/nodejs/build/issues/3923) |
| 62 | + * Discussion around the resources that we have there |
| 63 | + * Richard: technical info has been sent but we need to fulfill additional information (funding, CLA, etc..) |
| 64 | + * The expectation is that the foundation can manage this communications in the future |
| 65 | + * The survey will close tomorrow |
| 66 | + * Ryan will provide support on this |
| 67 | + |
| 68 | +## Upcoming Meetings |
| 69 | + |
| 70 | +* **Node.js Project Calendar**: <https://nodejs.org/calendar> |
| 71 | + |
| 72 | +Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. |
| 73 | + |
0 commit comments