Joe Gordon 7b0280fd27 run link-logs builder first
The builders are run sequentially and short circuited. So if a job fails
we used to loose the link to the logs, but a failed job is the main
reason why someone would try to access the jenkins console log directly.

Confirmed this patch hits all cases of link-logs using 'git grep -B1 link-logs'

Change-Id: I74bc87b706c13624a1b34d0a0335c3a167ff8e34
2014-03-14 15:06:44 +00:00

40 lines
1.3 KiB
YAML

- job-template:
name: '{pipeline}-swift-dsvm-functional{branch-designator}'
node: '{node}'
wrappers:
- timeout:
timeout: 95
fail: true
- timestamps
builders:
- link-logs
- devstack-checkout
- shell: |
#!/bin/bash -xe
export PYTHONUNBUFFERED=true
export DEVSTACK_GATE_TIMEOUT=90
export FUNCTEST_TIMEOUT=30
export DEVSTACK_GATE_TEMPEST=0
export DEVSTACK_GATE_EXERCISES=0
export BRANCH_OVERRIDE={branch-override}
if [ "$BRANCH_OVERRIDE" != "default" ] ; then
export OVERRIDE_ZUUL_BRANCH=$BRANCH_OVERRIDE
fi
function post_test_hook {{
cd /opt/stack/new/swift
# Launch V2 auth tests and v1 tests after.
timeout -s 9 ${{FUNCTEST_TIMEOUT}}m bash .functests --verbosity=3 && \
SWIFT_TEST_CONFIG_FILE=/opt/stack/new/swift/test/sample.conf \
timeout -s 9 ${{FUNCTEST_TIMEOUT}}m bash .functests --verbosity=3
}}
export -f post_test_hook
cp devstack-gate/devstack-vm-gate-wrap.sh ./safe-devstack-vm-gate-wrap.sh
./safe-devstack-vm-gate-wrap.sh
publishers:
- devstack-logs
- console-log