Fix e2e test dependency on building k8s
These two should not be tightly-coupled. e.g. for RPM testing, the packages will be built/installed, then e2e tests will run. Having k8s secondarily built/installed will seriously screw with rpm-building and testing. Signed-off-by: Chris Evich <cevich@redhat.com>
This commit is contained in:
parent
369aca6dcf
commit
70b83fd641
2 changed files with 3 additions and 3 deletions
|
@ -1,8 +1,5 @@
|
|||
---
|
||||
|
||||
- name: clone build and install kubernetes
|
||||
include: "build/kubernetes.yml"
|
||||
|
||||
- name: enable and start CRI-O
|
||||
systemd:
|
||||
name: crio
|
||||
|
|
|
@ -31,6 +31,9 @@
|
|||
- integration
|
||||
- e2e
|
||||
tasks:
|
||||
- name: clone build and install kubernetes
|
||||
include: "build/kubernetes.yml"
|
||||
|
||||
- name: clone build and install cri-o
|
||||
include: "build/cri-o.yml"
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue