offline_nodes 1.08 KB
Newer Older
1 2 3
# The hosts listed below are known to be down atm.
# No builds will be dispatched to those nodes, and the nodes will be marked
# as offline in the jenkins UI.
4 5 6 7 8 9 10 11 12 13 14 15
#
# The code greps for the local hostname, i.e.
# foobar-armhf-rb
# codethink-sled23-arm64
# profitbricks-build42-amd64
#
# (name coming from the basename of the workspace directory for start-agent.sh
# and from the list in reproducible_build_service.sh for reproducible_worker.sh)
#
# This means one could specify either the FQDN or the local hostname, bearing
# in mind the FQDN will always match, whereas the shorter variant may stop
# working.
16

17

18 19
# Also see https://pad.sfconservancy.org/p/rb-build-nodes-keep

Mattia Rizzolo's avatar
Mattia Rizzolo committed
20 21
# host stuck somewhere, will need vagrant to poke physically
jtx1b-armhf-rb.debian.net
22 23
# i/o errors and reset is not doing anything.  vagrant will need to push the btn
bbx15-armhf-rb.debian.net
24 25
# keeps crashing, disabled until vagrant can look at it.
opi2b-armhf-rb.debian.net
Mattia Rizzolo's avatar
Mattia Rizzolo committed
26

27
## temporary problems
28 29 30

# Down here nodes are automtically added by the maintenance job when they have
# been failing their health check for too long.