action #59397

Make openQA less "iso" centric

Added by okurz 3 months ago. Updated 3 months ago.

Status:NewStart date:13/11/2019
Priority:LowDue date:
Assignee:-% Done:

0%

Category:Feature requests
Target version:QA - future
Difficulty:
Duration:

Description

Motivation

Initially openQA was invented to test "ISOs", nowadays it is much more than that, e.g. with booting HDD images for JeOS as well as in many downstream jobs after installation. Things like the API route operation "isos post" feels outdated and confusing as well as having an ISO commonly set on all jobs even if not required can cause useless traffic and usage of space (see #59394)

Suggestions

  • Somehow make an empty ISO variable the default when an HDD is used
  • Add/rename API route to a more generic one
  • Check for occurences of "ISO" where we most likely mean a more generic "product" and change that

Related issues

Copied from openQA Project - action #33946: Iso image of Parent Job is downloaded even if "--skip-dep... Resolved 28/03/2018 12/11/2019

History

#1 Updated by okurz 3 months ago

  • Copied from action #33946: Iso image of Parent Job is downloaded even if "--skip-deps" property is specified while cloning Child Job added

Also available in: Atom PDF