Project

General

Profile

Actions

action #163286

closed

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

Reduce yaml files for textmode

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

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

0%

Estimated time:

Description

Motivation

See epic and tickets in the epic for best practices.

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:
Schedules for this test suite exists in schedule/yast/textmode.

Acceptance criteria

AC1: Reduce yaml files for corresponding test suite over all the architectures.
AC2: Clean-up unused files and other improvements (read epic to refresh about those enhancements).

Actions #1

Updated by jfernandez 5 months ago

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

Updated by rainerkoenig 5 months ago

  • Tags changed from qe-yam-jul-sprint, qe-yam-aug-sprint to qe-yam-aug-sprint
Actions #4

Updated by jfernandez 5 months ago

  • Status changed from In Progress to Resolved
Actions #5

Updated by leli 4 months ago

  • Status changed from Resolved to Workable
Actions #6

Updated by JERiveraMoya 2 months ago

  • Tags changed from qe-yam-aug-sprint to qe-yam-oct-sprint
  • Status changed from Workable to In Progress

@jfernandez could you please take a look?

Actions #7

Updated by JERiveraMoya 2 months ago

  • Tags changed from qe-yam-oct-sprint to qe-yam-nov-sprint
Actions #8

Updated by jfernandez 2 months ago

On my way

Actions #9

Updated by jfernandez 2 months ago

It seems to be a timing issue, related to the speed of s390x-zVM speed and OpenQA needle checking, the rest of builds pass this test so I would mark this ticket as ready to close.

Actions #10

Updated by JERiveraMoya about 2 months ago

  • Status changed from In Progress to Resolved
Actions

Also available in: Atom PDF