Project

General

Profile

Actions
Copy link

action #12846

closed

Easier job triggering on existing test suite

Added by dheidler almost 8 years ago. Updated over 6 years ago.

Status:
Rejected
Priority:
Low
Assignee:
-
Category:
Feature requests
Target version:
-
Start date:
2016-07-25
Due date:
% Done:

0%

Estimated time:

Description

User story

As an operator trying to reproduce an issue or developing a new test I want an easier way to trigger tests based on test suites than needing to write down all variables manually to save typing.

acceptance criteria

  • AC1: There is a CLI containing only test suite, iso to trigger a test
  • AC2: The CLI also takes additional overwrite variables as the existing clone_job or client script

tasks

  • Look at the existing clone_job.pl and client script, maybe can be added there
  • Parse available test suites and ISOs from server and compare against CLI parameter
  • optional: handle variable expansion in variables, e.g. asset prefix in HDD_1
Actions
Copy link
 #1

Updated by okurz over 7 years ago

  • Category set to Feature requests
  • Priority changed from Normal to Low
Actions
Copy link
 #2

Updated by coolo over 6 years ago

  • Status changed from New to Rejected

I don't even understand the user story. If I 'reproduce an issue', I clone the job. If I start to write a new test suite, I start with an existant test - aka clone the job.

To trigger a test suite on an ISO, you still need DISTRI, VERSION, FLAVOR, ARCH and the MACHINE settings. Aka: what you describe is impossible

Actions
Copy link

Also available in: Atom PDF