Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

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

Ouverte
  • Quelque chose ne va pas ?
#4,536 5 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 3 jours

Personne n'a encore pris cette issue.

Évaluation

Difficulté
3/5
Temps estimé
1-2 jours
Accessibilité débutants
48/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
yaml
Domaine
ci-cd, infrastructure

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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

Langage dominant
Jinja
Étoiles
544
Forks
184
Merge moyen
4 j 16 h
PR mergées (30 j)
12

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de nodejs/build

Toutes les issues de nodejs/build

Issues similaires

Plus d'issues DevOps

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.