mirrors/pinniped
1
0
Fork 0
mirror of https://github.com/vmware-tanzu/pinniped.git synced 2026-01-06 21:47:45 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

move manually triggered jobs earlier in main pipeline

Browse Source 
So we can manually trigger them to run in parallel with other
jobs, so we don't have to wait for those other jobs to pass because
they can be flaky sometimes.
This commit is contained in:
Ryan Richard
2025-12-23 14:18:35 -08:00
parent 2d3c1515a0
commit 06f0728479
1 changed files with 6 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
pipelines/main/pipeline.yml
View File

@@ -34,6 +34,7 @@ groups:
- ready-to-release
- name: int-k8s-versions
jobs:
- ready-for-int # this job is auto-triggered, but show it again here to make it easy to see in the UI which versions are ready to go
- run-int-k8s-versions
- integration-test-1.22
- integration-test-1.23
@@ -50,6 +51,7 @@ groups:
- integration-test-1.34
- name: int-misc
jobs:
- ready-for-int # this job is auto-triggered, but show it again here to make it easy to see in the UI which versions are ready to go
- run-int-misc
- integration-test-latest-arm64
- integration-test-idps-firewalled
@@ -63,6 +65,7 @@ groups:
- uninstall-existing-ns-test
- name: int-cloud-providers
jobs:
- ready-for-int # this job is auto-triggered, but show it again here to make it easy to see in the UI which versions are ready to go
- run-int-cloud-providers
- integration-test-gke-rapid
- integration-test-gke-stable
@@ -885,7 +888,7 @@ jobs:
- get: pinniped
version: every
passed:
- ready-for-acceptance
- ready-for-int
# Repeat these from ready-for-int because we want to refer to them also in the "passed"
# constraints for the other resources below, so we can be sure that the pinniped resource
# version has passed these jobs *together* with the other resource versions below.
@@ -918,7 +921,7 @@ jobs:
- get: pinniped
version: every
passed:
- ready-for-acceptance
- ready-for-int
# Repeat these from ready-for-int because we want to refer to them also in the "passed"
# constraints for the other resources below, so we can be sure that the pinniped resource
# version has passed these jobs *together* with the other resource versions below.
@@ -951,7 +954,7 @@ jobs:
- get: pinniped
version: every
passed:
- ready-for-acceptance
- ready-for-int
# Repeat these from ready-for-int because we want to refer to them also in the "passed"
# constraints for the other resources below, so we can be sure that the pinniped resource
# version has passed these jobs *together* with the other resource versions below.