Project

General

Profile

Actions

coordination #33745

closed

coordination #58184: [saga][epic][use case] full version control awareness within openQA

coordination #94750: [epic] Support needles from git-cloned or separate repo if casedir points to a git-repo

[epic] Improve handling of external Git repositories (for needles)

Added by mkittler over 6 years ago. Updated 18 days ago.

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

100%

Estimated time:
(Total: 0.00 h)

Description

Motivation

When working on #9906 (Show added/updated needles in editor) general problems regarding how openQA handles the Git repository came up. This ticket is only meant to describe the general problems and might be used for further discussion.

Current way it works

  1. There are two ways openQA can detect a new needle:
    1. running a job which uses the needle
    2. the needle is created in the needle editor
  2. There is a Gru task which periodically checks whether needle files are still present. It doesn't delete any entries in the openQA database. Only the absence of files is tracked. This will also not detect any new needles.
  3. When creating a needle via the needle editor, openQA commits that change to the Git repository. It also instantly creates a database entry for that needle.
  4. When removing a needle via the web interface, openQA commits the deletion to the Git repository or just removes the file. The needle is also deleted from the internal database if the needle files could be removed successfully.

Problems

  1. The feature 'Show added/updated needles in editor' only works when the new needle has been created via the needle editor or at least one job loading it has been started.
  2. When restarting a job, newly created needles are not instantly available because it takes shortly for fetch_needles to catch up (unless they are added via the needle editor). Not relevant when specifying a Git-URL via NEEDLES_DIR.
  3. Can a test immediately pick up new needles created via the needle editor when continuing in the developer mode when NEEDLES_DIR is set to a Git-URL? (#162647)
  4. In 3. and 4. (under "Current way it works") conflicts can occur. In this case openQA will push to another branch. Needles could get lost in that case. (#70774)

Subtasks 1 (0 open1 closed)

action #162647: Ensure the developer mode and its feature to reload newly created needles work when NEEDLES_DIR is a Git sourceResolvedmkittler2024-06-20

Actions

Related issues 2 (1 open1 closed)

Related to openQA Project - action #9906: Show added/updated needles in editorResolvedmkittler2015-12-14

Actions
Related to openQA Project - action #70774: save_needle Minion tasks fail frequently and needles could get lostNew2020-09-01

Actions
Actions #1

Updated by okurz over 6 years ago

  • Description updated (diff)
  • Category set to Feature requests

Nicely written, looks good

Actions #2

Updated by mkittler over 6 years ago

  • Related to action #9906: Show added/updated needles in editor added
Actions #3

Updated by mkittler over 6 years ago

  • Description updated (diff)
Actions #4

Updated by mkittler over 6 years ago

  • Description updated (diff)
Actions #5

Updated by okurz over 4 years ago

  • Parent task set to #58184
Actions #6

Updated by okurz almost 4 years ago

  • Target version set to Ready
Actions #7

Updated by mkittler almost 4 years ago

  • Related to action #70774: save_needle Minion tasks fail frequently and needles could get lost added
Actions #8

Updated by okurz over 3 years ago

  • Target version changed from Ready to future
Actions #9

Updated by okurz about 3 years ago

  • Parent task changed from #58184 to #94750
Actions #10

Updated by okurz 25 days ago

  • Target version changed from future to Ready
Actions #11

Updated by okurz 24 days ago

  • Subject changed from Improve handling external Git repositories (for needles) to [epic] Improve handling of external Git repositories (for needles)
  • Description updated (diff)
  • Status changed from New to Workable
  • Assignee set to mkittler
  • Priority changed from Low to Normal
Actions #12

Updated by mkittler 24 days ago

  • Subtask #162647 added
Actions #13

Updated by mkittler 24 days ago

I created ticket #162647 for problem 3. Ticket #70774 is already covering problem 4. I would only create a ticket for problem 1 when we decide it is worth it. Problem 2 seems no longer relevant as we should push using Git-URLs instead.

Actions #14

Updated by mkittler 24 days ago

  • Description updated (diff)
Actions #15

Updated by okurz 24 days ago

  • Status changed from Workable to Blocked

alright, thx. I guess with that we can block on #162647 and afterwards resolve as the rest is covered in the other tickets you mentioned.

Actions #16

Updated by okurz 18 days ago

  • Tracker changed from action to coordination
  • Status changed from Blocked to Resolved
Actions

Also available in: Atom PDF