-function liquid () { hostname | grep -q liquid ; }
-function reed () { hostname | grep -q reed ; }
-function velvet () { hostname | grep -q velvet ; }
+# XXX historically we had several build boxes
+#function liquid () { hostname | grep -q liquid ; }
+#function reed () { hostname | grep -q reed ; }
+#function buzzcocks () { hostname | grep -q buzzcocks ; }
+
+/root/bin/lbuild-nightly.sh -f f24 -b @DATE@--f24 -e check-initscripts &
+#/root/bin/lbuild-nightly.sh -f f23 -b @DATE@--f23 -e check-initscripts &
+
+[ -n "$SINGLE" ] && exit
+# xxx when running 3 builds of 22, 23 and 23-sfataga in parallel, I observe that
+# they all 3 trigger the tests at the exact same time, which runs into a bug of libvirt
+# might go away once we upgrade buzzcocks to f23 ?
+#sleep 600
+#/root/bin/lbuild-nightly.sh -f f22 -b @DATE@--f22 -e check-initscripts &
+#/root/bin/lbuild-nightly.sh -f f14 -b @DATE@--f14 -d onelab &
+#/root/bin/lbuild-nightly.sh -f f21 -b @DATE@--f21 -e check-initscripts &
+#/root/bin/lbuild-nightly.sh -f f20 -b @DATE@--f20 -e check-initscripts &
+