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

38 lines
1.1 KiB
YAML

- job-template:
name: '{pipeline}-sqlalchemy-migrate-devstack-dsvm{branch-designator}'
node: '{node}'
wrappers:
- timeout:
timeout: 185
fail: true
- timestamps
builders:
- link-logs
- devstack-checkout
- shell: |
#!/bin/bash -xe
export PYTHONUNBUFFERED=true
export DEVSTACK_GATE_TIMEOUT=180
export PROJECTS="stackforge/sqlalchemy-migrate $PROJECTS"
export DEVSTACK_GATE_TEMPEST=1
export DEVSTACK_GATE_TEMPEST_FULL=1
export BRANCH_OVERRIDE={branch-override}
if [ "$BRANCH_OVERRIDE" != "default" ] ; then
export OVERRIDE_ZUUL_BRANCH=$BRANCH_OVERRIDE
fi
function pre_test_hook {{
cd /opt/stack/new/sqlalchemy-migrate
sudo pip install .
}}
export -f pre_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