Re-integrate build-image "test" back into the test suites #444
Assignees
Labels
Comments
|
@Ark-kun, what is the status on this? Can we close? |
|
This has been completed. |
Linchin
pushed a commit
to Linchin/pipelines
that referenced
this issue
Apr 11, 2023
…and E2E clusters (kubeflow#512) * cleanup_ci needs to use different expiration times for auto deployed and E2E clusters * The auto deployed clusters are now using unique names rather than being recycled and we rely on cleanup_ci.py to GC old auto-deployments (kubeflow#444) * To support this we need to use variable expiration times. * Deployments created by tests should expire as soon as the test is done (so 1-2 hours) * But auto-deployed clusters need to live longer * There are only refreshed periodically by a cron job (~8 hours) we don't want to delete the cluster before a new one is deployed because we need a cluster for the example tests * We want to leave the clusters up as long as we can to facilitate debugging by people working on example tests. Related to kubeflow#444 * Address reviewer comments.
magdalenakuhn17
pushed a commit
to magdalenakuhn17/pipelines
that referenced
this issue
Oct 22, 2023
HumairAK
pushed a commit
to red-hat-data-services/data-science-pipelines
that referenced
this issue
Mar 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reasons:
run_after_success: Prow constantly reruns successful tests and tide does not put PRs in merge pool kubernetes/test-infra#10244 (comment)The text was updated successfully, but these errors were encountered: