https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842021-05-07T11:08:58ZopenSUSE Project Management ToolopenQA Project - action #92311: Complete test definition from a single yaml schedule file in local test distribution folderhttps://progress.opensuse.org/issues/92311?journal_id=4051302021-05-07T11:08:58Zokurzokurz@suse.com
<ul><li><strong>Copied from</strong> <i><a class="issue tracker-4 status-3 priority-4 priority-default closed child" href="/issues/71758">action #71758</a>: [spike][timeboxed:20h] complete test definition from a yaml schedule file in local test distribution folder</i> added</li></ul> openQA Project - action #92311: Complete test definition from a single yaml schedule file in local test distribution folderhttps://progress.opensuse.org/issues/92311?journal_id=6015622023-02-14T09:49:46Zokurzokurz@suse.com
<ul><li><strong>Status</strong> changed from <i>Workable</i> to <i>New</i></li><li><strong>Target version</strong> changed from <i>future</i> to <i>Ready</i></li></ul> openQA Project - action #92311: Complete test definition from a single yaml schedule file in local test distribution folderhttps://progress.opensuse.org/issues/92311?journal_id=6016252023-02-14T10:43:28Zmkittlermarius.kittler@suse.com
<ul><li><strong>Assignee</strong> set to <i>mkittler</i></li></ul> openQA Project - action #92311: Complete test definition from a single yaml schedule file in local test distribution folderhttps://progress.opensuse.org/issues/92311?journal_id=6019102023-02-14T16:35:16Zmkittlermarius.kittler@suse.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li></ul> openQA Project - action #92311: Complete test definition from a single yaml schedule file in local test distribution folderhttps://progress.opensuse.org/issues/92311?journal_id=6027022023-02-15T17:14:36Zmkittlermarius.kittler@suse.com
<ul></ul><p>Draft PR: <a href="https://github.com/os-autoinst/openQA/pull/4999" class="external">https://github.com/os-autoinst/openQA/pull/4999</a></p>
openQA Project - action #92311: Complete test definition from a single yaml schedule file in local test distribution folderhttps://progress.opensuse.org/issues/92311?journal_id=6035362023-02-17T10:38:27Zokurzokurz@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-4 priority-default closed child" href="/issues/124502">action #124502</a>: [spike][timeboxed:20h] complete test definition from yaml schedule in git checked out test distribution</i> added</li></ul> openQA Project - action #92311: Complete test definition from a single yaml schedule file in local test distribution folderhttps://progress.opensuse.org/issues/92311?journal_id=6065902023-02-27T10:06:48Zmkittlermarius.kittler@suse.com
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Feedback</i></li></ul><p>The PR is ready to be merged and documentation has been prepared as well (<a href="https://github.com/os-autoinst/openQA/pull/4999#issuecomment-1446028476" class="external">https://github.com/os-autoinst/openQA/pull/4999#issuecomment-1446028476</a>).</p>
openQA Project - action #92311: Complete test definition from a single yaml schedule file in local test distribution folderhttps://progress.opensuse.org/issues/92311?journal_id=6115102023-03-09T13:49:59Zmkittlermarius.kittler@suse.com
<ul></ul><ul>
<li>I will work on points added as inline-comments on <a href="https://github.com/os-autoinst/openQA/pull/4999" class="external">https://github.com/os-autoinst/openQA/pull/4999</a>. for everything that seems too much for the initial version of this feature I'll create follow-up tickets.</li>
<li>I will pick the documentation branch here and update it to use single quotes and to state the feature is experimental.</li>
</ul>
openQA Project - action #92311: Complete test definition from a single yaml schedule file in local test distribution folderhttps://progress.opensuse.org/issues/92311?journal_id=6115252023-03-09T14:23:49Zmkittlermarius.kittler@suse.com
<ul></ul><p>I will also create a ticket to have <code>openqa-cli</code> validate the YAML client-side. I could create the ticket right now but it would be blocked by this one anyways.</p>
openQA Project - action #92311: Complete test definition from a single yaml schedule file in local test distribution folderhttps://progress.opensuse.org/issues/92311?journal_id=6115582023-03-09T15:49:51Zmkittlermarius.kittler@suse.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>In Progress</i></li></ul> openQA Project - action #92311: Complete test definition from a single yaml schedule file in local test distribution folderhttps://progress.opensuse.org/issues/92311?journal_id=6132742023-03-14T13:05:50Zmkittlermarius.kittler@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-1 priority-3 priority-lowest" href="/issues/125990">action #125990</a>: Allow client-side validation of YAML files posted via `openqa-cli`</i> added</li></ul> openQA Project - action #92311: Complete test definition from a single yaml schedule file in local test distribution folderhttps://progress.opensuse.org/issues/92311?journal_id=6132802023-03-14T13:12:14Zmkittlermarius.kittler@suse.com
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li></ul><ul>
<li>The PR has been merged with previously mentioned amendments. This also includes documentation (stating the feature is experimental).</li>
<li>I've created <a class="issue tracker-4 status-1 priority-3 priority-lowest" title="action: Allow client-side validation of YAML files posted via `openqa-cli` (New)" href="https://progress.opensuse.org/issues/125990">#125990</a> as follow-up ticket with the idea of client-side validation of YAML documents.</li>
</ul>
<p>So I'm considering this ticket resolved. The work on <a class="issue tracker-4 status-3 priority-4 priority-default closed child" title="action: [spike][timeboxed:20h] complete test definition from yaml schedule in git checked out test distri... (Resolved)" href="https://progress.opensuse.org/issues/124502">#124502</a> has already shown that this feature generally works in production. There are further features to implement, though. So I will continue the epic by implementing <a class="issue tracker-4 status-3 priority-4 priority-default closed child" title="action: [spike][timeboxed:20h] Add monitoring-support into openqa-cli (Resolved)" href="https://progress.opensuse.org/issues/125720">#125720</a> (and then <a class="issue tracker-4 status-3 priority-5 priority-high3 closed child" title="action: Provide a ready-to-use container image or GitHub action repository to trigger/monitor openQA jobs... (Resolved)" href="https://progress.opensuse.org/issues/125723">#125723</a> would be next).</p>