Current state of Build WG owned machines
Los mantenedores suelen responder en 2 días
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 25/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Necesita aclaración
- Estado de actividad
- Activo
- Stack tecnológico
- ansible, azure, node.js
- Área
- devops, infrastructure
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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).
- Lenguaje dominante
- Jinja
- Estrellas
- 541
- Forks
- 185
- Merge medio
- 2 d 1 h
- PR fusionados (30 d)
- 10
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de nodejs/build
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
nodejs/build#4482 · 1 comentario ·
Los mantenedores suelen responder en 2 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
nodejs/build#4324 · 1 comentario ·
Los mantenedores suelen responder en 2 días
-
Is gzemnid still required?Abiertoinfra
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100
Los mantenedores suelen responder en 2 días
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
nodejs/build#4499 · 23 comentarios · 16 reacciones ·
Los mantenedores suelen responder en 2 días
-
Dificultad 4/5 3-5 días Aptitud para principiantes 52/100
nodejs/build#4497 · 4 comentarios ·
Los mantenedores suelen responder en 2 días
Todos los issues de nodejs/build
Issues similares
-
tech debt
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
TAMULib/fw-registry#543 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 80/100
ClusterLabs/fence-agents#663 ·
-
settings.py flaps between reconciles: needsMigrationSetting depends on map iteration orderPosiblemente ocupada @fontaineajulien la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
pulp/pulp-operator#1691 ·
-
[Lesson] A compatibility-gate rejection is a verdict, not something to overwrite with --accept-riskAbiertolesson-submission needs-ac pending-review
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
Ikalus1988/MisakaNet#2870 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
semaphoreci/docker-images#46 · 1 comentario ·