Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Adjust free space threshold for jenkins and allow it to bring machines offline

Aperta
  • Qualcosa non va?
#4,536 5 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 4 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
48/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
yaml
Ambito
ci-cd, infrastructure

Direzione di ricerca

Start by locating the Jenkins configuration that sets the workspace free-space warning threshold and controls whether low-space agents are taken offline; the issue does not name the file. Review how the current 0.2GB setting is applied, then determine how to set the threshold to roughly 4–5GB and enable taking agents offline. Done when the policy prevents builds from being scheduled on agents below the chosen threshold.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

build-agenda jenkins

Jenkins has the option to mark machines offline if the workspace space gets too low. At the moment we hae the warning threshold set to 0.2G of space (i.e. when it gets below that it will warn, but not take the machine offline).

I think we should be more aggressive with this and set it to a larger figure (At least 2GB but ideally 4-5GB which would usually cover one full build on most systems) and allow jenkins to take machines offline when they hit the threshold which should prevent out of space conditions.

At the time of writing having a policy of "offline at 5GB" would take out the following executors, including the IBM Cloud RHEL ones which we raised a separate issue for.

Since I have the page up on my screen just now I'll add a note that the following systems have between 5GB and 10GB free:

In recent months we have had quite a lot of issues relating to systems going low on disk space and while taking the machines offline prevents things being scheduled on them and therefore potentially causing queue backlogs (which is why we usually have redundancy across systems for each build type) that is probably preferable to having CI builds fail so I propropose we allow jenkins to take machines in that state machines offline.

Richard has looked at single points of failures in our critical servers under https://github.com/nodejs/build/issues/4498 but we should perhaps take a closer look at our regular agents, not least because we hit a situation today where the only two agents that could run one particuar build were on separate containers on a single physical host and therefore were impacted simultaneously: https://github.com/nodejs/build/issues/4534

Lingua principale
Jinja
Stelle
544
Fork
184
Merge medio
5g 40m
PR unite (30g)
11

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di nodejs/build

Tutte le issue di nodejs/build

Issue simili

Altre issue su DevOps

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.