action #166658
closed
QA (public) - coordination #162890: [saga][epic] feature discoverability
coordination #162896: [epic] Job triggering on jobless openQA instances
Trigger os-autoinst-distri-example tests from fresh openQA instances via a button on the index page size:S
Added by okurz 3 months ago.
Updated 3 months ago.
Category:
Feature requests
Description
Motivation¶
Newcomers to openQA on a fresh instance with no jobs should have an easily discoverable step what to try next after bringing up an instance. Let's provide them a simple button to trigger some example tests.
Acceptance criteria¶
- AC1: Have a discoverable way for newcomers how to trigger openQA example jobs over the webUI
- AC2: By default the user does not need to customize any settings and can rely on a default test repository
Suggestions¶
Further details¶
- openQA instances which already have jobs don't need to show the "+" button but it shouldn't harm to still display it and allow access to the feature.
- See #21032
- Copied from action #162899: [timeboxed:20h][spike solution] Trigger os-autoinst-distri-example tests from fresh openQA instances on a "+" button on the index page size:M added
- Related to action #21032: Feature to start new jobs from web interface added
- Subject changed from Trigger os-autoinst-distri-example tests from fresh openQA instances on a "+" button on the index page to Trigger os-autoinst-distri-example tests from fresh openQA instances via a button on the index page size:S
- Description updated (diff)
- Status changed from New to Workable
- Status changed from Workable to In Progress
- Assignee set to mkittler
- Due date set to 2024-10-02
Setting due date based on mean cycle time of SUSE QE Tools
- Status changed from In Progress to Feedback
- Copied to action #167335: Conduct "lessons learned" with Five Why analysis for GRU git cloning related errors added
- Priority changed from Normal to Urgent
- Priority changed from Urgent to Normal
- Status changed from Feedback to Resolved
The fetchneedles changes are now also deploy on OSD and it still works.
I also created an example test via the new feature on o3 and it worked: https://openqa.opensuse.org/tests/4508160
On both - o3 and OSD - the example distribution was already present when I opened the form editor. So I suppose people were actually already trying it out themselves and the initial cloning worked. (The example distribution was only cloned on Sep 23/25 on o3/OSD and it definitely didn't do it manually.)
With that I'm considering this ticket resolved. A further improvement that comes to mind would be to have clickable links on the products page but that's out of scope for this ticket and I think we have a ticket for that somewhere on progress.
- Status changed from Resolved to Feedback
There were questions in slack about the content of "Additional settings" and "Scenario definitions". Apparently from the "?" box it's not completely clear, e.g. one question was, whether the scenario definitions should be a path / url.
Since this is meant for beginners, I think the help boxes can be made a bit more clear.
- Status changed from Feedback to Resolved
The PR has been merged and it covers the points mentioned by @tinita.
Also available in: Atom
PDF