use minimal to verify ping/tempest

The minimal config is only used outside of the upstream CI
system.  We cover both ping and tempest upstream but not
across all the releases.  Let's use minimal.yml as the
config that should work across rleases to verify that
both ping and tempest are working correctly from a
CI standpoint.

Change-Id: I23cb01a5f753214897a0e59b4adc45e910fb3cf3
This commit is contained in:
Wes Hayutin 2018-04-02 12:36:41 -04:00 committed by wes hayutin
parent 4ab8b78276
commit ed99f54fb7
1 changed files with 6 additions and 16 deletions

View File

@ -71,23 +71,13 @@ artcl_create_docs_payload:
# Use the traditional ping test in newton, ocata and pike # Use the traditional ping test in newton, ocata and pike
# Run tempest in queens+ # Run tempest in queens+
test_ping: >- # always run the ping test
{% if release in ['newton', 'ocata', 'pike'] -%} test_ping: true
true
{%- else -%}
false
{%- endif -%}
run_tempest: >- # looking for a small set of tempest tests to validate
{% if release in ['newton', 'ocata', 'pike'] -%} # tempest config and execution are working
false run_tempest: true
{%- else -%} test_regex: 'tempest.api.compute.admin'
true
{%- endif -%}
test_regex: ''
tempest_whitelist:
- 'tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.test_network_basic_ops'
deploy_steps_ansible_workflow: >- deploy_steps_ansible_workflow: >-
{% if release not in ['newton','ocata','pike'] -%} {% if release not in ['newton','ocata','pike'] -%}