d49fb788da
Depending on the state of upstream repositories, it's possible the kubernetes repo could change between the ``setup`` and ``run`` phase. Alternatively, something during ``setup`` itself could mangle the repo. Add an option to force clone the kubernetes repo. This gives support for testing on multiple CRI-O branches, realizing some benefit from caching, yet also allows hauling in brand-new-kubernetes for the e2e tests. Signed-off-by: Chris Evich <cevich@redhat.com> |
||
|---|---|---|
| .. | ||
| integration | ||
| requirements.txt | ||
| venv-ansible-playbook.sh | ||