Project

General

Profile

Actions

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.

Status:
Workable
Priority:
Normal
Assignee:
-
Category:
Feature requests
Target version:
Start date:
2024-06-10
Due date:
% Done:

0%

Estimated time:

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 open0 closed)

Related to openQA Project (public) - action #56789: New needles from git repository not working with openqa-clone-custom-git-refspecBlockedokurz2019-09-11

Actions
Related to openQA Project (public) - action #157159: Show version of candidate needles the test ran on in the "diff view" on the test details pageNew

Actions
Actions #1

Updated by okurz 6 months ago

  • Tracker changed from coordination to action
  • Target version changed from Tools - Next to Ready
Actions #2

Updated by okurz 6 months ago

  • 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
Actions #3

Updated by livdywan 5 months ago

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.

Actions #4

Updated by okurz 4 months ago

  • Priority changed from Normal to High
Actions #5

Updated by tinita 4 months ago

  • Assignee set to tinita
Actions #6

Updated by tinita 4 months ago

  • Status changed from Workable to In Progress
Actions #7

Updated by openqa_review 4 months ago

  • Due date set to 2024-09-03

Setting due date based on mean cycle time of SUSE QE Tools

Actions #8

Updated by tinita 4 months ago

  • Status changed from In Progress to Feedback

I tried out the pull request locally and added some notes: https://github.com/os-autoinst/openQA/pull/5175
Still need to understand all of it...

Actions #9

Updated by livdywan 4 months ago

  • Related to action #56789: New needles from git repository not working with openqa-clone-custom-git-refspec added
Actions #10

Updated by livdywan 4 months ago

  • Description updated (diff)
Actions #11

Updated by tinita 4 months ago

  • Related to action #157159: Show version of candidate needles the test ran on in the "diff view" on the test details page added
Actions #12

Updated by tinita 4 months ago

  • 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

Actions #13

Updated by tinita 4 months ago

  • Assignee deleted (tinita)
Actions #14

Updated by livdywan 4 months ago

  • Due date deleted (2024-09-03)
Actions #15

Updated by livdywan 3 months ago

  • 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.

Actions #16

Updated by livdywan 3 months ago

  • Status changed from In Progress to Blocked

Waiting for a response for now

Actions #17

Updated by livdywan 3 months ago

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.

Actions #18

Updated by livdywan 3 months ago

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.

Actions #19

Updated by livdywan 3 months ago

  • Status changed from Blocked to Workable

Scott confirmed the AC's we came up with but seems to have no time to work on this for now. The PR has some conflicts. Maybe this can be considered unblocked.

Actions #20

Updated by ybonatakis 2 months ago

Let's wait for Liv to return from vacation next week!?!

Actions #21

Updated by okurz 2 months ago

  • Priority changed from High to Normal
Actions #22

Updated by livdywan about 2 months ago

  • Status changed from Workable to In Progress

Re-reading the current code and rebasing the PR against the latest upstream

Actions #23

Updated by openqa_review about 2 months ago

  • Due date set to 2024-11-05

Setting due date based on mean cycle time of SUSE QE Tools

Actions #24

Updated by livdywan about 2 months ago

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)
Actions #25

Updated by livdywan about 2 months ago

  • Status changed from In Progress to Workable

Putting this aside for a moment.

Actions #26

Updated by livdywan about 2 months ago

  • 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.

Actions #27

Updated by livdywan 22 days ago

  • Assignee deleted (livdywan)
Actions

Also available in: Atom PDF