X-Git-Url: http://git.onelab.eu/?a=blobdiff_plain;f=scripts%2Fbuilds.sh;h=5ae430b884aa1112ecae403de8bde90e77268607;hb=4af3926b1d321f620f245fdcf2441062dbe9cef9;hp=b9cbd6ddf43ddc976fc4f6444730ee34e0298409;hpb=41253e0a5b8fa6176a555d89858058ac64e73822;p=infrastructure.git

diff --git a/scripts/builds.sh b/scripts/builds.sh
index b9cbd6d..5ae430b 100755
--- a/scripts/builds.sh
+++ b/scripts/builds.sh
@@ -20,16 +20,24 @@
 #function reed () { hostname | grep -q reed ; }
 #function buzzcocks () { hostname | grep -q buzzcocks ; }
 
-/root/bin/lbuild-nightly.sh -f f23 -b @DATE@--f23 -e check-initscripts &
+/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
-/root/bin/lbuild-nightly.sh -f f22 -b @DATE@--f22 -e check-initscripts &
+# 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 branch
+### 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-21 &
 #/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
@@ -37,7 +45,7 @@
 ### 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
 
-exit
+exit # END - for my-builds
 
 ########## oldies