zuul-jobs/zuul.d/project.yaml
Radosław Piliszek 4887ac0b39 Use the default minikube driver (docker)
To fix issues with the upstream way of doing it directly on the
host.
This also makes the logic much simpler.
Fixes at least the CoreDNS containers not starting issue.

Change-Id: I6ef651b1df972c7021d9f304a2479ae97e51696c
2024-02-12 22:26:00 +01:00

53 lines
1.9 KiB
YAML

- project:
check:
jobs: &check-jobs
- nox-linters
# cross-testing with component-template
- nebulous-component-template-hadolint:
vars:
zuul_work_dir: src/opendev.org/nebulous/component-template
required-projects:
- nebulous/component-template
files:
- ^playbooks/hadolint/
- ^roles/ensure-hadolint/
- ^roles/hadolint/
- nebulous-component-template-helm-lint:
vars:
zuul_work_dir: src/opendev.org/nebulous/component-template
required-projects:
- nebulous/component-template
files:
# NOTE: hackish way to only run it when its definition changes
# as no files exist in this repo that control its behaviour
- ^never-existing-file$
- nebulous-component-template-apply-helm-charts:
vars:
zuul_work_dir: src/opendev.org/nebulous/component-template
required-projects:
- nebulous/component-template
files: &nebulous-component-template-apply-helm-charts-files
- ^playbooks/helm/
- ^playbooks/kubernetes/
- ^roles/check-pod-restarts/
- ^roles/collect-kubernetes-pods-logs/
- ^roles/collect-kubernetes-state/
- ^roles/ensure-minikube/
- opendev-buildset-registry:
files: *nebulous-component-template-apply-helm-charts-files
# cross-testing with library-template
- nebulous-library-template-build-java-libraries:
vars:
zuul_work_dir: src/opendev.org/nebulous/library-template
required-projects:
- nebulous/library-template
files:
- ^playbooks/java-libraries/
- ^roles/install-jdk/
- ^roles/install-maven/
gate:
jobs: *check-jobs