tripleo-ci/zuul.d
Sorin Sbarnea e454fe143d Improve file patterns used to trigger buildcontainers
Adds patterns for kolla repository.

Adds generic patterns for sensitive files which are likely to cause
problems with any repository.

Change-Id: I621d778ee83f0df7a04ec34e9c553a73e091c2e8
2019-02-28 10:44:54 +00:00
..
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 Improve file patterns used to trigger buildcontainers 2019-02-28 10:44:54 +00:00
build-containers.yaml Create a new container build job with Buildah on centos7 2019-02-28 00:13:39 +00:00
build-image.yaml Update heat agent path for image building 2019-01-03 10:33:41 -07:00
deprecated-jobs.yaml Deprecate tripleo stable/{newton,ocata} jobs 2018-12-11 11:53:03 -02:00
layout.yaml Adding scenario012 standalone job 2019-02-19 13:41:39 +00:00
multinode-jobs.yaml Merge "Use override-checkout for stable branch jobs" 2019-02-06 18:37:52 +00:00
nodesets.yaml Adopt use of pre-commit linting 2018-12-14 15:50:06 +00:00
standalone-jobs.yaml Revert "Temporary disable scenarios 1+4 standalone for ceph bluestore" 2019-02-26 15:37:11 +00:00
undercloud-jobs.yaml Merge "undercloud upgrade should be voting" 2019-01-05 02:40:18 +00:00

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'