Project

General

Profile

Actions

action #98619

closed

Move YAML_SCHEDULE from Test Suites settings to Job Group Settings on OSD

Added by oorlov over 2 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
2021-09-14
Due date:
% Done:

0%

Estimated time:

Description

Motivation

As amount of yaml schedules grow, we should have a predictable and ideally a single place to set/edit paths to them (exceptions are allowed for sure, but smart reasons should be behind them).

Test Settings can be only be changed via browser or API calls. In both cases it does not keep history of changes, so it is easy to broke things and hard to revert them back. Also, keeping Test Settings are set after Job Group settings, so the value from Test Settings overrides the one from Job Group settings, which also may be confusing while debugging what goes wrong with some particular test.

In order to have the changes tracked, keep them in one place and have all the power of IDEs while editing them, we need to keep the YAML_SCHEDULE only in Job Group settings.

Scope

  • OSD;
  • All test suites that set YAML_SCHEDULE in Test Suite settings and have schedule/yast path.

Task

  1. Remove all YAML_SCHEDULES to schedule/yast from Test Suite setting;
  2. Add them to Job Group settings accordingly;
  3. For maintenance job, move YAML_SCHEDULES setting from json test suites to job group test suite (in maintenance repo). It should be done, but double-check.
  4. Provide Verification runs.
Actions #1

Updated by oorlov over 2 years ago

  • Subject changed from Move YAML_SCHEDULE from Test Suites settings to Job Group Settings to Move YAML_SCHEDULE from Test Suites settings to Job Group Settings on OSD
Actions #2

Updated by JERiveraMoya over 2 years ago

Notice we should discuss and take into account that for the test suite that are shared, there was this recent PR https://gitlab.suse.de/qa-maintenance/qam-openqa-yml/-/merge_requests/163. So if we move the setting it will reappear once that external CI is triggered (in my understanding) as test suite are stored there in json format. We have the option to exclude it there (I asked for that just in case), but if we do so the setting needs to be in Test suites in openQA or pushed to those groups by our CI (which I think that is out of scope). So we might need to leave for now with those setting in json if present.

Actions #3

Updated by JERiveraMoya over 2 years ago

  • Tags deleted (qe-yast-refinement)
  • Status changed from New to Workable
Actions #4

Updated by JERiveraMoya over 2 years ago

  • Description updated (diff)
Actions #5

Updated by JERiveraMoya over 2 years ago

  • Status changed from Workable to In Progress
  • Assignee set to JERiveraMoya
Actions #7

Updated by JERiveraMoya over 2 years ago

  • Status changed from In Progress to Feedback
Actions #8

Updated by JERiveraMoya over 2 years ago

  • Status changed from Feedback to Closed
Actions

Also available in: Atom PDF