Open upodroid opened 1 year ago
/priority important-soon /sig testing
Omitting build flag doesn't work because the shell scripts are looking for cloudprovider gcp binaries.
kubetest2 gce \
-v=2 \
--repo-root="$REPO_ROOT" \
--build \
--up \
--down \
--test=ginkgo \
--master-size=e2-standard-2 \
--node-size=e2-standard-2 \
-- \
--test-package-version="${TEST_PACKAGE_VERSION}" \
--focus-regex='Secrets should be consumable via the environment' \
--skip-regex='\[Driver:.gcepd\]|\[Slow\]|\[Serial\]|\[Disruptive\]|\[Flaky\]|\[Feature:.+\]' \
--timeout=60m
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
Is this still needed?
Every time
kubetest2 gce
is ran, the entire k/cloud-provider-gcp repo is built when all we are doing in some situations is either testing a prebuilt version of Kubernetes or building just k/k code.I want to eliminate the
legacy-mode
flag by copying all the cluster bootstrap logic to thek/cloud-provider-gcp
repo.We are wasting 10 minutes building on every run building k/cloud-provider-gcp when we don't need it.
https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_kubetest2/236/pull-kubetest2-gce-build-up-down/1689755384274751488 Is a good example.