action #162899
closed
QA - coordination #162890: [saga][epic] feature discoverability
coordination #162896: [epic] Job triggering on jobless openQA instances
[timeboxed:20h][spike solution] Trigger os-autoinst-distri-example tests from fresh openQA instances on a "+" button on the index page size:M
Added by okurz 5 months ago.
Updated about 1 month ago.
Category:
Feature requests
Description
Goals¶
- G1: Have a discoverable way for newcomers how to trigger openQA jobs
- G2: We know what the requirements or challenges here about triggering on the webUI itself, e.g. user permissions, and such
Suggestions¶
- Target version changed from Tools - Next to Ready
- Subject changed from [timeboxed:20h][spike solution] Trigger os-autoinst-distri-example tests from fresh openQA instances on a "+" button on the index page to [timeboxed:20h][spike solution] Trigger os-autoinst-distri-example tests from fresh openQA instances on a "+" button on the index page size:M
- Status changed from New to Workable
- Assignee set to ybonatakis
- Status changed from Workable to In Progress
- Due date set to 2024-09-17
Setting due date based on mean cycle time of SUSE QE Tools
Action items:
- Clean up the proof of concept a little (typos, js in its own file) and propose a draft PR
- Clarify G2 - as it seems there's no special considerations you can probably just say that nothing special is needed here as it simply uses requests like we already do elsewhere?
- Take a screenshot and put it in the PR for easy demonstration of what you came up with
- File a follow-up ticket for the implementation (not timeboxed, not spike)
- Status changed from In Progress to Feedback
livdywan wrote in #note-7:
Action items:
- Clean up the proof of concept a little (typos, js in its own file) and propose a draft PR
I cleanup a bit. Mainly js and html stuff
- Clarify G2 - as it seems there's no special considerations you can probably just say that nothing special is needed here as it simply uses requests like we already do elsewhere?
AFAIU the user doesnt need any particular requirements. Once he/she log in, he/she should be able to run the os-autoinst-distri-example (or any other). I was able to run the job as admin and as operator.
I run test from main repo as well as from other branch https://github.com/os-autoinst/os-autoinst-distri-example#training
- Take a screenshot and put it in the PR for easy demonstration of what you came up with
Done. A small mp4 video
- File a follow-up ticket for the implementation (not timeboxed, not spike)
TBD
#166610 new followup ticket to bring this in reality
- Precedes action #166610: Trigger custom tests from openQA instances on a "+" button on the index page added
- Status changed from Feedback to Resolved
I provided a PR with suggestions and created a follow up issue. I dont see any crazy challenges in implemented this. ofc considering we want to replace jqueries the implementation might wait to avoid conflicts.
I also found this feature useful, as i used it while I was working in backend and I could take advantage of it and run a job in a sensible, quick and easy way
PR has unresolved feedback which might be considered for the actual implementation. I will have to respond on those
- Copied to action #166658: Trigger os-autoinst-distri-example tests from fresh openQA instances via a button on the index page size:S added
- Due date deleted (
2024-09-17)
Also available in: Atom
PDF