
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
38 lines
1.0 KiB
YAML
38 lines
1.0 KiB
YAML
- job-template:
|
|
name: '{pipeline}-neutron-dsvm-functional{branch-designator}'
|
|
node: '{node}'
|
|
|
|
wrappers:
|
|
- timeout:
|
|
timeout: 125
|
|
fail: true
|
|
- timestamps
|
|
|
|
builders:
|
|
- link-logs
|
|
- devstack-checkout
|
|
- shell: |
|
|
#!/bin/bash -xe
|
|
export PYTHONUNBUFFERED=true
|
|
export DEVSTACK_GATE_TIMEOUT=120
|
|
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 {{
|
|
/opt/stack/new/devstack/unstack.sh
|
|
export OS_SUDO_TESTING=1
|
|
cd /opt/stack/new/neutron
|
|
tox -e functional
|
|
}}
|
|
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
|