Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -264,7 +264,7 @@ tests:
- as: e2e-kubevirt-metal-ovn
capabilities:
- intranet
cron: 31 0 * * 0
cron: 0 0 17 5 *
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All 10 jobs share the same cron (0 0 17 5 *), so they'll all fire at midnight on May 17 simultaneously. That could overload the CI nodes, especially the metal jobs on equinix-ocp-hcp. Could we spread them across different hours to avoid the spike?

steps:
cluster_profile: equinix-ocp-hcp
env:
Expand All @@ -288,7 +288,7 @@ tests:
- as: e2e-kubevirt-metal-ovn-disconnected
capabilities:
- intranet
cron: 23 0 * * 6
cron: 0 0 17 5 *
steps:
cluster_profile: equinix-ocp-hcp
env:
Expand Down Expand Up @@ -319,7 +319,7 @@ tests:
TEST_SUITE: openshift/conformance/parallel/minimal
workflow: hypershift-kubevirt-azure-conformance
- as: e2e-kubevirt-aws-ovn
cron: 0 0,6,12,18 * * *
cron: 0 0 17 5 *
steps:
cluster_profile: openshift-org-aws
env:
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -285,7 +285,7 @@ tests:
- as: e2e-kubevirt-metal-ovn
capabilities:
- intranet
cron: 0 0 * * 0
cron: 0 0 17 5 *
steps:
cluster_profile: equinix-ocp-hcp
env:
Expand All @@ -298,7 +298,7 @@ tests:
- as: e2e-kubevirt-metal-ovn-disconnected
capabilities:
- intranet
cron: 0 4 * * 1
cron: 0 0 17 5 *
steps:
cluster_profile: equinix-ocp-hcp
env:
Expand Down Expand Up @@ -337,7 +337,7 @@ tests:
TEST_SUITE: openshift/conformance/parallel/minimal
workflow: hypershift-kubevirt-azure-conformance
- as: e2e-kubevirt-aws-ovn
cron: 0 0,6,12,18 * * *
cron: 0 0 17 5 *
steps:
cluster_profile: openshift-org-aws
env:
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -263,7 +263,7 @@ tests:
- as: e2e-kubevirt-metal-ovn
capabilities:
- intranet
cron: 0 4 * * *
cron: 0 0 17 5 *
steps:
cluster_profile: equinix-ocp-hcp
env:
Expand All @@ -282,7 +282,7 @@ tests:
- as: e2e-kubevirt-metal-ovn-disconnected
capabilities:
- intranet
cron: 0 8 * * *
cron: 0 0 17 5 *
steps:
cluster_profile: equinix-ocp-hcp
env:
Expand Down Expand Up @@ -385,7 +385,7 @@ tests:
TEST_SUITE: openshift/conformance/parallel/minimal
workflow: hypershift-kubevirt-azure-conformance
- as: e2e-kubevirt-aws-ovn
cron: 0 0,6,12,18 * * *
cron: 0 0 17 5 *
steps:
cluster_profile: openshift-org-aws
env:
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -262,7 +262,7 @@ tests:
TEST_SUITE: openshift/conformance/parallel/minimal
workflow: hypershift-kubevirt-azure-conformance
- as: e2e-kubevirt-aws-ovn
cron: 0 0,6,12,18 * * *
cron: 0 0 17 5 *
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The same kubevirt jobs (e2e-kubevirt-aws-ovn, e2e-kubevirt-metal-ovn, e2e-kubevirt-metal-ovn-disconnected) are still running on active schedules in release-4.23 and 5.0. If the kubevirt infra issues affect all releases, those are still burning CI time. Were 4.23/5.0 intentionally left out?

steps:
cluster_profile: openshift-org-aws
env:
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -1326,7 +1326,7 @@ periodics:
secretName: result-aggregator
- agent: kubernetes
cluster: build01
cron: 0 0,6,12,18 * * *
cron: 0 0 17 5 *
decorate: true
decoration_config:
skip_cloning: true
Expand Down Expand Up @@ -1743,7 +1743,7 @@ periodics:
secretName: result-aggregator
- agent: kubernetes
cluster: build03
cron: 31 0 * * 0
cron: 0 0 17 5 *
decorate: true
decoration_config:
skip_cloning: true
Expand Down Expand Up @@ -1827,7 +1827,7 @@ periodics:
secretName: result-aggregator
- agent: kubernetes
cluster: build03
cron: 23 0 * * 6
cron: 0 0 17 5 *
decorate: true
decoration_config:
skip_cloning: true
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -1492,7 +1492,7 @@ periodics:
secretName: result-aggregator
- agent: kubernetes
cluster: build01
cron: 0 0,6,12,18 * * *
cron: 0 0 17 5 *
decorate: true
decoration_config:
skip_cloning: true
Expand Down Expand Up @@ -1909,7 +1909,7 @@ periodics:
secretName: result-aggregator
- agent: kubernetes
cluster: build03
cron: 0 0 * * 0
cron: 0 0 17 5 *
decorate: true
decoration_config:
skip_cloning: true
Expand Down Expand Up @@ -1993,7 +1993,7 @@ periodics:
secretName: result-aggregator
- agent: kubernetes
cluster: build03
cron: 0 4 * * 1
cron: 0 0 17 5 *
decorate: true
decoration_config:
skip_cloning: true
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -1658,7 +1658,7 @@ periodics:
secretName: result-aggregator
- agent: kubernetes
cluster: build01
cron: 0 0,6,12,18 * * *
cron: 0 0 17 5 *
decorate: true
decoration_config:
skip_cloning: true
Expand Down Expand Up @@ -2075,7 +2075,7 @@ periodics:
secretName: result-aggregator
- agent: kubernetes
cluster: build03
cron: 0 4 * * *
cron: 0 0 17 5 *
decorate: true
decoration_config:
skip_cloning: true
Expand Down Expand Up @@ -2159,7 +2159,7 @@ periodics:
secretName: result-aggregator
- agent: kubernetes
cluster: build03
cron: 0 8 * * *
cron: 0 0 17 5 *
decorate: true
decoration_config:
skip_cloning: true
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -1413,7 +1413,7 @@ periodics:
secretName: result-aggregator
- agent: kubernetes
cluster: build01
cron: 0 0,6,12,18 * * *
cron: 0 0 17 5 *
decorate: true
decoration_config:
skip_cloning: true
Expand Down