tripleo-ci/zuul.d
2018-11-01 14:07:49 +00:00
..
base.yaml Move environment_type to the new base jobs 2018-10-11 10:07:00 +00:00
build-image.yaml Add full path to required projects 2018-08-21 15:47:51 -04:00
layout.yaml Remove non-voting job from gate 2018-09-29 05:46:46 -06:00
multinode-jobs.yaml Switch scenarios to non-voting 2018-10-31 09:56:07 -06:00
nodesets.yaml Add peer and switch nodes for fedora28 2018-10-30 08:21:51 +01:00
README.rst Enable featureset override for tempest_{format, extra_override} 2018-10-14 19:29:09 +05:30
standalone-jobs.yaml Disable tempest run on tripleo-ci-fedora-28-standalone 2018-10-26 15:09:58 +05:30
undercloud-jobs.yaml Make containerized-undercloud-upgrades job non-voting 2018-10-23 15:02:05 +00:00

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

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'