coordination #55730
Updated by okurz almost 4 years ago
## Motivation We want to move forward with reducing the number of test suites. For that we should analzye and find the job group with the biggest impact on that. ## Acceptance criteria * see subtasks ## Suggestions - analyze the test suites on osd to see which are used in very few job groups - check which of them overlap with a lot of settings and seperate settings from parameters - suggest shared test suites with common settings to job group owners/maintainers (aka convert to YAML) - remove test suites no longer used After that step I expect usability issues (we already talked about missing a unique name for such job groups) that need to be identified and solved. And then we'd restart the issue with the next job group.