Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

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

Offen
  • Stimmt etwas nicht?
#4,536 5 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 3 Tagen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
48/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
yaml
Bereich
ci-cd, infrastructure

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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

Vorherrschende Sprache
Jinja
Sterne
544
Forks
184
Ø Merge
4 T. 16 Std.
Gemergte PRs (30 T.)
12

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus nodejs/build

Alle Issues in nodejs/build

Ähnliche Issues

Weitere Issues zu DevOps

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.