openstack/requirements
Code Issues Proposed changes

Demote validate-projects to non-voting

Browse Source 
Since we changed the PTI in [1] without depending on [2]  We can't
reliably validate which projects do or do not have the
check-requirements template enabled.

We *could* grovel around in the repo and reproduce a bunch of zuul logic
for finding zuul config or we could just use this as information only
and rely on the core team to validate additions.

[1] https://review.openstack.org/#/c/571520
[2] https://review.openstack.org/#/c/550979

Change-Id: I1a777f67031dfcff02bff1bbff66f06b1618b8a0
This commit is contained in:
Tony Breeds 2018-09-12 13:27:41 +10:00
parent 8bf1b46bd8
commit 996c2788b5
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
.zuul.d/project.yaml
View File

@ -26,7 +26,8 @@
- requirements-tox-py35-check-uc
- requirements-tox-py36-check-uc:
voting: false
- requirements-tox-validate-projects
- requirements-tox-validate-projects:
voting: false
- cross-cinder-py27
- cross-cinder-py35
- cross-glance-py27
@ -75,7 +76,6 @@
- requirements-tox-babel
- requirements-tox-py27-check-uc
- requirements-tox-py35-check-uc
- requirements-tox-validate-projects
- cross-cinder-py27
- cross-cinder-py35
- cross-glance-py27