3 function liquid () { hostname | grep -q liquid ; }
4 function reed () { hostname | grep -q reed ; }
5 function velvet () { hostname | grep -q velvet ; }
7 # 2.6.32 kernel on f14 - ongoing work - needs 2.6.32
8 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
9 #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-bmtag bootmanager-GITPATH=git://git.onelab.eu/bootmanager.git@bootmanager-5.0-12
10 # one is enough for now
11 #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
13 # 2.6.27 kernel on f12
14 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
15 #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
17 #### 2.6.22 kernel on f12 - known to be broken, node won't fly
18 ####liquid && /root/bin/vbuild-nightly.sh -m build@onelab.eu -d onelab -f f12 -p linux32 -b @DATE@--k22-f12-32
19 ####liquid && /root/bin/vbuild-nightly.sh -m build@onelab.eu -d onelab -f f12 -p linux64 -b @DATE@--k22-f12-64 -B
22 reed && /root/bin/vbuild-nightly.sh -m build@onelab.eu -d onelab -f f8 -p linux32 -b @DATE@--k22-f8-32 # -c dual
23 #reed && /root/bin/vbuild-nightly.sh -m build@onelab.eu -d onelab -f f8 -p linux32 -b @DATE@--k22-f8-32-tagbm bootmanager-GITPATH=git://git.onelab.eu/bootmanager.git@bootmanager-5.0-12
24 #reed && /root/bin/vbuild-nightly.sh -m build@onelab.eu -d onelab -f f8 -p linux64 -b @DATE@--k22-f8-64 -B
27 #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
28 #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
30 #### 2.6.27 kernel on c5 - is there anyone using this ?
31 ####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
32 ####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
35 #velvet && /root/bin/vbuild-nightly.sh -m build@onelab.eu -d onelab -f centos5 -p linux32 -b @DATE@--k22-c55-32
36 #velvet && /root/bin/vbuild-nightly.sh -m build@onelab.eu -d onelab -f centos5 -p linux64 -b @DATE@--k22-c55-64 -B
39 ### turning this off during vacations
40 #liquid && /root/bin/vbuild-nightly.sh -m build@onelab.eu -d wextoolbox -p linux32 -f f12 -b @DATE@--wtx-f12-32
42 ########################################
43 ########## f12 bootstrap : vserver-capa2.6.32, util-vserver and yum, for a plain fedora 12 build or test box
44 ########## enable on a need-by-need basis
45 #liquid && /root/bin/vbuild-nightly.sh -m build@onelab.eu -d f12 -f f12 -p linux64 -b @DATE@--f12-f12-64 -B
46 # the 32bits version is not very useful
47 #### liquid && /root/bin/vbuild-nightly.sh -m build@onelab.eu -d f12 -f f12 -p linux32 -b @DATE@--f12-f12-32 -B
49 ########################################
50 ########## f10 : shouldn't be needed anymore
51 ## 2.6.27 kernel on f10
52 #velvet && /root/bin/vbuild-nightly.sh -m build@onelab.eu -d onelab -t onelab-k27-tags.mk -f f10 -p linux32 -b @DATE@--k27-f10-32 -B
53 #velvet && /root/bin/vbuild-nightly.sh -m build@onelab.eu -d onelab -t onelab-k27-tags.mk -f f10 -p linux64 -b @DATE@--k27-f10-64 -B
55 ## 2.6.22 kernel on f10
56 #velvet && /root/bin/vbuild-nightly.sh -m build@onelab.eu -d onelab -f f10 -p linux32 -b @DATE@--k22-f10-32 -B
57 #velvet && /root/bin/vbuild-nightly.sh -m build@onelab.eu -d onelab -f f10 -p linux64 -b @DATE@--k22-f10-64 -B
59 #velvet && /root/bin/vbuild-nightly.sh -m build@onelab.eu -d wextoolbox -p linux32 -f f10 -b @DATE@--wtx-f10-32 -B
61 #liquid && /root/bin/vbuild-nightly.sh -m build@onelab.eu -d wextoolbox -p linux32 -f f10 -b @DATE@--wtx-f10-32 -B