History

Rafael Folco 2af5efcbf7 Deprecate tripleo stable/{newton,ocata} jobs Non-containerized jobs were running for stable/newton and stable/ocata branches and are no longer supported. - Move deprecated jobs into a separate zuul config file - Reparent deprecated jobs to tripleo-ci-deprecated - Add a playbook with deprecated warning - Disable jobs with 'branches: none/deprecated' filter - Remove/disable non-containerized scenario jobs from layout - Add noop to templates with non-contrainerized jobs only * tripleo-multinode-baremetal-minimal template * tripleo-multinode-baremetal-full template - Rename (create a copy for) scen006 and scen009 with a '-container' suffix as these are containerized As tripleo-ci repo is not branched, all the projects that have these jobs in their zuul config (including all branches) will be affected. Therefore, a cleanup is required to deprecate jobs before removing them from zuul config. A follow-up change will delete the definition of deprecated jobs from zuul config, Story: https://tree.taiga.io/project/tripleo-ci-board/issue/372 Change-Id: I23df3518820d39f32d1daded33776d757c144217		2018-12-11 11:53:03 -02:00
..
README.rst	Add tempest_workers to featureset_overrides	2018-12-10 11:48:59 +00:00
base.yaml	Remove legacy tripleo-ci-dsvm* jobs	2018-12-03 12:20:46 +00:00
build-containers.yaml	TripleO Container build CI job	2018-11-06 22:51:05 +00:00
build-image.yaml	Fix build-image job parent	2018-12-06 13:05:17 +00:00
deprecated-jobs.yaml	Deprecate tripleo stable/{newton,ocata} jobs	2018-12-11 11:53:03 -02:00
layout.yaml	Deprecate tripleo stable/{newton,ocata} jobs	2018-12-11 11:53:03 -02:00
multinode-jobs.yaml	Deprecate tripleo stable/{newton,ocata} jobs	2018-12-11 11:53:03 -02:00
nodesets.yaml	Add peer and switch nodes for fedora28	2018-10-30 08:21:51 +01:00
standalone-jobs.yaml	Add new tripleo-ci-centos-7-scenario003-standalone job	2018-12-10 11:40:15 +01:00
undercloud-jobs.yaml	Revert "remove non-voting job from gate"	2018-12-07 17:52:07 +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'