action #98619
Updated by JERiveraMoya over 2 years ago
## 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.