action #113219
closed
Create a master label at job group level to label all the jobs in the same build
Added by jlausuch almost 2 years ago.
Updated almost 2 years ago.
Category:
Feature requests
Description
As a openQA user, I would like to have a feature to label all the jobs of the same build at the same time with certain bsc or poo, instead of labeling one by one.
A possible use case is in container image tests (BCI) where a new container image build is tested on multiple host versions and architectures to be validated. Sometimes, the image is faulty and we need to label all the jobs (~40) which makes thing very time consuming for the reviewer.
For example, this build or this are mostly failed tests.
It would be nice to use the tag feature + the build number doing something like this:
and automatically label all the jobs.
Files
- Subject changed from Create a master label at job group level to label all the jobs in the same build. to Create a master label at job group level to label all the jobs in the same build
- Category set to Feature requests
- Status changed from New to Feedback
- Assignee set to okurz
- Target version set to Ready
jlausuch wrote:
[…] we need to label all the jobs (~40) which makes thing very time consuming for the reviewer.
I assume you mean that this is very time consuming because reviewers do that manually one by one?
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:
- Simply use the build tagging and ignore individual unlabeled jobs as the complete build can be ignored
- Use auto-review to label jobs automatically based on regex matches in ticket subject lines
- Use the application "openqa-label-all" from the package "openQA-python-scripts", part of openQA
- Manual script hacking using the openQA API and labelling, e.g. using openqa-cli or simply curl to write comments
- Delete all affected jobs directly
- Due date set to 2022-07-19
- Status changed from Feedback to Closed
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!
Also available in: Atom
PDF