Project

General

Profile

Actions

action #132335

closed

coordination #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

Added by okurz 11 months ago. Updated 4 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
Start date:
2023-06-01
Due date:
% Done:

0%

Estimated time:

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

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

Related issues 2 (0 open2 closed)

Copied from openQA Project - action #130369: [spike][timeboxed:20h] Reduce duplication of openQA-in-openQA tests in os-autoinst-distri-opensuse and os-autoinst-distri-openQA size:SResolvedtinita2023-06-01

Actions
Copied to openQA Project - action #155218: [spike][timeboxed:30h] Use scenario definitions instead of job group templates for os-autoinst-distri-opensuse size:MResolvedtinita

Actions
Actions #1

Updated by okurz 11 months 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
Actions #2

Updated by okurz 11 months 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
Actions #3

Updated by osukup 10 months ago

  • Assignee set to osukup
Actions #4

Updated by osukup 10 months ago

  • Status changed from Workable to In Progress
Actions #5

Updated by osukup 10 months ago

preparing a change in the schedule script for Jenkins. Deployment is now blocked by https://github.com/os-autoinst/openQA/pull/5277

Actions #6

Updated by osukup 10 months 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

Actions #8

Updated by osukup 10 months 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

Actions #10

Updated by osukup 10 months 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 ..

Actions #11

Updated by okurz 5 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.

Actions #12

Updated by osukup 5 months ago

  • Status changed from Workable to Feedback

job template cleanup in O3,

Actions #13

Updated by okurz 5 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!

Actions #14

Updated by okurz 4 months ago

  • Parent task changed from #108527 to #154780
Actions #15

Updated by okurz 4 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
Actions

Also available in: Atom PDF