Project

General

Profile

Actions
Copy link

action #161126

closed

coordination #151816: [epic] Handle openQA fixes and job group setup

Enable SL Micro 6.1 in OSD in Yam squad

Added by JERiveraMoya 4 months ago. Updated 4 months ago.

Status:
Resolved
Priority:
High
Assignee:
tinawang123
Target version:
-
Start date:
2024-05-29
Due date:
% Done:

0%

Estimated time:
Tags:
qe-yam-jun-sprint

Description

Motivation

See

Acceptance criteria

AC1: Job group for SL Micro 6.1 is enabled for QE Yam

Additional information

It was mentioned that those variables starting by dot . at the beginning of the job group yaml should be reviewed and don't copy paste if they are already in mediums.

Actions
Copy link
 #2

Updated by JERiveraMoya 4 months ago

  • Priority changed from Normal to High
Actions
Copy link
 #3

Updated by tinawang123 4 months ago

  • Status changed from Workable to In Progress
  • Assignee set to tinawang123
Actions
Copy link
 #4

Updated by JERiveraMoya 4 months ago

For now we will attempt migration 6.0 -> 6.1 as discussed in Slack.

Actions
Copy link
 #7

Updated by JERiveraMoya 4 months ago

hi @tinawang123, would you mind to reopen this ticket to add ppc64le as well, I just read that in the related ticket, perhaps you also can ask there the doubt about toolbox. https://progress.opensuse.org/issues/160433#note-14

Actions
Copy link
 #8

Updated by tinawang123 4 months ago

JERiveraMoya wrote in #note-7:

hi @tinawang123, would you mind to reopen this ticket to add ppc64le as well, I just read that in the related ticket, perhaps you also can ask there the doubt about toolbox. https://progress.opensuse.org/issues/160433#note-14

I have asked at the ticket, which medium should be tested for ppc.

If we need add jobs for ppc, I will re-open this ticket.

Actions
Copy link
 #9

Updated by JERiveraMoya 4 months ago ยท Edited

We should not rely on resolved ticket to remember things (otherwise we might forget) or reopen tickets in a different sprint (to mess up with metrics).
For me there are two options to avoid that:

  • Reopen this ticket and wait for the answer (this makes more sense to me because Jose most likely will setup ppc64le soon there, but we don't know for sure).
  • File a new one for the remaining part (anyone else can do it, this is better solution if ETA is longer).

Please apply one of those or suggest another way of reminder.

Actions
Copy link
 #10

Updated by tinawang123 4 months ago

JERiveraMoya wrote in #note-9:

We should not rely on resolved ticket to remember things (otherwise we might forget) or reopen tickets in a different sprint (to mess up with metrics).
For me there are two options to avoid that:

  • Reopen this ticket and wait for the answer (this makes more sense to me because Jose most likely will setup ppc64le soon there, but we don't know for sure).
  • File a new one for the remaining part (anyone else can do it, this is better solution if ETA is longer).

Please apply one of those or suggest another way of reminder.

Thanks for your suggestion. After I can confirm we need add ppc job for slem, I will open a new ticket for the remaining part.

Actions
Copy link
 #11

Updated by JERiveraMoya 4 months ago

Thanks for checking it, then we are done here :)
https://progress.opensuse.org/issues/160433#note-18

Actions
Copy link

Also available in: Atom PDF