action #91905

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 #88561: [epic] Extend needle version control handling

webui fails to display needles when using a git repository as CASEDIR

Added by dancermak about 1 year ago. Updated about 1 year ago.

Feature requests
Target version:
Start date:
Due date:
% Done:


Estimated time:


The openQA webui implicitly searches for the needles in /var/lib/openqa/share/tests/$DISTRI/needles even when one overrides CASEDIR. The crux in this is, that os-autoinst actually does find the needles in the "correct" location (= $CASEDIR/needles). Only in the webui it looks like no needles could be found, because it does not automatically look in $CASEDIR/needles.

This issue can be reproduced by creating a new job and use a git repository as CASEDIR. I have for instance used, which includes the needles in the needles/ subdir. os-autoinst finds all present needles, but the webui does not.

Related issues

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


#1 Updated by mkittler about 1 year ago

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

#2 Updated by mkittler about 1 year ago

  • Parent task set to #88561

This looks similar to #56789. I've described the general problem (and some ideas to overcome it) with custom needles and the web UI here: #56789#note-21 #56789#note-35

#3 Updated by okurz about 1 year ago

  • Category set to Feature requests
  • Priority changed from Normal to Low
  • Target version set to future

mkittler right, similar to #56789 but not exactly the same as here we have a case of needles that are part of CASEDIR, not a separate repo. Thanks for bringing in the right ticket connections.

dancermak I was not aware that you want to use needles from a custom git repo, would have told you that this feature is not yet supported :D

Also available in: Atom PDF