action #25412: Clone_job: support global variables - openQA Project (public) - openSUSE Project Management Tool

Actions

Copy link

action #25412

closed

Clone_job: support global variables

Added by zluo about 7 years ago. Updated over 6 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

mitiao

Category:

Feature requests

Target version:

Done

Start date:

2017-09-19

Due date:

% Done:

Estimated time:

Description

Doing clone_job.pl --skip-chained-deps --skip-download --from http://openqa.suse.de 1173559 WORKER_CLASS=local

Creates

Created job #4099: sle-15-Leanos-DVD-x86_64-Build260.4-autoyast-supportserver@64bit -> http://localhost/t4099
Created job #4100: sle-15-Leanos-DVD-x86_64-Build260.4-sles12_autoyast_tftp@64bit -> http://localhost/t4100

While sle-15-Leanos-DVD-x86_64-Build260.4-sles12_autoyast_tftp@64bit ended up with WORKER_CLASS=local it's parent job sle-15-Leanos-DVD-x86_64-Build260.4-autoyast-supportserver@64bit did not (It kept the values from the original job).

Actions

Copy link

Updated by coolo over 6 years ago

Subject changed from Clone job does not copy settings to chained jobs to Clone_job: support global variables
Category changed from Regressions/Crashes to Feature requests
Target version set to Ready

This is a feature - as the variables you give there are for the jobs to be cloned. WORKER_CLASS (and possibly other machine related variables) need to be differed. But perhaps you realize the problem if you consider that I use TEST very often for clone_job to give the clone a different name. Having this in the parents too doesn't make sense.
But even things like QEMUCPU are not necessarly also for the dependencies (imagine you're cloning parallel jobs, not chained ones).

So IMO what we need is a switch in clone_job for variables to be passed to dependent jobs.

Actions

Copy link

Updated by oorlov over 6 years ago

Today I've also noticed that behavior while cloning child job with the custom WORKER_CLASS parameter. The parent did not get the same worker class name and did not start. Would be a nice feature to pass the WORKER_CLASS parameter to parent job.

Actions

Copy link