d4b8abae78
While having a native Zuul job for testing is really nice, but it puts some imitations, like being unable to use external collections which a role might depend on. In order to overcome these limitations, molecule test job was added, which does exactly same set of actions, except vlan configuration. We also switch ansible-lint job to track molecule playbook. Change-Id: I219cc1c06c49a6710edfd6104580cdc01b768ab0
36 lines
618 B
YAML
36 lines
618 B
YAML
---
|
|
|
|
- nodeset:
|
|
name: debian-buster-2-node
|
|
nodes:
|
|
- name: primary
|
|
label: debian-buster
|
|
- name: secondary
|
|
label: debian-buster
|
|
groups:
|
|
- name: switch
|
|
nodes:
|
|
- primary
|
|
- name: peers
|
|
nodes:
|
|
- primary
|
|
- secondary
|
|
|
|
- job:
|
|
name: ffrouting-deploy
|
|
parent: base
|
|
run: tests/test.yml
|
|
nodeset: debian-buster-2-node
|
|
|
|
- project:
|
|
check:
|
|
jobs:
|
|
- ffrouting-deploy
|
|
- tox-linters
|
|
- tox-molecule
|
|
gate:
|
|
jobs:
|
|
- ffrouting-deploy
|
|
- tox-linters
|
|
- tox-molecule
|