ISO builds from branch that need more RAM can break all our Jenkins isobuilders without us being notified
I just had to restart the jenkins-slave service on 3 of our 4
isobuilders: it was down since yesterday because a feature/stretch build
had triggered the OOM (by the way, this hints that we need an Icinga
check that asks systemd if everything is running all-right; please add a
low prio ticket if you agree). This has the potential to essentially
kill our CI system within a few days, hence high priority.
Related issues
- Related to #11858 (closed)
Original created by @intrigeri on 11632 (Redmine)