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>
63 lines
1.3 KiB
YAML
63 lines
1.3 KiB
YAML
- hosts: all
|
|
remote_user: root
|
|
vars_files:
|
|
- "{{ playbook_dir }}/vars.yml"
|
|
tags:
|
|
- setup
|
|
tasks:
|
|
- name: set up the system
|
|
include: system.yml
|
|
|
|
- name: install Golang tools
|
|
include: golang.yml
|
|
|
|
- name: clone build and install bats
|
|
include: "build/bats.yml"
|
|
|
|
- name: clone build and install cri-tools
|
|
include: "build/cri-tools.yml"
|
|
|
|
- name: clone build and install kubernetes
|
|
include: "build/kubernetes.yml"
|
|
|
|
- name: clone build and install runc
|
|
include: "build/runc.yml"
|
|
|
|
- name: clone build and install networking plugins
|
|
include: "build/plugins.yml"
|
|
|
|
- hosts: all
|
|
remote_user: root
|
|
vars_files:
|
|
- "{{ playbook_dir }}/vars.yml"
|
|
tags:
|
|
- integration
|
|
- e2e
|
|
tasks:
|
|
- name: clone build and install cri-o
|
|
include: "build/cri-o.yml"
|
|
|
|
- hosts: all
|
|
remote_user: root
|
|
vars_files:
|
|
- "{{ playbook_dir }}/vars.yml"
|
|
tags:
|
|
- integration
|
|
tasks:
|
|
- name: run cri-o integration tests
|
|
include: test.yml
|
|
|
|
- hosts: all
|
|
remote_user: root
|
|
vars_files:
|
|
- "{{ playbook_dir }}/vars.yml"
|
|
tags:
|
|
- e2e
|
|
tasks:
|
|
- name: clone build and install kubernetes
|
|
include: "build/kubernetes.yml"
|
|
vars:
|
|
force_clone: True
|
|
|
|
- name: run k8s e2e tests
|
|
include: e2e.yml
|