Project

General

Profile

action #68008

coordination #10316: [epic] Better command line options extending "client"

Implement a retrigger command in openqa-cli

Added by cdywan 10 months ago. Updated 8 months ago.

Status:
Workable
Priority:
Low
Assignee:
-
Category:
Feature requests
Target version:
Start date:
2020-06-12
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Motivation

Example:

openqa-cli retrigger --failed --job-group 'Tumbleweed' --arch x86_64

With openqa-clithis can be implemented by adding a new plugin module providing the command.

Acceptance criteria

  • AC1: Jobs can be retriggered based on common filters without needing to specify individual job IDs
  • AC2: No direct database access is needed for the caller

Suggestions

History

#1 Updated by okurz 10 months ago

  • Category set to Feature requests

#2 Updated by okurz 9 months ago

  • Target version set to Ready

#3 Updated by okurz 9 months ago

  • Subject changed from Implement a rebuild command in openqa-cli to Implement a retrigger command in openqa-cli
  • Description updated (diff)
  • Status changed from New to Workable

#4 Updated by okurz 8 months ago

  • Priority changed from Normal to Low
  • Target version changed from Ready to future

Originally I think this was a good idea but by now I think we know better:

  • Blind retriggers especially without labels can be a waste of test capacity while not addressing the real issue
  • openqa-clone-job --within-instance can help as well same as a simple for loop retriggering all failed jobs as well as re-executing the original isos post command which by now when using ObsRsync is also available over the webUI

So after all I think this might still be a valid idea but we should not currently have it on the backlog of SUSE QA Tools

Also available in: Atom PDF