action #166658
closedQA (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
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¶
- See what was done in https://github.com/os-autoinst/openQA/pull/5914
- Add a "+" button probably in the menu bar or a floating + button and provide screenshots in a draft PR
- Add a new blank page offering to schedule example tests
- Use https://github.com/os-autoinst/os-autoinst-distri-example/blob/main/.github/workflows/openqa.yml#L26 with the "schedule" API route
- Make the default tests repo configurable (for an admin to set, not in the web UI)
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
Updated by okurz 3 months ago
- 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
Updated by okurz 3 months ago
- Related to action #21032: Feature to start new jobs from web interface added
Updated by okurz 3 months ago
- 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
Updated by openqa_review 3 months ago
- Due date set to 2024-10-02
Setting due date based on mean cycle time of SUSE QE Tools
Updated by tinita 3 months ago
https://openqa.opensuse.org/tests/4500449#step/test_distribution/3
The initial clone still needs a branch name
Updated by mkittler 3 months ago
This works again after https://github.com/os-autoinst/openQA/pull/5940, see e.g. https://openqa.opensuse.org/tests/4504077#step/test_distribution/4.
I ran fetchneedles on o3 and OSD just like cron would do and haven't encountered any errors, e.g.:
sudo -u geekotest bash -c 'env updateall=1 force=1 /usr/share/openqa/script/fetchneedles'
martchus@ariel:~> echo $?
0
I'll have to re-conduct the test later on OSD because my changes haven't been deployed there.
Updated by okurz 3 months ago
Related: https://bugzilla.suse.com/show_bug.cgi?id=1230953. I would like us to understand why a submission ends up failing in Tumbleweed when we run very similar tests in https://openqa.opensuse.org/group_overview/24 as part of the release pipelines. Do you have an idea?
Updated by okurz 3 months ago
- Copied to action #167335: Conduct "lessons learned" with Five Why analysis for GRU git cloning related errors added
Updated by okurz 3 months ago ยท Edited
- Priority changed from Normal to Urgent
Next to #166658-10 there were more significant problems observed on o3, see https://suse.slack.com/archives/C02CANHLANP/p1727237231866739 and https://matrix.to/#/!dRljORKAiNJcGEDbYA:opensuse.org/$ZqnHKAJ3VZEn2R57ynsS7UozSKC63TK3BqtZGJZ2ERA (https://app.element.io/#/room/#openqa:opensuse.org) and failures in https://gitlab.suse.de/openqa/scripts-ci/-/pipelines
Updated by mkittler 3 months ago
- 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.
Updated by tinita 3 months ago
- 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.