action #132335
closedcoordination #58184: [saga][epic][use case] full version control awareness within openQA
coordination #154780: [epic] openQA scenario definitions fully in git
In openqa-in-openqa use scenario definitions instead of job group templates size:M
0%
Description
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
Updated by okurz over 1 year ago
- Copied from action #130369: [spike][timeboxed:20h] Reduce duplication of openQA-in-openQA tests in os-autoinst-distri-opensuse and os-autoinst-distri-openQA size:S added
Updated by okurz over 1 year ago
- Subject changed from In openqa-in-openqa use scenario definitions instead of job group templates to In openqa-in-openqa use scenario definitions instead of job group templates size:M
- Description updated (diff)
- Status changed from New to Workable
Updated by osukup over 1 year ago
preparing a change in the schedule script for Jenkins. Deployment is now blocked by https://github.com/os-autoinst/openQA/pull/5277
Updated by osukup over 1 year ago
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
so two scenario files and running publish only in Full scenario? as we now have publish jobs in standard run with openQA instance without test data and needles (uses scenario definiton to run simple job) and Full with os-autoins-distri-opensuse pull to SUT including all needles :D which is now in jenkins decided by simple ENV var
Updated by osukup over 1 year ago
Related PR:
https://github.com/os-autoinst/scripts/pull/252
https://github.com/os-autoinst/os-autoinst-distri-openQA/pull/144
https://github.com/os-autoinst/openQA/pull/5277
only missing deletion of openqa.yaml from https://github.com/os-autoinst/opensuse-jobgroups/blob/master/job_groups/openqa.yaml and a separate file for CI ... on which is q. if is really needed different definition?
Updated by osukup over 1 year ago
- Status changed from In Progress to Feedback
all three PR merged .. we will see how is going in production then remove openqa.yaml from jobs repo
Updated by osukup over 1 year ago
Updated by osukup over 1 year ago
- Status changed from Feedback to Resolved
both schedules in jenkins works as excepted, last PR isn't merged but hasn't any influence on new schedule :D so we can mark as resolved ..
Updated by okurz 12 months ago
- Status changed from Resolved to Workable
https://github.com/os-autoinst/opensuse-jobgroups/pull/358 wasn't merged until today but https://openqa.opensuse.org/admin/job_templates/24 still shows content. This should be fixed so that the job templates do not show content from something that is not even in git. Please remove the job group templates accordingly and ensure that tests still work fine after the removal.
Updated by okurz 12 months ago
- Status changed from Feedback to Resolved
ok, https://openqa.opensuse.org/group_overview/24 still shows jobs an in before. I guess we are good then. Thank you!
Updated by okurz 11 months ago
- Copied to action #155218: [spike][timeboxed:30h] Use scenario definitions instead of job group templates for os-autoinst-distri-opensuse size:M added