oops, had turned on the f10 build instead of f12-f12

[infrastructure.git] / scripts / builds.sh

diff --git a/scripts/builds.sh b/scripts/builds.sh
index caf277e..0c6746a 100755 (executable)
--- a/scripts/builds.sh
+++ b/scripts/builds.sh
@@ -4,6 +4,11 @@ function liquid () { hostname | grep -q liquid ; }
 function reed () { hostname | grep -q reed ; }
 function velvet () { hostname | grep -q velvet ; }
 
+# 2.6.27 kernel on f14 - this fails for now - try both archs
+# try on velvet that has a hacked util-vserver 
+velvet && /root/bin/vbuild-nightly.sh -m build@onelab.eu   -d onelab -t onelab-k27-tags.mk -f f14 -p linux32 -b @DATE@--k27-f14-32
+velvet && /root/bin/vbuild-nightly.sh -m build@onelab.eu   -d onelab -t onelab-k27-tags.mk -f f14 -p linux64 -b @DATE@--k27-f14-64
+
 # 2.6.27 kernel on f12
 liquid && /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 -c dual
 #liquid && /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 -B
@@ -12,14 +17,14 @@ liquid && /root/bin/vbuild-nightly.sh -m build@onelab.eu   -d onelab -t onelab-k
 ####liquid && /root/bin/vbuild-nightly.sh -m build@onelab.eu   -d onelab -f f12 -p linux32 -b @DATE@--k22-f12-32
 ####liquid && /root/bin/vbuild-nightly.sh -m build@onelab.eu   -d onelab -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.22 kernel on f8
 reed && /root/bin/vbuild-nightly.sh -m build@onelab.eu   -d onelab -f f8 -p linux32 -b @DATE@--k22-f8-32 -c dual
 #reed && /root/bin/vbuild-nightly.sh -m build@onelab.eu   -d onelab -f f8 -p linux64 -b @DATE@--k22-f8-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
@@ -33,10 +38,11 @@ velvet && /root/bin/vbuild-nightly.sh -m build@onelab.eu   -d onelab -f centos5
 #liquid && /root/bin/vbuild-nightly.sh -m build@onelab.eu   -d wextoolbox -p linux32 -f f12 -b @DATE@--wtx-f12-32
 
 ########################################
-########## f12 bootstrap : 2.6.31, util-vserver and yum, for a plain fedora 12 build or test box
+########## 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
-########## liquid && /root/bin/vbuild-nightly.sh -m build@onelab.eu   -d f12 -f f12 -p linux64 -b @DATE@--f12-f12-64 -B
-########## liquid && /root/bin/vbuild-nightly.sh -m build@onelab.eu   -d f12 -f f12 -p linux32 -b @DATE@--f12-f12-32 -B
+liquid && /root/bin/vbuild-nightly.sh -m build@onelab.eu   -d f12 -f f12 -p linux64 -b @DATE@--f12-f12-64 -B
+# the 32bits version is not very useful
+#### liquid && /root/bin/vbuild-nightly.sh -m build@onelab.eu   -d f12 -f f12 -p linux32 -b @DATE@--f12-f12-32 -B
 
 ########################################
 ########## f10 : shouldn't be needed anymore