Project

General

Profile

Actions

action #108001

open

[doc][ux][ui] Make it more obvious what "important jobs" are and how one can make jobs important (was: Important tags don't seem to have any effect)

Added by livdywan almost 3 years ago. Updated almost 3 years ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
Feature requests
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Tags:

Description

Motivation

From #105657:

  • The number of retries seen in a job is pretty handy
  • Log files tend to be gone after 3 days or so, which might be fine because bugs should be handled by then. Although uploading log files to bugs is recommended since otherwise the issue can't be investigated
  • Idea, maybe jobs with open bugs should generally be archived?

openQA has the concept of important jobs and more recently the ability to archive important jobs.

I noticed this wasn't a part of the workflow described to me. So I wanted to test it out, and I'm not sure if it actually works 🤔️


Related issues 1 (0 open1 closed)

Copied to openQA Project (public) - action #108004: Consider jobs important so long as they reference open bugsResolvedokurz2022-03-08

Actions
Actions #1

Updated by livdywan almost 3 years ago

  • Copied to action #108004: Consider jobs important so long as they reference open bugs added
Actions #2

Updated by livdywan almost 3 years ago

  • Project changed from 46 to openQA Project (public)
Actions #4

Updated by okurz almost 3 years ago

  • Category set to Support
  • Assignee set to okurz
  • Target version set to Ready

cdywan wrote:

  • Log files tend to be gone after 3 days or so, which might be fine because bugs should be handled by then. Although uploading log files to bugs is recommended since otherwise the issue can't be investigated

can you provide examples of such jobs because that shouldn't really be the case that log files vanish after three days already.

  • Idea, maybe jobs with open bugs should generally be archived?

Well, that should be in place already considering
http://open.qa/docs/#_referer_settings_to_auto_mark_important_jobs
meaning that for any openQA job where an openQA job URL is referenced and someone clicks the openQA URL from that external reference, e.g. from the bugzilla bug report, then the job will be marked with "label:linked" which should mark the job as "important"

openQA has the concept of important jobs and more recently the ability to archive important jobs.

I noticed this wasn't a part of the workflow described to me. So I wanted to test it out, and I'm not sure if it actually works 🤔️

There seems to be quite some confusion with wording. You can only tag builds, not jobs, see http://open.qa/docs/#build_tagging . What you did in https://openqa.opensuse.org/tests/2234385#comments is effectively write a plain comment because the keyword "tag" does not have any special meaning within a job comment. What we could do is mark the keyword "tag" in plain openQA comments and provide some kind of "help text" like Clippy in Microsoft Office to remind people that maybe they tried to achieve something different and that this does not work here :)

Actions #5

Updated by livdywan almost 3 years ago

okurz wrote:

Well, that should be in place already considering
http://open.qa/docs/#_referer_settings_to_auto_mark_important_jobs

#108004#note-4

There seems to be quite some confusion with wording. You can only tag builds, not jobs, see http://open.qa/docs/#build_tagging . What you did in https://openqa.opensuse.org/tests/2234385#comments is effectively write a plain comment because the keyword "tag" does not have any special meaning within a job comment. What we could do is mark the keyword "tag" in plain openQA comments and provide some kind of "help text" like Clippy in Microsoft Office to remind people that maybe they tried to achieve something different and that this does not work here :)

My confusion might be that the docs talk about "important jobs" in several places, yet it's not clear how to identify them or make them important. Examples of what would help me:

  • Do xy to mark a job as important.
  • Observe the xy which tells you that the job is considered important.

My user story is really is this: I want to retain the assets of this job

Actions #6

Updated by okurz almost 3 years ago

  • Subject changed from Important tags don't seem to have any effect to Make it more obvious what "important jobs" are and how one can make jobs important (was: Important tags don't seem to have any effect)
  • Category changed from Support to Feature requests
  • Assignee deleted (okurz)
  • Priority changed from Normal to Low
  • Target version changed from Ready to future

cdywan wrote:

There seems to be quite some confusion with wording. You can only tag builds, not jobs, see http://open.qa/docs/#build_tagging . What you did in https://openqa.opensuse.org/tests/2234385#comments is effectively write a plain comment because the keyword "tag" does not have any special meaning within a job comment. What we could do is mark the keyword "tag" in plain openQA comments and provide some kind of "help text" like Clippy in Microsoft Office to remind people that maybe they tried to achieve something different and that this does not work here :)

My confusion might be that the docs talk about "important jobs" in several places, yet it's not clear how to identify them or make them important. Examples of what would help me:

  • Do xy to mark a job as important.
  • Observe the xy which tells you that the job is considered important.

Ok, good ideas how to improve the descriptions as visible in the webUI as well as the documentation

My user story is really is this: I want to retain the assets of this job

Do you mean "assets" as in the openQA definition of assets meaning isos, qcow files, etc.? Or do you mean logs+results?

Actions #7

Updated by livdywan almost 3 years ago

okurz wrote:

cdywan wrote:

My user story is really is this: I want to retain the assets of this job

Do you mean "assets" as in the openQA definition of assets meaning isos, qcow files, etc.? Or do you mean logs+results?

Personally I'd prefer to retain all assets 😸️ The user story mentioned above is about log files needed for the investigation i.e. autoinst-log and other log files depending on the case

Actions #8

Updated by okurz almost 3 years ago

  • Tags set to doc, ux, ui
  • Subject changed from Make it more obvious what "important jobs" are and how one can make jobs important (was: Important tags don't seem to have any effect) to [doc][ux][ui] Make it more obvious what "important jobs" are and how one can make jobs important (was: Important tags don't seem to have any effect)

So the next task that would need to be done is to explicitly describe in our documentation how one can mark jobs as "important". In #65271#note-91 I have reported the idea to make important jobs visible as such in the webUI. http://open.qa/docs/#_referer_settings_to_auto_mark_important_jobs already mentions that jobs can be marked as important manually but does not explain how.

Actions

Also available in: Atom PDF