action #97112
coordination #58184: [saga][epic][use case] full version control awareness within openQA, e.g. user forks and branches, fully versioned test schedules and configuration settings
coordination #94750: [epic] Support needles from git-cloned or separate repo if casedir points to a git-repo
Support relative needle directories together with tests checked out from git
0%
Description
Motivation¶
See the unexpected current default behaviour in #94735
Acceptance criteria¶
- AC1: For test distributions that include needles when tests triggered with git URL pointing to test repo by default needles from that repo should be used and not a non-git default repo
Suggestions¶
Discussed with mkittler and cdywan. We propose to shift more logic into os-autoinst and implement an additional keyword so that os-autoinst looks up only a fallback needles repo in case needles are not found anywhere else. Also we assume that os-autoinst is easier to change and maintain. The current proposal is to use NEEDLES_DIR=[<keyword>]<dir>, e.g. NEEDLES_DIR=[fallback]my/productdir/needles for a relative fallback directory. The only suggested to be supported keyword should be "fallback" for now.
- In os-autoinst parse keyword from
NEEDLES_DIR - If "[fallback]" then try to find needles in all default paths, e.g. subdir of casedir, productdir, etc., only if not found look up in the fallback one
- Prepare setting fallback in openQA Worker/Engines/isotovideo.pm but do not merge yet
- Deploy new feature in os-autoinst
- Wait grace period
- Deploy openQA feature
Related issues
History
#1
Updated by okurz almost 2 years ago
Updated by - Copied from action #94735: needles not found in `needles` subdirectory when CASEDIR is a git repository added