-# 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 &
-
-
-### sfa from stable
-# xxx see above
-sleep 600
-/root/bin/lbuild-nightly.sh -f f23 -b @DATE@--f23-sfatag -e check-initscripts GITPATH=git://git.onelab.eu/sfa.git@sfa-3.1-19 &
-#/root/bin/lbuild-nightly.sh sfa-GITPATH=git://git.onelab.eu/sfa.git@master tests-GITPATH=git://git.onelab.eu/tests.git@master -f f23 -b @DATE@--f23-sfa -e check-initscripts &
-
-### older fedoras
-#/root/bin/lbuild-nightly.sh -f f18 -b @DATE@--f18 &
-### 32bits build for the yum arch patch - do not forget to protect this within a call to linux32
-#linux32 /root/bin/lbuild-nightly.sh -f f14 -p linux32 -b @DATE@--f14-32 -d onelab
+/root/bin/lbuild-nightly.sh -f f31 -b @DATE@--f31-serversideonly &
+/root/bin/lbuild-nightly.sh -f f29 -b @DATE@--f29-serversideonly &