tripleo-ci/zuul.d
yatinkarel 318df84d54 Update molecule image defaults to centos8
Also update irrelevant-files for standalone/multinode
so these jobs don't get triggered on tripleo-repos role changes
as that role is not used in these jobs.

Closes-Bug: #1908328
Change-Id: Id0770af88bf7d4c0af165a06242f044eac7304ac
2020-12-17 11:16:49 +05:30
..
README.rst Add tempest_workers to featureset_overrides 2018-12-10 11:48:59 +00:00
ansible.yaml Create tripleo-ansible-role-job template for ansible projects. 2018-11-27 17:22:59 +01:00
base.yaml Remove lower-constraints.txt from irrelevant files 2020-12-10 21:30:51 +00:00
build-containers.yaml exclude ussuri, tested via content-provider 2020-12-12 14:02:26 -07:00
build-image.yaml buildimage-overcloud-hardened NV, kernel and nodepool image are not in sync 2020-12-09 13:42:52 -07:00
content-provider.yaml Add job definition for victoria content-provider 2020-11-02 11:49:51 +02:00
deprecated-jobs.yaml Deprecate centos 7 train jobs 2020-07-31 16:00:13 +05:30
layout.yaml Switch to content provider jobs/templates 2020-11-01 17:52:11 -05:00
multinode-jobs.yaml Update molecule image defaults to centos8 2020-12-17 11:16:49 +05:30
nodesets.yaml Don't install br-ex on standalone 2020-10-13 17:31:27 +00:00
periodic.yaml Fix variables for upstream periodic jobs 2020-11-10 15:14:01 +02:00
standalone-jobs.yaml Assure lower-constraints.txt do not trigger any deployments 2020-12-09 12:07:47 +00:00
undercloud-jobs.yaml Update molecule image defaults to centos8 2020-12-17 11:16:49 +05:30

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.
  • `test_white_regex`: Regex to be used by tempest
  • `tempest_workers`: Numbers of parallel workers to run

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_workers: 1
        tempest_plugins:
          - 'python-keystone-tests-tempest'
          - 'python-cinder-tests-tempest'
        standalone_environment_files:
          - 'environments/low-memory-usage.yaml'
          - 'ci/environments/scenario003-standalone.yaml'