3 # activate the zuul virtual env on system that has tox installed
4 source /opt/venv-zuul/bin/activate
10 # track the upstream zuul HEAD, this may be honestly a little risky
11 # but the validations shouldn't fail often due to upstream changes
12 git clone https://github.com/openstack-infra/zuul --depth 1
15 # calling tox will actually build out a new virtualenv and use that
16 # which is honestly a little silly... but whatever
17 tox -e validate-layout $WORKSPACE/zuul/layout.yaml