From f191051fa739a9065364a931f23c59568ab91097 Mon Sep 17 00:00:00 2001 From: wtripp180901 Date: Fri, 17 Jan 2025 15:55:13 +0000 Subject: [PATCH] reverted out of scope doc changes --- doc/source/contributor/testing-ci-automation.rst | 6 +++--- .../notes/stackhpc-openstack-tests-0224908453ae72cc.yaml | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/source/contributor/testing-ci-automation.rst b/doc/source/contributor/testing-ci-automation.rst index 219744757..fef94e4ae 100644 --- a/doc/source/contributor/testing-ci-automation.rst +++ b/doc/source/contributor/testing-ci-automation.rst @@ -123,7 +123,7 @@ The workflow performs the following high-level steps: #. If this is an upgrade job, upgrade the cloud under test to the target release. #. Run Tempest and `StackHPC OpenStack Tests - `_ to test the cloud. + `_ to test the cloud. #. Collect diagnostic information. #. Upload results as an artifact. #. Destroy the VM using Terraform. @@ -346,11 +346,11 @@ The workflow performs the following high-level steps: #. Register test resources in the cloud under test (images, flavors, networks, subnets, routers, etc.). #. Run Tempest and `StackHPC OpenStack Tests - `__ to test the cloud. + `__ to test the cloud. #. If this is an upgrade job, upgrade the cloud under test to the target release. #. Run Tempest and `StackHPC OpenStack Tests - `__ to test the cloud. + `__ to test the cloud. #. Collect diagnostic information. #. Upload results as an artifact. #. Destroy the VMs using Terraform. diff --git a/releasenotes/notes/stackhpc-openstack-tests-0224908453ae72cc.yaml b/releasenotes/notes/stackhpc-openstack-tests-0224908453ae72cc.yaml index c2a72184d..eb3c21266 100644 --- a/releasenotes/notes/stackhpc-openstack-tests-0224908453ae72cc.yaml +++ b/releasenotes/notes/stackhpc-openstack-tests-0224908453ae72cc.yaml @@ -3,6 +3,6 @@ features: - | Adds a new ``stackhpc-openstack-tests.yml`` playbook that executes tests in the `StackHPC OpenStack Tests - `__ repository. Both + `__ repository. Both the playbook and tests are currently experimental, and are currently targeting only an all-in-one CI use case.