Project

General

Profile

action #93931

coordination #93871: [epic] support process improvement in maintenance requests: packages from different code streams with identical fix sets/features in a single incident

[tools][qem] MTUI support multiple versions of package in incident

Added by osukup about 2 months ago. Updated about 1 month ago.

Status:
Resolved
Priority:
Low
Assignee:
Target version:
Start date:
2021-06-14
Due date:
% Done:

0%

Estimated time:

Description

Acceptance criteria

  1. new Incidents can be created using multiple code branches

Suggestion

  1. Parse new PackageVer from template
  2. compare correct version during update/downgrade step
  3. export command exports correct versions per refhost
  4. list_packages command with the correct version

Related issues

Has duplicate QA - action #80690: [qem] Testing of packages in different codestreams but in one incidentResolved2020-12-03

Blocked by QA - action #93934: [tools][qem] template generator - multiple package version in incidentResolved2020-12-04

History

#1 Updated by osukup about 2 months ago

  • Blocked by action #93934: [tools][qem] template generator - multiple package version in incident added

#2 Updated by okurz about 2 months ago

  • Target version set to Ready

#3 Updated by okurz about 2 months ago

osukup how would you judge the urgency of this ticket? Strictly speaking, when do we need this?

#4 Updated by osukup about 2 months ago

  • Description updated (diff)
  • Status changed from New to In Progress
  • Assignee set to osukup

okurz - in an ideal state, before the first Incident with this change :(

-> It needs move package versions storage and handling from Testreport class to Target + optimally also 'add/remove repo' etc

#5 Updated by openqa_review about 2 months ago

  • Due date set to 2021-07-03

Setting due date based on mean cycle time of SUSE QE Tools

#6 Updated by jbaier_cz about 1 month ago

  • Has duplicate action #80690: [qem] Testing of packages in different codestreams but in one incident added

#7 Updated by okurz about 1 month ago

  • Priority changed from Normal to Low

I understood from hrommel1 that this task would be good to follow-up and finish but is considered less important than for example #92125 as IIUC workarounds are known and the impact is limited to mtui. If possible please finish fast or unassign to be picked up later again.

#8 Updated by jbaier_cz about 1 month ago

okurz wrote:

as IIUC workarounds are known and the impact is limited to mtui

Maybe I miss something, but I am not really aware of any workaround. The impact is limited to testing incidents with this "feature" (and there are such in the queue at this moment).

#10 Updated by cdywan about 1 month ago

  • Description updated (diff)

#11 Updated by osukup about 1 month ago

  • Status changed from In Progress to Feedback

if no complaint about devel version of MTUI +- on Monday create new versio n branch and publish in stable channel

#12 Updated by osukup about 1 month ago

  • Status changed from Feedback to Resolved

released as 13.0.0

#13 Updated by cdywan about 1 month ago

  • Due date deleted (2021-07-03)

Also available in: Atom PDF