https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842020-01-17T08:36:20ZopenSUSE Project Management ToolopenQA Project - action #62219: jobs post does not support to trigger a test suite that is defined in YAML with a new aliashttps://progress.opensuse.org/issues/62219?journal_id=2721682020-01-17T08:36:20Zlivdywanliv.dywan@suse.com
<ul></ul><p>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.</p>
openQA Project - action #62219: jobs post does not support to trigger a test suite that is defined in YAML with a new aliashttps://progress.opensuse.org/issues/62219?journal_id=2721832020-01-17T09:02:18Zokurzokurz@suse.com
<ul><li><strong>Category</strong> set to <i>Feature requests</i></li></ul> openQA Project - action #62219: jobs post does not support to trigger a test suite that is defined in YAML with a new aliashttps://progress.opensuse.org/issues/62219?journal_id=2726302020-01-20T08:53:36ZXiaojing_liuxliu1@suse.com
<ul></ul><p>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.<br>
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?</p>
openQA Project - action #62219: jobs post does not support to trigger a test suite that is defined in YAML with a new aliashttps://progress.opensuse.org/issues/62219?journal_id=2733232020-01-22T07:24:16ZXiaojing_liuxliu1@suse.com
<ul></ul><p>As discussed with @cdywan, I need to write more details about question 1.<br>
The whole users' story is that:</p>
<ol>
<li>About the setting with a '+', here is a ticket that explains it. <a href="https://progress.opensuse.org/issues/60371" class="external">https://progress.opensuse.org/issues/60371</a></li>
<li>Users defined the setting property with <code>+ISO</code> both in Medium Type and YAML.
in Medium Type, the setting is <code>+ISO=SLE-%VERSION%-Online-%ARCH%-Build%BUILD%-Media1.iso</code>
in YAML the setting is re-defined as this:
<code>
- offline_sles15_media_basesys-srv-desk_all_full:
settings:
+ISO: SLE-%VERSION%-Full-%ARCH%-Build%BUILD%-Media1.iso
</code> </li>
<li>when the job is trigger by openQA, the job's setting is <code>SLE-15-SP2-Full-x86_64-Build122.1-Media1.iso</code>. The result is expected.</li>
<li>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:
<code>
+ISO: SLE-15-SP2-Online-x86_64-Build122.1-Media1.iso
ISO: SLE-15-SP2-Full-x86_64-Build122.1-Media1.iso
</code>
Although the setting <code>+ISO</code> does not affect the job, IMHO it should not be here.
I checked the code, the <code>+ISO</code> 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 <code>openqa-clone-job</code>.</li>
</ol>
openQA Project - action #62219: jobs post does not support to trigger a test suite that is defined in YAML with a new aliashttps://progress.opensuse.org/issues/62219?journal_id=2759092020-02-03T08:15:30Zlivdywanliv.dywan@suse.com
<ul><li><strong>Blocked by</strong> <i><a class="issue tracker-4 status-3 priority-3 priority-lowest closed" href="/issues/60371">action #60371</a>: Fix variable precedence and predence overriding in job templates YAML documents</i> added</li></ul> openQA Project - action #62219: jobs post does not support to trigger a test suite that is defined in YAML with a new aliashttps://progress.opensuse.org/issues/62219?journal_id=2759122020-02-03T08:17:07Zlivdywanliv.dywan@suse.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li><li><strong>Assignee</strong> set to <i>Xiaojing_liu</i></li><li><strong>Target version</strong> set to <i>Current Sprint</i></li></ul> openQA Project - action #62219: jobs post does not support to trigger a test suite that is defined in YAML with a new aliashttps://progress.opensuse.org/issues/62219?journal_id=2787822020-02-19T07:29:15ZXiaojing_liuxliu1@suse.com
<ul><li><strong>Copied to</strong> <i><a class="issue tracker-4 status-3 priority-3 priority-lowest closed" href="/issues/63565">action #63565</a>: The extra setting is added to the new job when cloning a job</i> added</li></ul> openQA Project - action #62219: jobs post does not support to trigger a test suite that is defined in YAML with a new aliashttps://progress.opensuse.org/issues/62219?journal_id=2788032020-02-19T07:48:41ZXiaojing_liuxliu1@suse.com
<ul><li><strong>Copied to</strong> <i><a class="issue tracker-4 status-6 priority-3 priority-lowest closed" href="/issues/63571">action #63571</a>: Cannot use `jobs post` to trigger test suites defined in job template</i> added</li></ul> openQA Project - action #62219: jobs post does not support to trigger a test suite that is defined in YAML with a new aliashttps://progress.opensuse.org/issues/62219?journal_id=2855932020-03-16T10:02:27Zlivdywanliv.dywan@suse.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Closed</i></li></ul><p>This ticket has been split up into separate tasks so for clarity I'm closing it.</p>