Project

General

Profile

Actions

action #159033

open

Refactor anchors for ppc64le in migration groups

Added by leli 3 months ago. Updated 3 days ago.

Status:
New
Priority:
Low
Assignee:
-
Target version:
-
Start date:
2024-04-16
Due date:
% Done:

0%

Estimated time:

Description

Motivation

We have some anchors for a set of settings but with a test suite name, we'd better rename them as a generic name while not a special test suite name.
Ex: online_sles15sp3_pscc_base-srv_all_full_spvm: &online_sles15sp3_pscc_base-srv_all_full_spvm

And some anchors are used both for SLES and SAP migration, maybe we can split it to two, so that reduce the setting in test suite.

Move definition of anchor from ppc64le.yaml to test_suite.yaml
Ex: settings: &sap_migration_offline_common_settings_ppc64le_pre
settings: &sap_migration_offline_common_settings_ppc64le

Refactor anchors then we can clean unneeded settings in test suites:
Ex: +UPGRADE_TARGET_VERSION: '15-SP6'
+YAML_SCHEDULE: ''

Acceptance criteria

AC1: Refactor anchors for ppc64le in migration groups


Related issues 1 (0 open1 closed)

Related to qe-yam - action #152873: Replace migration test suites in openQA DB/UI in migration jobs groups with anchor/alias in job group yaml definitionResolvedleli2023-12-22

Actions
Actions #1

Updated by leli 3 months ago

  • Related to action #152873: Replace migration test suites in openQA DB/UI in migration jobs groups with anchor/alias in job group yaml definition added
Actions #2

Updated by JERiveraMoya 3 days ago

we should avoid to create too many of those share settings starting by .<key> so in some point we might need to replace settings by refactoring code instead of that, in other words, this might require more thinking.

Actions #3

Updated by JERiveraMoya 3 days ago

  • Priority changed from Normal to Low
Actions

Also available in: Atom PDF