action #162035
open
coordination #58184: [saga][epic][use case] full version control awareness within openQA
coordination #88561: [epic] Extend needle version control handling
Support development of "Use needles from correct ref of NEEDLES_DIR" https://github.com/os-autoinst/openQA/pull/5175 size:M
Added by okurz 6 months ago.
Updated 22 days ago.
Category:
Feature requests
Description
Motivation¶
It can be confusing to not see candidate needles on the web UI that were not available at the time the test was being executed.
Acceptance criteria¶
- AC1: The candidates view on the test details pages shows candidate needles of the version that was used when the test was executed.
- AC2: Temporary needles are cleaned up (instantly or on a schedule)
- AC3: The needle editor still shows the last candidates. One might optionally show there the candidates at the time the test ran as well.
Suggestions¶
- Read exactly what the PR "Use needles from correct ref of NEEDLES_DIR" is about
- Checkout #154783-10 and further comments for what's missing
- Review the code and make suggestions or add changes yourself to get it merged
- Make sure test coverage is appropriate (PR does not look like it atm.)
- If any work becomes too much work then split out into separate explicit tickets and provide explicit feedback to the PR author about what is expected from them and what can be expected from us
- Saying no to a feature is always an option too
- Consider a NEEDLES_DIR being a different repo/remote entirely (e.g. a pull request) (although this is not strictly required it would be good to ensure we could also support it)
- Read #56789 again
Related issues
2 (2 open — 0 closed)
- Tracker changed from coordination to action
- Target version changed from Tools - Next to Ready
- Subject changed from Support development of https://github.com/os-autoinst/openQA/pull/5175 to Support development of "Use needles from correct ref of NEEDLES_DIR" https://github.com/os-autoinst/openQA/pull/5175 size:M
- Description updated (diff)
- Status changed from New to Workable
I would guess there were more urgent tickets preventing someone from picking this up within our usual 30 days. If you took a look and had open questions, might be worth discussing again, though.
- Priority changed from Normal to High
- Status changed from Workable to In Progress
- Due date set to 2024-09-03
Setting due date based on mean cycle time of SUSE QE Tools
- Status changed from In Progress to Feedback
- Related to action #56789: New needles from git repository not working with openqa-clone-custom-git-refspec added
- Description updated (diff)
- Related to action #157159: Show version of candidate needles the test ran on in the "diff view" on the test details page added
- Status changed from Feedback to Workable
It looks like I can't work on it in the very near future, so putting it back to Workable for now
- Assignee deleted (
tinita)
- Due date deleted (
2024-09-03)
- Status changed from Workable to In Progress
- Assignee set to livdywan
Let's see if I can drive this. To start out I'm going to check if the OP had a chance to review the acceptance criteria we came up with.
- Status changed from In Progress to Blocked
Waiting for a response for now
livdywan wrote in #note-16:
Waiting for a response for now
No response so far. Might just need to wait for Scott to make time for it.
Waiting for a response for now
No response so far. Might just need to wait for Scott to make time for it.
Asked once more.
- Status changed from Blocked to Workable
Let's wait for Liv to return from vacation next week!?!
- Priority changed from High to Normal
- Status changed from Workable to In Progress
Re-reading the current code and rebasing the PR against the latest upstream
- Due date set to 2024-11-05
Setting due date based on mean cycle time of SUSE QE Tools
Discussed in the unblock
- https://github.com/os-autoinst/openQA/pull/5175 rebased
- I dropped the use of File::Touch which we don't depend on (I was confused by the CI results but the fix was straightforward)
- Looking into coverage gaps which are now also visible on the PR
- Most importantly the candidates view
- Needle editing looks to be using the new code, too, but is not required
- Check how to reproduce the new feature manually e.g. using NEEDLES_DIR/other test vars (same in unit tests)
- Status changed from In Progress to Workable
Putting this aside for a moment.
- Due date deleted (
2024-11-05)
I won't be able to have this wrapped up and deployed by the due date. Unless somebody else wants to take over in my absence and make that happen.
- Assignee deleted (
livdywan)
Also available in: Atom
PDF