8cb2ede7d4
scenario003-standalone job overrides a custom env file on standalone_environment_files parameter. Change-Id: I2d6955cedcecbe679f37ab064502668aebddb273 Story: https://tree.taiga.io/project/tripleo-ci-board/us/338 |
||
---|---|---|
.. | ||
README.rst | ||
base.yaml | ||
build-containers.yaml | ||
build-image.yaml | ||
layout.yaml | ||
multinode-jobs.yaml | ||
nodesets.yaml | ||
standalone-jobs.yaml | ||
undercloud-jobs.yaml |
README.rst
Override config
featureset override
Take advantage of zuul job config to override featureset settings like tempest tests that should run. The following settings from the featureset config can be overriden:
- `run_tempest`: To run tempest or not (true|false).
- `tempest_whitelist`: List of tests you want to be executed.
- `test_black_regex`: Set of tempest tests to skip.
- `tempest_format`: Installing tempest from venv, packages or containers
- `tempest_extra_config`: A dict values in order to override the tempest.conf
- `tempest_plugins`: List of tempest plugins needs to be installed
- `standalone_environment_files`: List of environment files to be overriden by the featureset configuration on standalone deployment. The environment file should exist in tripleo-heat-templates repo.
Example:
- job:
name: tripleo-ci-centos-7-scenario001-multinode-oooq-container
parent: tripleo-ci-multinode
...
vars:
featureset_override:
run_tempest: true
tempest_whitelist:
- 'tempest.scenario.test_volume_boot_pattern.TestVolumeBootPattern.test_volume_boot_pattern'
tempest_black_regex: 'tempest.api.network|tempest.api.compute'
tempest_format: 'containers'
tempest_extra_config: {'telemetry.alarm_granularity': '60'}
tempest_plugins:
- 'python-keystone-tests-tempest'
- 'python-cinder-tests-tempest'
standalone_environment_files:
- 'environments/low-memory-usage.yaml'
- 'ci/environments/scenario003-standalone.yaml'