Project

General

Profile

Actions

action #124493

closed

openqa-clone-job --skip-deps behavior contradicts documentation size:M

Added by MDoucha almost 2 years ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Regressions/Crashes
Target version:
Start date:
2023-02-14
Due date:
2023-03-31
% Done:

0%

Estimated time:

Description

Observation

Both OpenQA documentation and openqa-clone-job --help say that --skip-deps and --skip-chained-deps should only prevent cloning of parent jobs. In reality, however, both options will prevent cloning of all (chained) dependencies regardless of parent/child relationship (even when you specify --clone-children). This means there is currently no way to clone a dependency subtree without parents using openqa-clone-job. The subtree can only be restarted in webUI which does not support modifying settings of the restarted jobs.

Acceptance criteria

  • AC1: There is a way to clone a dependency subtree without parents using openqa-clone-job (in accordance with the documentation).

Suggestions

  • It probably worked in the past, maybe a regression?
  • Create a set of dependent jobs locally (e.g. by setting dependencies manually within the database or by cloning a set of jobs from production) and run openqa-clone-job locally with parameters mention in description
  • Extend unit tests
Actions

Also available in: Atom PDF