QA (public) » openQA Project (public)

Motivation¶

As observed in #179512 as openQA-in-openQA tests show that the inner openQA-in-openQA test cloning the "ping_test" triggers

Mar 26 07:03:25 susetest openqa-gru[12474]: [info] Running cmd: env GIT_SSH_COMMAND=ssh -oBatchMode=yes GIT_ASKPASS= GIT_TERMINAL_PROMPT=false git -C /var/lib/openqa/share/tests/opensuse fetch origin master

which in the case of https://openqa.opensuse.org/tests/4951090/modules/test_running/steps/4 took 15 (!) minutes. Why do we even call that expensive fetch here? Do we need it? It should be enough to use limited "--depth"?

Acceptance Criteria¶

• AC1: Given an openQA instance not needing the full history When a test is cloned/triggered based on a bigger test distribution Then starting a git based test takes significantly less time
• AC2: The full git history is still available on an openQA instance when needed

Suggestions¶

• The relevant call in the inner openQA-in-openQA test is Mar 26 07:03:25 susetest openqa-gru[12474]: [info] Running cmd: env GIT_SSH_COMMAND=ssh -oBatchMode=yes GIT_ASKPASS= GIT_TERMINAL_PROMPT=false git -C /var/lib/openqa/share/tests/opensuse fetch origin master. Why don't we fetch with limited depth like we do in os-autoinst?
• https://github.com/os-autoinst/openQA/blob/master/lib/OpenQA/Git.pm https://github.com/os-autoinst/openQA/blob/master/lib/OpenQA/Task/Git/Clone.pm The fetch is likely initialized from https://github.com/os-autoinst/openQA/blob/master/lib/OpenQA/Task/Git/Clone.pm#L116