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:
Chris Evich 2017-11-03 15:37:37 -04:00
parent 369aca6dcf
commit 70b83fd641
2 changed files with 3 additions and 3 deletions

View file

@ -1,8 +1,5 @@
--- ---
- name: clone build and install kubernetes
include: "build/kubernetes.yml"
- name: enable and start CRI-O - name: enable and start CRI-O
systemd: systemd:
name: crio name: crio

View file

@ -31,6 +31,9 @@
- integration - integration
- e2e - e2e
tasks: tasks:
- name: clone build and install kubernetes
include: "build/kubernetes.yml"
- name: clone build and install cri-o - name: clone build and install cri-o
include: "build/cri-o.yml" include: "build/cri-o.yml"