action #57845

openQA Tests - action #15132: [epic] Better structure of test plans in main.pm

action #44360: [epic] Parameterize test suites within job groups

action #55730: [epic] Move parameters from test suites into job groups

Switch more job groups to YAML job templates

Added by okurz 5 months ago. Updated 3 months ago.

Status:ResolvedStart date:09/10/2019
Priority:NormalDue date:19/11/2019
Assignee:okurz% Done:

0%

Category:Organisational
Target version:Current Sprint
Difficulty:
Duration: 30

History

#1 Updated by okurz 4 months ago

  • Due date changed from 22/10/2019 to 05/11/2019

As discussed in the QA tools weekly meeting 2019-10-22 and announced in http://mailman.suse.de/mlarch/SuSE/openqa/2019/openqa.2019.10/msg00005.html we will await SLE12SP5 GM gold declaration and then switch over all remaining job groups to the YAML format.

#2 Updated by okurz 4 months ago

  • Due date changed from 05/11/2019 to 19/11/2019

#3 Updated by okurz 3 months ago

  • Due date changed from 19/11/2019 to 17/12/2019

o3 is fully YAML-only now. osd has select count(id) from job_groups where template is null; -> 114 . Next step: https://github.com/os-autoinst/openQA/pull/2518 for deprecation notice. Follow-up: https://github.com/os-autoinst/openQA/pull/2519 disabling editor functionalities. In weekly tools team meeting we decided to point admins to the UI for saving instead of coming up with a migration script that could break in the background. I assume with this we give users again more time to switch by themselves.

#4 Updated by coolo 3 months ago

That deprecation warning was not for osd though - there we gave a deprecation warning by email before summer. So go ahead with osd independently of that

#5 Updated by mgriessmeier 3 months ago

for reference:
Functional group for SLE15 was already migrated, including gitlab-ci with auto deployment in place - same as for YaST job group

#6 Updated by okurz 3 months ago

Sent email announcement to openqa.suse.de. Saving backup of all job templates with openqa-dump-templates --full --json --host openqa.suse.de > openqa_templates_osd-$(date +%F).json && openqa-dump-templates --full --host openqa.suse.de > openqa_templates_osd-$(date +%F).pl, saved in https://w3.nue.suse.com/~okurz/openqa_osd_backup_job_templates_before_switch_to_yaml_poo57845/

I did a dry-run of the migration with

for i in $(ssh openqa.suse.de "sudo -u geekotest psql --no-align --tuples-only --command=\"select id from job_groups where template is null order by id;\" openqa") ; do curl -s http://openqa.suse.de/api/v1/job_templates_scheduling/$i | openqa-client --json-output --host http://openqa.suse.de job_templates_scheduling/$i post --form schema=JobTemplates-01.yaml preview=1 template="$(cat -)"; done | tee migration_preview.log 2>&1

and have received entries like

{
   "id" : 1,
   "preview" : 1
}

for all job groups. I guess this is a good sign.

And a live change with

for i in $(ssh openqa.suse.de "sudo -u geekotest psql --no-align --tuples-only --command=\"select id from job_groups where template is null order by id;\" openqa") ; do curl -s http://openqa.suse.de/api/v1/job_templates_scheduling/$i | openqa-client --json-output --host http://openqa.suse.de job_templates_scheduling/$i post --form schema=JobTemplates-01.yaml template="$(cat -)"; done | tee migration.log 2>&1

All done. Database query select count(id) from job_groups where template is null; returns 0 job groups left. The ids of all job groups converted can be found in https://w3.nue.suse.com/~okurz/openqa_osd_backup_job_templates_before_switch_to_yaml_poo57845/ as well.

#7 Updated by okurz 3 months ago

  • Due date changed from 17/12/2019 to 19/11/2019
  • Status changed from Feedback to Resolved

Considered done.

Also available in: Atom PDF