Skip to content

It takes ~50 minutes to build kubernetes from source for Windows presubmits #1955

New issue
New issue
Open
#2041
Open
It takes ~50 minutes to build kubernetes from source for Windows presubmits#1955
#2041
Assignees
tonyzhc
Labels
lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
@mauriciopoppe

Description

@mauriciopoppe
mauriciopoppe
opened on Feb 26, 2025 · edited by mauriciopoppe
Member

Example: https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/kubernetes-sigs_gcp-compute-persistent-disk-csi-driver/1951/pull-gcp-compute-persistent-disk-csi-driver-e2e-windows-2019/1894527667919654912

The integration script is called with

+ /home/prow/go/src/sigs.k8s.io/gcp-compute-persistent-disk-csi-driver/bin/k8s-integration-test ... --kube-version=master ...

Which together with the flag flag.Bool("do-k8s-build", true, "building the driver from source. If false, will fetch precompiled artifacts")

Forces to build k8s from scratch

gcp-compute-persistent-disk-csi-driver/test/k8s-integration/main.go

Lines 330 to 335 in 39a5910

if *doK8sBuild {
klog.Info("Building Kubernetes source")
if err := buildKubernetes(testParams.k8sSourceDir, "quick-release"); err != nil {
return fmt.Errorf("failed to build Kubernetes: %v", err.Error())
}
} else {

Which takes ~50 minutes:

I0225 23:48:36.829509   17242 main.go:331] Building Kubernetes source
...
I0226 00:35:01.275869   17242 utils.go:15] Starting E2E Cluster on GCE

Do we need to build k/k from source or just take the latest CI builds? I think we should take the k/k CI builds, I forgot the reason we build from source.

Activity

sunnylovestiramisu

sunnylovestiramisu commented on Apr 3, 2025

@sunnylovestiramisu
sunnylovestiramisu
on Apr 3, 2025
Contributor

/assign @tonyzhc

k8s-ci-robot
assigned
tonyzhc
on Apr 3, 2025
tonyzhc

tonyzhc commented on Apr 3, 2025

@tonyzhc
tonyzhc
on Apr 3, 2025
Contributor

Where could we access the k/k CI builds?

sunnylovestiramisu

sunnylovestiramisu commented on Apr 3, 2025

@sunnylovestiramisu
sunnylovestiramisu
on Apr 3, 2025
Contributor

@tonyzhc Click into the runs in https://testgrid.k8s.io/provider-gcp-compute-persistent-disk-csi-driver#ci-windows-2019-provider-gcp-compute-persistent-disk-csi-driver

tonyzhc
linked a pull request that will close this issue on Apr 3, 2025
k8s-triage-robot

k8s-triage-robot commented on Jul 2, 2025

@k8s-triage-robot
k8s-triage-robot
on Jul 2, 2025

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-ci-robot
added
lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
on Jul 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

    Development

    Participants

    @mauriciopoppe@k8s-ci-robot@tonyzhc@k8s-triage-robot@sunnylovestiramisu

    Issue actions
      It takes ~50 minutes to build kubernetes from source for Windows presubmits · Issue #1955 · kubernetes-sigs/gcp-compute-persistent-disk-csi-driver