7b0280fd27
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
40 lines
1.0 KiB
YAML
40 lines
1.0 KiB
YAML
- job:
|
|
name: gate-barbican-devstack-dsvm
|
|
node: devstack-precise
|
|
|
|
wrappers:
|
|
- timeout:
|
|
timeout: 65
|
|
fail: true
|
|
- timestamps
|
|
|
|
builders:
|
|
- link-logs
|
|
- devstack-checkout
|
|
- shell: |
|
|
#!/bin/bash -xe
|
|
export PYTHONUNBUFFERED=true
|
|
export DEVSTACK_GATE_TIMEOUT=60
|
|
export ENABLED_SERVICES=barbican,tempest,keystone
|
|
export PROJECTS="stackforge/barbican $PROJECTS"
|
|
export PROJECTS="stackforge/python-barbicanclient $PROJECTS"
|
|
|
|
function pre_test_hook {
|
|
cd /opt/stack/new/barbican/functionaltests
|
|
./pre_test_hook.sh
|
|
}
|
|
export -f pre_test_hook
|
|
|
|
function post_test_hook {
|
|
cd /opt/stack/new/barbican/functionaltests
|
|
./post_test_hook.sh
|
|
}
|
|
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
|