action #132335
Updated by okurz 10 months ago
## Motivation We have both https://github.com/os-autoinst/os-autoinst-distri-openQA/blob/master/scenario-definitions.yaml as well as https://github.com/os-autoinst/opensuse-jobgroups/blob/master/job_groups/openqa.yaml and we should not duplicate. Let's ensure that the scenario definitions file can take over completely including the test suite descriptions and then delete the job group templates. ## Acceptance criteria * **AC1:** https://github.com/os-autoinst/opensuse-jobgroups/blob/master/job_groups/openqa.yaml does not duplicate anything anymore from https://github.com/os-autoinst/os-autoinst-distri-openQA/blob/master/scenario-definitions.yaml * **AC2:** We still have separate, differing test definitions for pull requests and for what is triggered nightly * **AC3:** It is clear from tests where the schedule is defined and where it needs to be changed ## Suggestions * Try to put in the scenario definitions URL into the isos post call in the according calls used in http://jenkins.qa.suse.de/ jobs so that we at best we don't need the job templates in the job group anymore * Include the test suite descriptions from job templates into scenario definitions * Consider the actual differences where they make sense, e.g. in job templates we have a "publish" job publishing an appliance which we don't want to trigger in every pull request CI test run. Maybe just handle the publish test completely separate with an explicit scenario definition file that is triggered or something. Maybe separate flavors like "dev" and our "publish" variant within the same file so that we don't need to duplicate machine, etc., in multiple files * If all works well empty/delete https://github.com/os-autoinst/opensuse-jobgroups/blob/master/job_groups/openqa.yaml