requirements/.zuul.d/project-template.yaml

- project-template:
    name: check-requirements
    check:
      jobs:
        - requirements-check
    gate:
      jobs:
        - requirements-check

- job:
    name: requirements-check
    parent: unittests
    run: playbooks/requirements-check.yaml
    required-projects:
      - openstack/requirements
    files:
      - ^tools/.*-requires$
      - ^.*requirements.txt$
      - ^.*requirements-py[2,3].txt$
      - playbooks/requirements-check.yaml
Add check-requirements project-template There's no real need to define this in openstack-zuul-jobs when we can define it here with the job definitions. Change-Id: Ic373d1a36a46d1005de1665fe4d04cd197f95e96 2017-10-05 12:25:33 -05:00			`- project-template:`
			`name: check-requirements`
			`check:`
			`jobs:`
Move file lists to requirements-check job definition It's the same list of requirements, and they're universally applicable. Add them to the job definition rather than twice in the project-template. Change-Id: I8dd6ca2f8366ba76bbb51a539c96eac24c461a78 2017-10-10 13:50:50 -05:00			`- requirements-check`
Add check-requirements project-template There's no real need to define this in openstack-zuul-jobs when we can define it here with the job definitions. Change-Id: Ic373d1a36a46d1005de1665fe4d04cd197f95e96 2017-10-05 12:25:33 -05:00			`gate:`
			`jobs:`
Move file lists to requirements-check job definition It's the same list of requirements, and they're universally applicable. Add them to the job definition rather than twice in the project-template. Change-Id: I8dd6ca2f8366ba76bbb51a539c96eac24c461a78 2017-10-10 13:50:50 -05:00			`- requirements-check`
Add check-requirements project-template There's no real need to define this in openstack-zuul-jobs when we can define it here with the job definitions. Change-Id: Ic373d1a36a46d1005de1665fe4d04cd197f95e96 2017-10-05 12:25:33 -05:00
Add requirements-check job This is a straight copy of the original gate-{name}-requirements job, except it copies the script over to the host rather than depending on a baked-in copy of the script. Followups should rework it to stop using zuul-cloner. (jlk) updated to fix pep8 errors so that the patch can land. Change-Id: I734db3b3e4d445e15084d1ca6e60cf2fe392385d 2017-10-02 09:15:41 -05:00			`- job:`
			`name: requirements-check`
			`parent: unittests`
Actually run check-requirements The job definition missed to actually run the written playbook, add it. Change-Id: I4b1140c20c68821eaf0849c9ee551ff9b1c27deb 2017-10-30 07:51:48 +01:00			`run: playbooks/requirements-check.yaml`
Add requirements-check job This is a straight copy of the original gate-{name}-requirements job, except it copies the script over to the host rather than depending on a baked-in copy of the script. Followups should rework it to stop using zuul-cloner. (jlk) updated to fix pep8 errors so that the patch can land. Change-Id: I734db3b3e4d445e15084d1ca6e60cf2fe392385d 2017-10-02 09:15:41 -05:00			`required-projects:`
			`- openstack/requirements`
Move file lists to requirements-check job definition It's the same list of requirements, and they're universally applicable. Add them to the job definition rather than twice in the project-template. Change-Id: I8dd6ca2f8366ba76bbb51a539c96eac24c461a78 2017-10-10 13:50:50 -05:00			`files:`
			`- ^tools/.*-requires$`
			`- ^.*requirements.txt$`
			`- ^.*requirements-py[2,3].txt$`
			`- playbooks/requirements-check.yaml`