starlingx/virt
Code Issues Proposed changes

Use shared zuul stx-tox-{linters,pep8}

Browse Source 
Previous commit defined a local zuul job to run tox linters. That job
was badly named, as the names are supposed to be globally-unique.

Solution: remove local job definition and call stx-tox-{linters,pep8}
defined by the Depends-On review.

Story: 2011326
Task: 51548

Depends-On: https://review.opendev.org/c/starlingx/zuul-jobs/+/939454

Change-Id: I7f4c4859efcfc50f91de51b76956e1cfce681fcb
Signed-off-by: Davlet Panech <davlet.panech@windriver.com>
This commit is contained in:
Davlet Panech 2025-01-16 16:11:00 -05:00
parent a0722defaa
commit 71a8a54b56
1 changed files with 4 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
.zuul.yaml
View File

@ -5,25 +5,18 @@
- stx-release-notes-jobs
check:
jobs:
- local-tox-pep8
- openstack-tox-linters
- stx-tox-pep8
- stx-tox-linters
- stx-virt-pylint
gate:
jobs:
- local-tox-pep8
- openstack-tox-linters
- stx-tox-pep8
- stx-tox-linters
- stx-virt-pylint
post:
jobs:
- stx-virt-upload-git-mirror
- job:
name: local-tox-pep8
parent: openstack-tox-pep8
description: |
Run Tox pep8 tests on debian-bullseye
nodeset: debian-bullseye
# This is the common base job definition for StarlingX flock services
- job:
name: flock-devstack-virt-base