CI for the TripleO project
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
Zuul 5e5e7868d4 Merge "Added standalone-full-tempest-api & -scenario -options jobs" 2 weeks ago
..
README.rst Update README to new rolevar for run-temepst role 1 year ago
ansible.yaml Create tripleo-ansible-role-job template for ansible projects. 4 years ago
base-upstream.yaml Adds compose-repos pre playbook on base jobs 3 months ago
base.yaml Use undercloud base parent in undercloud upgrade job 2 months ago
build-containers.yaml Ussuri tear down as EOL 1 month ago
build-image.yaml Ussuri tear down as EOL 1 month ago
content-provider.yaml Ussuri tear down as EOL 1 month ago
deprecated-jobs.yaml Ussuri tear down as EOL 1 month ago
layout.yaml Enable tripleo-ceph-periodic run for tripleo-ci project 3 months ago
multinode-jobs.yaml Ussuri tear down as EOL 1 month ago
nodesets.yaml Use nested-virt nodeset for c9 scenario010 5 months ago
periodic.yaml Add ussuri content provider back to upstream periodic layout 1 month ago
standalone-jobs.yaml Merge "Added standalone-full-tempest-api & -scenario -options jobs" 2 weeks ago
undercloud-jobs.yaml Ussuri tear down as EOL 1 month ago
upgrades-jobs-templates.yaml Add back ussuri content-provider for V upgradejobs 1 month ago

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_exclude_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_exclude_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'