Clone_job: support global variables
Doing clone_job.pl --skip-chained-deps --skip-download --from http://openqa.suse.de 1173559 WORKER_CLASS=local
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).
#1 Updated by coolo almost 2 years ago
- Subject changed from Clone job does not copy settings to chained jobs to Clone_job: support global variables
- Category changed from Concrete Bugs 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.