tripleo-ci/zuul.d
Marios Andreou 74be796580 Adds tripleo-repos/-operator-ansible collection push jobs
In [1] a release job was added for tripleo-operator. Now we need
to add the same for the tripleo-repos collection. This proposes
we move the playbook, secret and job definition to here so that
both jobs can share them. Then the jobs can be wired up into their
respective repo zuul layout files.

Once we are happy with testing (this needs to merge so we can test)
we can merge [2] and remove the duplication in t-o-a.

[1] https://review.opendev.org/c/openstack/tripleo-operator-ansible/+/803588
[2] https://review.opendev.org/c/openstack/tripleo-operator-ansible/+/810259
Change-Id: I09b24c4782db2e7cad117fb98a70a1c3d36a4301
2021-10-11 10:08:49 +00:00
..
README.rst Update README to new rolevar for run-temepst role 2021-02-11 13:42:27 -06:00
ansible-galaxy.yaml Adds tripleo-repos/-operator-ansible collection push jobs 2021-10-11 10:08:49 +00:00
ansible.yaml Create tripleo-ansible-role-job template for ansible projects. 2018-11-27 17:22:59 +01:00
base.yaml move scenario010 to branched jobs for voting 2021-07-26 06:54:51 -04:00
build-containers.yaml Enable supported container-tools before login 2021-08-31 15:01:45 -04:00
build-image.yaml Remove overcloud-hardened-full jobs after victoria 2021-08-24 13:21:22 +12:00
content-provider.yaml add tripleo-common checkout to content-provider 2021-08-18 10:54:11 -06:00
deprecated-jobs.yaml Remove jobs that uses obselete fs b/w 31 - 99 2021-09-16 12:07:38 +00:00
layout.yaml Make standalone-ipa jobs voting again - minus train 2021-06-23 11:59:50 +00:00
multinode-jobs.yaml Merge "Remove jobs that uses obselete fs b/w 31 - 99" 2021-09-22 14:52:27 +00:00
nodesets.yaml Remove unused c8s nodesets 2021-08-09 02:08:09 +09:00
periodic.yaml Rename the upstream upgrades templates so we can run only once 2021-08-02 16:40:30 +00:00
standalone-jobs.yaml Merge "Add scenario001/004 coverage to image uploader changes" 2021-10-07 19:41:09 +00:00
undercloud-jobs.yaml Merge "Remove all rocky related jobs/conditionals tests after rocky End of Life" 2021-04-07 02:55:43 +00:00
upgrades-jobs-templates.yaml Merge "Donot trigger undercloud upgrade jobs on standalone fs" 2021-09-11 02:20:29 +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_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'