Project

General

Profile

Actions

action #66071

closed

TEST is overridden in parent job when doing `openqa-clone-custom-git-refspec`

Added by Xiaojing_liu almost 4 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
Low
Assignee:
Category:
Feature requests
Target version:
Start date:
2020-04-26
Due date:
% Done:

0%

Estimated time:

Description

When users use openqa-clone-custom-git-refspec to trigger a job which has a parent job (START_DIRECTLY_AFTER_TEST=XXX), the two jobs were triggered and they had the same TEST.

Steps:

  1. remove the default parameter --skip-chained-deps from openqa-clone-custom-git-refspec. (If not remove, only one job will be triggered)
  2. using openqa-clone-custom-git-refspec to trigger one job with parent job or parallel job, with -c "--parental-inheritance"
  3. two jobs will be triggered and with same TEST

Here is an example:

openqa-clone-custom-git-refspec https://github.com/hjluo/os-autoinst-distri-opensuse/tree/ppc64le-spvm http://openqa.nue.suse.com/tests/4142993 -c " --apikey xxx --apisecret xxx" _GROUP=0 -c " --parental-inheritance"
Cloning dependencies of sle-15-SP2-Migration-from-SLE15-SPX-to-SLE15-SP2-ppc64le-Build178.1-offline_sles15sp1_media_basesys-srv_all_full_spvm@ppc64le-hmc
Created job #4144834: sle-15-SP1-Migration-from-SLE15-SPX-to-SLE15-SP2-ppc64le-Build178.1-offline_sles15sp1_media_basesys-srv_all_full_spvm_peperation@ppc64le-hmc -> http://openqa.nue.suse.com/t4144834
Created job #4144835: sle-15-SP2-Migration-from-SLE15-SPX-to-SLE15-SP2-ppc64le-Build178.1-offline_sles15sp1_media_basesys-srv_all_full_spvm@ppc64le-hmc -> http://openqa.nue.suse.com/t4144835

Suggestion:
The TEST should not be overridden in parent or parallel job.


Related issues 2 (1 open1 closed)

Related to openQA Project - coordination #58184: [saga][epic][use case] full version control awareness within openQABlockedokurz2018-03-232024-04-19

Actions
Related to openQA Project - coordination #103971: [epic] Easy *re*-triggering and cloning of multi-machine testsResolvedmkittler2020-08-13

Actions
Actions #1

Updated by okurz almost 4 years ago

  • Related to coordination #58184: [saga][epic][use case] full version control awareness within openQA added
Actions #2

Updated by okurz almost 4 years ago

  • Target version set to future

Yes, this happens but we should rather invest our time in better integral support of version control systems within openQA rather than the wrapper scripts. See #58184

Actions #3

Updated by okurz about 2 years ago

  • Related to coordination #103971: [epic] Easy *re*-triggering and cloning of multi-machine tests added
Actions #4

Updated by okurz about 2 years ago

  • Status changed from New to Blocked
  • Assignee set to okurz
  • Target version changed from future to Ready

This is implicitly addressed by https://github.com/os-autoinst/openQA/pull/4563 in the scope of #103971

Actions #5

Updated by okurz about 2 years ago

  • Status changed from Blocked to Resolved

In my understanding https://github.com/os-autoinst/openQA/pull/4563 resolves this as well.

Actions

Also available in: Atom PDF