@@ -17,6 +17,11 @@ steps:
17
17
agents :
18
18
queue : " ${BUILDKITE_AGENT_META_DATA_QUEUE:-default}"
19
19
20
+ - label : ' :linux: setup taps'
21
+ commands :
22
+ - ' sudo ip tuntap add fc-test-tap${BUILDKITE_BUILD_NUMBER} mode tap user $(sudo id -u buildkite-agent)'
23
+ - ' sudo ip tuntap add fc-root-tap${BUILDKITE_BUILD_NUMBER} mode tap user $(sudo id -u buildkite-agent)'
24
+
20
25
# We use a "wait" step here, because Go's module logic freaks out when
21
26
# multiple go builds are downloading to the same cache.
22
27
- wait
@@ -31,17 +36,23 @@ steps:
31
36
- ' ln -s /var/lib/fc-ci/vmlinux.bin testdata/vmlinux'
32
37
- ' ln -s /usr/local/bin/firecracker-v0.15.0 testdata/firecracker'
33
38
- ' ln -s /usr/local/bin/jailer-v0.15.0 testdata/jailer'
34
- - ' sudo ip tuntap add fc-test-tap${BUILDKITE_BUILD_NUMBER} mode tap user $(sudo id -u buildkite-agent)'
35
39
- " DISABLE_ROOT_TESTS=true FC_TEST_TAP=fc-test-tap${BUILDKITE_BUILD_NUMBER} make test EXTRAGOARGS='-v -count=1'"
36
- - ' sudo ip tuntap del fc-test-tap${BUILDKITE_BUILD_NUMBER} mode tap'
37
40
38
41
- label : ' :hammer: root tests'
39
42
commands :
40
43
- ' ln -s /var/lib/fc-ci/vmlinux.bin testdata/vmlinux'
41
44
- ' cp /usr/local/bin/firecracker-v0.15.0 testdata/firecracker'
42
45
- ' cp /usr/local/bin/jailer-v0.15.0 testdata/jailer'
43
- - ' sudo ip tuntap add fc-root-tap${BUILDKITE_BUILD_NUMBER} mode tap user $(sudo id -u buildkite-agent)'
44
46
- " sudo FC_TEST_TAP=fc-root-tap${BUILDKITE_BUILD_NUMBER} make test EXTRAGOARGS='-v -count=1'"
45
- - ' sudo ip tuntap del fc-root-tap${BUILDKITE_BUILD_NUMBER} mode tap'
46
47
agents :
47
48
queue : " ${BUILDKITE_AGENT_META_DATA_QUEUE:-default}"
49
+
50
+ # This allows the cleanup step to always run, regardless of test failure
51
+ - wait : ~
52
+ continue_on_failure : true
53
+
54
+ - label : ' :linux: cleanup taps'
55
+ commands :
56
+ - ' sudo ip tuntap del fc-test-tap${BUILDKITE_BUILD_NUMBER} mode tap'
57
+ - ' sudo ip tuntap del fc-root-tap${BUILDKITE_BUILD_NUMBER} mode tap'
58
+
0 commit comments