Current state of Build WG owned machines
Maintainer antworten meist innerhalb von 2 Tagen
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Anfängerfreundlichkeit
- 25/100
- Issue-Typ
- Feature
- Klarheit
- Muss geklärt werden
- Aktivitätsstatus
- Aktiv
- Tech-Stack
- ansible, azure, node.js
- Bereich
- devops, infrastructure
Rechercherichtung
Start with the host-map entry point at tools/host-map/ and run the release and test commands shown in the issue. Review the listed machines, providers, and linked issues, including the AWX reference in issue 4487. Done means the Build WG's single-provider dependencies and unclear or unused hosts have been evaluated and recorded with agreed next steps.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
Idea came out of a recent Build WG meeting to evaluate where our single points of failure are in the Build WG owned machines/providers. In the screenshots from the host-map tool the rows in green highlight where we have machines on two or more providers.
Infra
No redundancy on any of these:
Azure
- infra-azure-ubuntu2404-x64-1 aka rsync
DigitalOcean
- infra-digitalocean-ubuntu1804-x64-1 aka gzemnid. https://github.com/nodejs/build/issues/4501
- infra-digitalocean-ubuntu1804-x64-2 aka unofficial-builds. https://unofficial-builds.nodejs.org/
- infra-digitalocean-ubuntu1804-x64-3 aka metrics. Unsure if still needed.
- infra-digitalocean-ubuntu2204-x64-1 aka CI. The test Jenkins server used for testing pull requests.
- infra-digitalocean-ubuntu2204-x64-2 aka www. Staging server. Critical for releases.
IBM Cloud
- infra-ibm-ubuntu2004-x64-1 aka ansible. AWX instance, see https://github.com/nodejs/build/issues/4487.
- infra-ibm-ubuntu2404-x64-1 aka ci-release. Our Release Jenkins server. Critical for releases.
- infra-mnx-ubuntu2204-x64-1 aka backup-2.
- infra-softlayer-debian8-x64-1 aka registry-mirror. I have no idea what this is. It also doesn't appear to exist in our IBM Cloud account -- maybe it was deleted but not removed from the inventory? https://github.com/nodejs/build/pull/4500
Rackspace
- infra-rackspace-debian12-x64-1 aka gh-bot. This is the server for https://github.com/nodejs/github-bot and used to bridge between Jenkins and GitHub (CI runs to PR status checks).
Release
node tools/host-map/ release
- AIX and Linux x64 are the only platforms we have redundancy for. All other platforms are dependent on a single provider.
- Although for x64 we run two jobs (rhel8/9-x64-release and rhel8/9-release-sources) so the two machines help run those in parallel.
- Although ubuntu2404_docker-x64 looks like we have redundancy, we're actually running different containers on the two hosts
- alpine container on the IBM host
- cross compilers for armv7 (only for Node.js 22) on the mnx host
- ibmi and zos machines are unused (we don't currently release on those platforms) but are hosted at providers specific to those platforms (so not taking anything away potentially from the other platforms).
Test
node tools/host-map/ test
- For Linux x64 we're reliant on DigitalOcean and IBM Cloud, although some of the platforms are not offered as options on IBM Cloud so we're reliant on DO (e.g. Debian 13, the Fedoras).
- Vorherrschende Sprache
- Jinja
- Sterne
- 542
- Forks
- 184
- Ø Merge
- 2 T. 23 Std.
- Gemergte PRs (30 T.)
- 11
Entwicklungsumgebung
- Kein Dockerfile und keine Docker-Compose-Datei
- Keine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus nodejs/build
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 70/100
nodejs/build#4482 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 2 Tagen
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
nodejs/build#4324 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 2 Tagen
-
Schwierigkeit 4/5 Über eine Woche Anfängerfreundlichkeit 5/100
Maintainer antworten meist innerhalb von 2 Tagen
-
Update to clang 21Offenbuild-agenda
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 25/100
nodejs/build#4509 · 2 Kommentare ·
Maintainer antworten meist innerhalb von 2 Tagen
-
incident
Schwierigkeit 4/5 1-2 Tage Anfängerfreundlichkeit 22/100
nodejs/build#4507 · 6 Kommentare ·
Maintainer antworten meist innerhalb von 2 Tagen
Ähnliche Issues
-
bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
mishraprafful/multihull#147 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
paperclipai/paperclip#15751 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 65/100
Maintainer antworten meist innerhalb von 1 Tag
-
bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 75/100
Maintainer antworten meist innerhalb von 1 Tag
-
good first issue need help packaging
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 66/100
phonology024/babelscribe#23 ·