Project

General

Profile

Actions

action #163232

closed

coordination #152769: [epic] Reduction of yaml files in YaST installations

Reduce yaml files for crypt{_no_,}lvm for powerVM

Added by JERiveraMoya 6 months ago. Updated 6 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
-
Start date:
2024-01-04
Due date:
% Done:

0%

Estimated time:

Description

Motivation

See epic and tickets in the epic for best practices.
This is a follow-up of #155869 and #155872 to unify with PowerVM.

Some general summary as a hint (after reading previous tickets):
Main goals are to reduce for single test suite to single yaml file comparing the ones created per each architecture before and drive the schedule having different yaml default files per each architecture. The final yaml should be stored in a folder where we have the representation of each test case: schedule/yam/test_cases
In order to do that you have to consider if it is just about yaml or would require some code changes to make things more homogeneous, there are multiple approaches ranging from simple dropping small tested functionality in some specific architecture to some more fancy code strategy.
At the same time we should care of variables, basically moving all of them to job group yaml.

Specific from this test suite:
None, should be straightforward.
Schedules for this test suite exists in schedule/yast/encryption/.

Acceptance criteria

AC1: Reduce yaml files for corresponding test suite over all the architectures
AC2: Clean-up unused files.

Actions #1

Updated by JERiveraMoya 6 months ago

  • Subject changed from Reduce yaml files for crypt_no_lvm for powerVM to Reduce yaml files for crypt{_no_,}lvm for powerVM
  • Description updated (diff)
Actions #2

Updated by hjluo 6 months ago

  • Status changed from Workable to In Progress
  • Assignee set to hjluo
Actions #3

Updated by hjluo 6 months ago

  • this ticket is focus on crypt_no_lvm and cryptlvm on ppc64le
Actions #5

Updated by hjluo 6 months ago

  • PR and MR were merged.
Actions #6

Updated by hjluo 6 months ago

  • Status changed from In Progress to Resolved
  • Mark it as resolved.
Actions

Also available in: Atom PDF