5e4b092c53
We have agreed to use term Active Contrubitor rather then Active Technical Contributor, which means it's high time we've aligned naming in our tools and releases documentation to align on term to use. Moreover, it makes even more sense with Extra ACs, since these are designed for ones, who do not contribute in gerrit but with other means, which are usually non-technical. Needed-By: https://review.opendev.org/c/openstack/releases/+/893833 Needed-By: https://review.opendev.org/c/openstack/election/+/893810 Change-Id: Id9f2d182d93a9fbe1357e9ecd4814d49d6eb962f
48 lines
1.4 KiB
YAML
48 lines
1.4 KiB
YAML
- job:
|
|
name: openstack-tox-validate_acs
|
|
parent: openstack-tox-linters
|
|
description: |
|
|
Run the AC checking to show if the current ACs are still valid.
|
|
Foundation membership can change anytime, and we don't want our linter
|
|
jobs to fail due to this, but we want to be informed at all times.
|
|
vars:
|
|
tox_envlist: validate_acs
|
|
|
|
- job:
|
|
name: governance-validate-legacy
|
|
parent: openstack-tox
|
|
description: |
|
|
Run a job to validate the legacy.yaml file to ensure that projects are
|
|
properly retired. This job only runs on legacy.yaml changes to ensure
|
|
that we don't hit OpenDev.org with too many requests without changes.
|
|
files:
|
|
- tools/validate-legacy.py
|
|
- reference/legacy.yaml
|
|
vars:
|
|
tox_envlist: validate-legacy
|
|
|
|
- project:
|
|
templates:
|
|
- build-openstack-docs-pti
|
|
- openstack-python3-jobs
|
|
check:
|
|
jobs:
|
|
- governance-validate-legacy
|
|
- openstack-tox-validate_acs:
|
|
voting: false
|
|
- openstack-tox-linters:
|
|
required-projects:
|
|
- openstack/project-config
|
|
experimental:
|
|
jobs:
|
|
- openstack-tox-validate
|
|
gate:
|
|
jobs:
|
|
- governance-validate-legacy
|
|
- openstack-tox-linters:
|
|
required-projects:
|
|
- openstack/project-config
|
|
promote:
|
|
jobs:
|
|
- promote-governance-tc
|