action #62219

jobs post does not support to trigger a test suite that is defined in YAML with a new alias

Added by Xiaojing_liu about 1 month ago. Updated 24 days ago.

Status:FeedbackStart date:17/01/2020
Priority:NormalDue date:
Assignee:Xiaojing_liu% Done:

0%

Category:Feature requests
Target version:Current Sprint
Difficulty:
Duration:

Description

  1. When cloning a job use clone_job.pl, the setting with + defined in Medium Types will be added into the job's setting, although it does not work. Here is an example: https://openqa.suse.de/tests/3795703#settings
  2. jobs post only support using test suite name when triggering a job.

Related issues

Blocked by openQA Project - action #60371: Fix variable precedence and predence overriding in job te... Resolved 28/11/2019
Copied to openQA Project - action #63565: The extra setting is added to the new job when cloning a job New 19/02/2020
Copied to openQA Project - action #63571: Cannot use `jobs post` to trigger test suites defined in ... Rejected 19/02/2020

History

#1 Updated by cdywan about 1 month ago

We should make sure the job template name works everywhere. To users it shouldn't even matter if it happens to be the name of a test suite or if it was defined in YAML.

#2 Updated by okurz about 1 month ago

  • Category set to Feature requests

#3 Updated by Xiaojing_liu about 1 month ago

For question 1, could we add a parameter when cloning a job? if the operation is cloning a job, just get the job's setting, don't get the other's settings from medium type and machine, test suite.
question 2, how could we support using job template name? when executing jobs post TEST=xxx, first search the XXX in job template table? if there are more than one job templates with this name, all of them will be triggered? if the job template table does not include this specified job template name, searching the test suite table?

#4 Updated by Xiaojing_liu about 1 month ago

As discussed with @cdywan, I need to write more details about question 1.
The whole users' story is that:
1. About the setting with a '+', here is a ticket that explains it. https://progress.opensuse.org/issues/60371
2. Users defined the setting property with +ISO both in Medium Type and YAML.
in Medium Type, the setting is +ISO=SLE-%VERSION%-Online-%ARCH%-Build%BUILD%-Media1.iso
in YAML the setting is re-defined as this:

- offline_sles15_media_basesys-srv-desk_all_full:
settings:
+ISO: SLE-%VERSION%-Full-%ARCH%-Build%BUILD%-Media1.iso

3. when the job is trigger by openQA, the job's setting is SLE-15-SP2-Full-x86_64-Build122.1-Media1.iso. The result is expected.
4. The job in this example (given in the description ), was cloned by users. As expected, the cloned job should have the same settings as the based job has. In fact, the cloned job has two parameters about ISO, such as:

+ISO: SLE-15-SP2-Online-x86_64-Build122.1-Media1.iso
ISO: SLE-15-SP2-Full-x86_64-Build122.1-Media1.iso

Although the setting +ISO does not affect the job, IMHO it should not be here.
I checked the code, the +ISO comes from the Medium Type. I think we should not get the settings from medium type or machine or test suite when users clone a job using openqa-clone-job.

#5 Updated by cdywan 24 days ago

  • Blocked by action #60371: Fix variable precedence and predence overriding in job templates YAML documents added

#6 Updated by cdywan 24 days ago

  • Status changed from New to Feedback
  • Assignee set to Xiaojing_liu
  • Target version set to Current Sprint

#7 Updated by Xiaojing_liu 8 days ago

  • Copied to action #63565: The extra setting is added to the new job when cloning a job added

#8 Updated by Xiaojing_liu 8 days ago

  • Copied to action #63571: Cannot use `jobs post` to trigger test suites defined in job template added

Also available in: Atom PDF