Browse Source

Add stestr master job

Tempest use stestr to run the tests, adding
a experimental and periodic job to run Tempest
with stestr master will help to detect any
breaking change in advance.

Change-Id: Ice57e193c5150be7141e0e003be5091a191b854c
changes/58/764058/4
Ghanshyam Mann 10 months ago
parent
commit
83d13e509b
  1. 12
      tox.ini
  2. 2
      zuul.d/project.yaml
  3. 16
      zuul.d/tempest-specific.yaml

12
tox.ini

@ -409,3 +409,15 @@ commands = bindep test
allowlist_externals = bash
commands =
bash tools/tempest-plugin-sanity.sh
[testenv:stestr-master]
envdir = .tox/tempest
sitepackages = {[tempestenv]sitepackages}
basepython = {[tempestenv]basepython}
setenv = {[tempestenv]setenv}
deps = {[tempestenv]deps}
# The below command install stestr master version and run smoke tests
commands =
find . -type f -name "*.pyc" -delete
pip install -U git+https://github.com/mtreinish/stestr
tempest run --regex '\[.*\bsmoke\b.*\]' {posargs}

2
zuul.d/project.yaml

@ -109,6 +109,7 @@
irrelevant-files: *tempest-irrelevant-files
experimental:
jobs:
- tempest-stestr-master
- tempest-cinder-v2-api:
irrelevant-files: *tempest-irrelevant-files
- tempest-all:
@ -133,3 +134,4 @@
jobs:
- tempest-all
- tempest-full-oslo-master
- tempest-stestr-master

16
zuul.d/tempest-specific.yaml

@ -113,3 +113,19 @@
vars:
devstack_localrc:
TEMPEST_HAS_ADMIN: False
- job:
name: tempest-stestr-master
parent: devstack-tempest
description: |
Smoke integration test with stestr master.
This ensures that new stestr release does
not break Temepst.
vars:
tox_envlist: stestr-master
devstack_services:
s-account: false
s-container: false
s-object: false
s-proxy: false
c-bak: false

Loading…
Cancel
Save