simpler

[infrastructure.git] / scripts / builds.sh

diff --git a/scripts/builds.sh b/scripts/builds.sh
index 314d0d3..3f2f9be 100755 (executable)
--- a/scripts/builds.sh
+++ b/scripts/builds.sh
@@ -3,53 +3,40 @@
 # tentatively trash all qemu instances as the pool is broken with threesome tests
 manage-infrastructure.py -qrs >& /dev/null
 
+# test the 32 builds with a single plc, tests tend to fail with a triangle setup
+# probably due to 32bits qemu machines being much slower
+# another approach would be to increase the ssh_slice timeout
+
 function liquid () { hostname | grep -q liquid ; }
 function reed () { hostname | grep -q reed ; }
 function velvet () { hostname | grep -q velvet ; }
 
 # the tests flavours available
 # -B means no test
-# default is one myplc
+# default for the tests setup is one myplc
 # -c dual has two myplc's - pointing to each other AMs
 # -c triangle has three - ditto
 # -c sfamesh makes them point to SMs
 
-# 2.6.22 kernel on f8
-#liquid && /root/bin/vbuild-nightly.sh -m build@onelab.eu   -d onelab -t onelab-k22-tags.mk -f f8 -p linux32 -b @DATE@--k22-f8-32
-liquid && /root/bin/vbuild-nightly.sh -m build@onelab.eu   -d onelab -t onelab-k22-tags.mk -f f8 -p linux64 -b @DATE@--k22-f8-64 
+# 2.6.27 kernel on f8
+liquid && /root/bin/vbuild-nightly.sh -m build@onelab.eu   -d onelab -t onelab-k32-tags.mk -f f8 -p linux64 -b @DATE@--f8-64 -c triangle -c sfamesh
+liquid && /root/bin/vbuild-nightly.sh -m build@onelab.eu   -d onelab -t onelab-k32-tags.mk -f f8 -p linux32 -b @DATE@--f8-32-sfagen sfa-GITPATH=git://git.f-lab.fr/sfa.git@generic
+# 2.6.32 kernel on f15 is broken
+# liquid && /root/bin/vbuild-nightly.sh -m build@onelab.eu   -d onelab -t onelab-k32-tags.mk -f f15 -p linux64 -b @DATE@--f15-64 -B
 
 # 2.6.27 kernel on f12
-#reed && /root/bin/vbuild-nightly.sh -m build@onelab.eu   -d onelab -t onelab-k27-tags.mk -f f12 -p linux32 -b @DATE@--k27-f12-32 
-reed && /root/bin/vbuild-nightly.sh -m build@onelab.eu   -d onelab -t onelab-k27-tags.mk -f f12 -p linux64 -b @DATE@--k27-f12-64
-# 2.6.32 kernel on f12
-reed && /root/bin/vbuild-nightly.sh -m build@onelab.eu   -d onelab -t onelab-k32-tags.mk -f f12 -p linux64 -b @DATE@--k32-f12-64
+reed && /root/bin/vbuild-nightly.sh -m build@onelab.eu   -d onelab -t onelab-k32-tags.mk -f f12 -p linux64 -b @DATE@--f12-64 -c triangle -c sfamesh
+reed && /root/bin/vbuild-nightly.sh -m build@onelab.eu   -d onelab -t onelab-k32-tags.mk -f f12 -p linux32 -b @DATE@--f12-32-sfasl sfa-GITPATH=git://git.f-lab.fr/sfa.git@senslab
 
-# f14 - ongoing work - needs 2.6.32
-# sfamesh currently does not finish with no antiloop; triangle hangs in sfi remove -t user
-#velvet && /root/bin/vbuild-nightly.sh -m build@onelab.eu   -d onelab -t onelab-k32-tags.mk -f f14 -p linux32 -b @DATE@--k32-f14-32 
-velvet && /root/bin/vbuild-nightly.sh -m build@onelab.eu   -d onelab -t onelab-k32-tags.mk -f f14 -p linux64 -b @DATE@--k32-f14-64 -c triangle -c sfamesh
+# f14 - needs 2.6.32
+#velvet && /root/bin/vbuild-nightly.sh -m build@onelab.eu   -d onelab -t onelab-k32-tags.mk -f f14 -p linux64 -b @DATE@--f14-64 -c triangle -c sfamesh
+velvet && /root/bin/vbuild-nightly.sh -m build@onelab.eu   -d onelab -t onelab-k32-tags.mk -f f14 -p linux64 -b @DATE@--f14-64
+velvet && /root/bin/vbuild-nightly.sh -m build@onelab.eu   -d onelab -t onelab-k32-tags.mk -f f14 -p linux32 -b @DATE@--f14-32-testtag tests-GITPATH=git://git.onelab.eu/tests.git@tests-5.0-29
 
 # wextoolbox on f14 (gnuradio is in f14 only)
 #reed && /root/bin/vbuild-nightly.sh -m build@onelab.eu -d wextoolbox -p linux32 -f f14 -b @DATE@--wtx-f14-32
 #liquid && /root/bin/vbuild-nightly.sh -m build@onelab.eu -d wextoolbox -p linux64 -f f14 -b @DATE@--wtx-f14-64
 
-##############################
-#### 2.6.22 kernel on f12 - known to be broken, node won't fly
-####liquid && /root/bin/vbuild-nightly.sh -m build@onelab.eu   -d onelab -t onelab-k22-tags.mk -f f12 -p linux32 -b @DATE@--k22-f12-32
-####liquid && /root/bin/vbuild-nightly.sh -m build@onelab.eu   -d onelab -t onelab-k22-tags.mk -f f12 -p linux64 -b @DATE@--k22-f12-64 -B
-
-# 2.6.27 kernel on f8
-#reed && /root/bin/vbuild-nightly.sh -m build@onelab.eu   -d onelab -t onelab-k27-tags.mk -f f8 -p linux32 -b @DATE@--k27-f8-32
-#reed && /root/bin/vbuild-nightly.sh -m build@onelab.eu   -d onelab -t onelab-k27-tags.mk -f f8 -p linux64 -b @DATE@--k27-f8-64 -B
-
-#### 2.6.27 kernel on c5 - is there anyone using this ?
-####velvet && /root/bin/vbuild-nightly.sh -m build@onelab.eu   -d onelab -t onelab-k27-tags.mk -f centos5 -p linux32 -b @DATE@--k27-c55-32 -B
-####velvet && /root/bin/vbuild-nightly.sh -m build@onelab.eu   -d onelab -t onelab-k27-tags.mk -f centos5 -p linux64 -b @DATE@--k27-c55-64 -B
-
-# 2.6.22 kernel on c5
-#velvet && /root/bin/vbuild-nightly.sh -m build@onelab.eu   -d onelab -t onelab-k22-tags.mk -f centos5 -p linux32 -b @DATE@--k22-c55-32 
-#velvet && /root/bin/vbuild-nightly.sh -m build@onelab.eu   -d onelab -t onelab-k22-tags.mk -f centos5 -p linux64 -b @DATE@--k22-c55-64 -B
-
 ########################################
 ########## f12 bootstrap : vserver-capa2.6.32, util-vserver and yum, for a plain fedora 12 build or test box
 ########## enable on a need-by-need basis