openstack
/
tripleo-ci
Code Issues Proposed changes
tripleo-ci/zuul.d
History
Bhagyashri Shewale 46d1aa9c5c Don't allow to run train on centos7 
This change will not allow to run the train on centos7.

Here we are going to migrate upstream stable/train jobs
from CentOS-7 to CentOS-8 [1] is close.
CentOS-7 stable/train will continue to be tested in our
3rd party periodic pipeline and builds of CentOS-7
stable/train will be qualified here [2][3].

Also we are keeping c7 multinode containers job to
maintain c7 coverage.

[1]: https://review.opendev.org/#/c/738375
[2]: https://review.rdoproject.org/zuul/builds?pipeline=openstack-periodic-integration-stable2-centos7
[3]: http://lists.openstack.org/pipermail/openstack-discuss/2020-July/016157.html

Change-Id: I9f274c3866b214373c3562b0d6b480d15df1ce37
Signed-off-by: Bhagyashri Shewale <bshewale@redhat.com>
 		2020-07-31 16:01:41 +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 Add tripleo-ansible to required projects in all jobs 2020-07-03 23:06:35 +00:00
build-containers.yaml Include train for Centos8 Jobs 2020-07-30 10:03:16 +05:30
build-image.yaml Include train for Centos8 Jobs 2020-07-30 10:03:16 +05:30
deprecated-jobs.yaml Deprecate centos 7 train jobs 2020-07-31 16:00:13 +05:30
layout.yaml Merge "Move job python." 2020-07-28 22:59:15 +00:00
multinode-jobs.yaml Don't allow to run train on centos7 2020-07-31 16:01:41 +05:30
nodesets.yaml Add base centos 8 jobs for parenting 2020-02-26 12:10:25 -05:00
periodic.yaml the standalone template and periodic are running 3 times each 2020-07-23 15:28:38 -06:00
standalone-jobs.yaml Don't allow to run train on centos7 2020-07-31 16:01:41 +05:30
undercloud-jobs.yaml Don't allow to run train on centos7 2020-07-31 16:01:41 +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'