Move legacy-swift-dsvm-functional job in-tree
Note that there's no swift-dsvm-functional-identity-v3-only because as of the Queens release, that's the *only* way Keystone gets deployed. Change-Id: I49d963b98f3df21fea0db24c83553ef873ad73c8
This commit is contained in:
4 changed files with 67 additions and 0 deletions
4
tools/playbooks/dsvm/post.yaml
Normal file
4
tools/playbooks/dsvm/post.yaml
Normal file
@@ -0,0 +1,4 @@
- hosts:all
roles:
- fetch-tox-output
- fetch-subunit-output
9
tools/playbooks/dsvm/pre.yaml
Normal file
9
tools/playbooks/dsvm/pre.yaml
Normal file
@@ -0,0 +1,9 @@
- hosts:all
roles:
- orchestrate-devstack
# Run bindep and test-setup after devstack so that they won't interfere
- role:bindep
bindep_profile:test
bindep_dir:"{{ zuul_work_dir }}"
- test-setup
- ensure-tox
11
tools/playbooks/dsvm/run.yaml
Normal file
11
tools/playbooks/dsvm/run.yaml
Normal file
@@ -0,0 +1,11 @@
- hosts:all
tasks:
- name:Run func tests with Keystone users
include_role:
name:tox
- name:Run func tests with tempauth users
include_role:
name:tox
vars:
tox_environment:
SWIFT_TEST_CONFIG_FILE:test/sample.conf
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.