Project

General

Profile

coordination #72889

[qe-core][qem][epic] QAM move job groups, test suites, medium types to git, and then restructure QAM testing to be more easily comparable to product QA

Added by okurz over 1 year ago. Updated about 1 month ago.

Status:
Workable
Priority:
Normal
Assignee:
-
Category:
Infrastructure
Target version:
-
Start date:
2021-01-12
Due date:
% Done:

50%

Estimated time:
(Total: 0.00 h)
Difficulty:

Subtasks

action #86099: [qe-core][qem] Move osd test suites to gitResolvedapappas

action #102548: [infrastructure] Ensure all jobgroups in osd and o3 display correct information on where they are being maintainedNew

History

#1 Updated by okurz over 1 year ago

  • Assignee deleted (okurz)

#2 Updated by okurz over 1 year ago

  • Subject changed from [QAM - QASLE Collaboration][DOING] QAM move job groups, test suites, medium types to git, and then restructure QAM testing to be more asily comparable to product QA. to QAM move job groups, test suites, medium types to git, and then restructure QAM testing to be more asily comparable to product QA

#3 Updated by okurz over 1 year ago

  • Tags set to qam-qasle-collaboration

#4 Updated by okurz over 1 year ago

  • Tags deleted (qam-qasle-collaboration)

#5 Updated by okurz about 1 year ago

  • Due date set to 2020-11-13
  • Assignee set to apappas

apappas is working on that. He can provide status after 2020-11-12

#7 Updated by apappas about 1 year ago

As mentioned in the related ticket I added, the CI was created at https://gitlab.suse.de/qa-maintenance/qam-openqa-yml . To avoid any synchronization issues and to be able to have the weekend to troubleshoot, I will enable it after business hours today.

#8 Updated by maritawerner about 1 year ago

Oli, I would be very interested in the discussion about "restructure QAM to be more comparabpe to product QA". Please let me know when there are more discussions taking place.

#9 Updated by okurz about 1 year ago

Sure. I am aware of discussions in the ticket here, the linked ticket and some confluence documents about QAM processes which in relation to the topic at hand mainly mention a simple, single aspect: Changes to the test schedule are important to have a proper reasoning for changes and trackability which is provided by knowing which git commit corresponds to observed test results. I am not aware of any more discussions, e.g. no "video-chat-meetings" about this topic in particular.

#10 Updated by okurz about 1 year ago

  • Subject changed from QAM move job groups, test suites, medium types to git, and then restructure QAM testing to be more asily comparable to product QA to QAM move job groups, test suites, medium types to git, and then restructure QAM testing to be more easily comparable to product QA

#11 Updated by okurz about 1 year ago

apappas as your "self-imposed due-date" has passed and as we discussed this topic in the weekly QE Sync call we would be happy to hear an update from you :) Maybe you can present something?

#12 Updated by tjyrinki_suse about 1 year ago

This is mostly done and works great, but a couple of things are simply missing from the set of managed job groups so the ticket is still open. Anton is currently away.

#13 Updated by tjyrinki_suse about 1 year ago

  • Status changed from In Progress to Resolved

No need for qasle-qam coordination on this topic anymore, the work ticket will need to be finished but is 90% done.

#14 Updated by apappas about 1 year ago

  • Status changed from Resolved to In Progress

The CI for the JobGroups is done but not for the other two things. After hitting a few snags with openqa-load/dump-templates and the REST API I am almost done with the test suites and I am reopening and adding them as a subissue now.

#15 Updated by apappas about 1 year ago

However I do thing this needs to be moved to the qem tag.

#16 Updated by tjyrinki_suse 12 months ago

  • Project changed from qam-qasle-collaboration to openQA Tests
  • Subject changed from QAM move job groups, test suites, medium types to git, and then restructure QAM testing to be more easily comparable to product QA to [qe-core][qem] QAM move job groups, test suites, medium types to git, and then restructure QAM testing to be more easily comparable to product QA

Moving the ticket as it was discussed this does not need to be on the weekly meeting's topic. Adding tags as suggested by apappas.

#17 Updated by tjyrinki_suse 11 months ago

  • Tracker changed from action to coordination
  • Subject changed from [qe-core][qem] QAM move job groups, test suites, medium types to git, and then restructure QAM testing to be more easily comparable to product QA to [qe-core][qem][epic] QAM move job groups, test suites, medium types to git, and then restructure QAM testing to be more easily comparable to product QA

Changing to epic task.

#18 Updated by tjyrinki_suse 11 months ago

  • Assignee deleted (apappas)

sub-tickets have assignees, this epic can be without.

#19 Updated by okurz 11 months ago

well, who would we ask about the progress then? What I suggest is to set the ticket to "Blocked" (by the sub-tickets) but still have a "person of contact", not necessarily the main implementer. So in this case it can be you, tjyrinki_suse. What do you think about that approach?

#20 Updated by tjyrinki_suse 9 months ago

  • Category set to Infrastructure

#21 Updated by tjyrinki_suse 2 months ago

  • Assignee set to tjyrinki_suse

Test suite CI review discussion was done at https://gitlab.suse.de/qa-maintenance/qam-openqa-yml/-/merge_requests/163

And indeed maybe this one could have a contact person if it helps, even if the contact person would only forward to another person.

Notably this task could theoretically extend to O3, an entirely different discussion and CI for which should be done in a public repository.

#22 Updated by tjyrinki_suse 2 months ago

  • Status changed from In Progress to Workable

I think at the moment this would need next phase of planning instead of being in progress.

#23 Updated by pcervinka 2 months ago

https://gitlab.suse.de/qa-maintenance/qam-openqa-yml/-/merge_requests/163 clearly demonstrates inneficiency of openQA management settings. It is bad that it must be handled outside of openQA by 3rd party git repo for versioning purposes of test suite settings.

#25 Updated by tjyrinki_suse about 1 month ago

  • Assignee deleted (tjyrinki_suse)

Also available in: Atom PDF