https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842022-07-05T13:17:23ZopenSUSE Project Management ToolopenQA Project - action #113219: Create a master label at job group level to label all the jobs in the same buildhttps://progress.opensuse.org/issues/113219?journal_id=5338162022-07-05T13:17:23Zokurzokurz@suse.com
<ul><li><strong>Subject</strong> changed from <i>Create a master label at job group level to label all the jobs in the same build.</i> to <i>Create a master label at job group level to label all the jobs in the same build</i></li><li><strong>Category</strong> set to <i>Feature requests</i></li><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li><li><strong>Assignee</strong> set to <i>okurz</i></li><li><strong>Target version</strong> set to <i>Ready</i></li></ul><p>jlausuch wrote:</p>
<blockquote>
<p>[…] we need to label all the jobs (~40) which makes thing very time consuming for the reviewer.</p>
</blockquote>
<p>I assume you mean that this is very time consuming because reviewers do that manually one by one?</p>
<p>I agree that this is a valid idea in general but should be done carefully as "all jobs in the same build" might not be immediately obvious to reviewers as they can be spread out in multiple job groups, etc. We already have solutions, please tell me what you think about them. Best practices so far are:</p>
<ol>
<li>Simply use the build tagging and ignore individual unlabeled jobs as the complete build can be ignored</li>
<li>Use <a href="https://github.com/os-autoinst/scripts/blob/master/README.md#auto-review---automatically-detect-known-issues-in-openqa-jobs-label-openqa-jobs-with-ticket-references-and-optionally-retrigger" class="external">auto-review</a> to label jobs automatically based on regex matches in ticket subject lines</li>
<li>Use the application "openqa-label-all" from the package "openQA-python-scripts", part of openQA</li>
<li>Manual script hacking using the openQA API and labelling, e.g. using openqa-cli or simply curl to write comments</li>
<li>Delete all affected jobs directly</li>
</ol>
openQA Project - action #113219: Create a master label at job group level to label all the jobs in the same buildhttps://progress.opensuse.org/issues/113219?journal_id=5338192022-07-05T13:17:32Zokurzokurz@suse.com
<ul><li><strong>Due date</strong> set to <i>2022-07-19</i></li></ul> openQA Project - action #113219: Create a master label at job group level to label all the jobs in the same buildhttps://progress.opensuse.org/issues/113219?journal_id=5341462022-07-06T10:13:27Zjlausuchjalausuch@suse.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Closed</i></li></ul><p>I guess I would go for 1) would fit best our needs. I see there are also different alternatives for labeling all jobs in case I want to use them. Thanks! </p>