Project

General

Profile

Actions
Copy link

action #117355

open

the description of "--skip-deps" from openqa-clone-job command is not exact

Added by jgwang over 1 year ago. Updated over 1 year ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Feature requests
Target version:
QA - future
Start date:
2022-09-29
Due date:
% Done:

0%

Estimated time:

Description

this is the description of '--skip-deps':

    --skip-deps
        Do NOT clone parent jobs (which is done by default).
  1. I tried to clone a job(such as named "A" ) with child job and parent job, and then only "A" is triggered with the option "--skip-deps", it seems like "Do NOT clone parent jobs and child jobs"
  2. I tried to clone a job(such as named "A" ) with child job and parent job, and then the job "A" and its parent job are triggered, so this option is not default
Actions
Copy link
 #1

Updated by okurz over 1 year ago

  • Category set to Feature requests
  • Target version set to Ready
Actions
Copy link
 #2

Updated by okurz over 1 year ago

  • Target version changed from Ready to future
Actions
Copy link
 #3

Updated by mkittler over 1 year ago

  1. Child jobs are not cloned by default (unless it is a parallel child). That is also explained correctly in the help for --clone-children. The --skip-deps has nothing to do with that so its documentation seems accurate to me.
  2. Yes. That is not in conflict with what the documentation says how I would understand it. The "which is done by default" part is in fact explicitly stating the behavior you've observed. It does not mean that the behavior with --skip-deps would be the default. That would make the flag quite useless, right? Maybe it would help to completely remove the backed as it may be more confusing than helpful.
Actions
Copy link
 #4

Updated by jgwang over 1 year ago

mkittler wrote:

  1. Child jobs are not cloned by default (unless it is a parallel child). That is also explained correctly in the help for --clone-children. The --skip-deps has nothing to do with that so its documentation seems accurate to me.
  2. Yes. That is not in conflict with what the documentation says how I would understand it. The "which is done by default" part is in fact explicitly stating the behavior you've observed. It does not mean that the behavior with --skip-deps would be the default. That would make the flag quite useless, right? Maybe it would help to completely remove the backed as it may be more confusing than helpful.

yes, I agree with you to remove the backed, and also I think we'd better to tell users the default behavior(Child jobs are not cloned by default) so that users don't get confused.

Actions
Copy link

Also available in: Atom PDF