-
Notifications
You must be signed in to change notification settings - Fork 791
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate release-master-blocking jobs to k8s-infra-prow-build #841
Comments
This is basically implementaton of kubernetes/test-infra#18549 |
The three jobs that remain are all blocked on #846 |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
I think build-master-fast may be done, I forget if it actually needed kubernetes-ci-images access |
/milestone v1.21 |
/close |
@spiffxp: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Let's use the build cluster setup in #830
blocked by needing write access to gs://kubernetes-release-dev(Migrate jobs away from gs://kubernetes-release-dev #846)blocking by needing write access to gcr.io/kubernetes-ci-imagesblocked by needing write access to gs://kubernetes-release-dev(Migrate jobs away from gs://kubernetes-release-dev #846)blocking by needing write access to gcr.io/kubernetes-ci-imagesblocked by needing write access to gs://kubernetes-release-dev(Migrate jobs away from gs://kubernetes-release-dev #846)may need gcp project with special quota for ingress?turns out it works fine with default gce-projecthttps://testgrid.k8s.io/sig-release-master-blocking#bazel-build-masterblocked by needing write access to gs://kubernetes-release-dev(Migrate jobs away from gs://kubernetes-release-dev #846)would benefit from greenhouse (Setup greenhouse in k8s-infra-prow-build cluster #842) (or needs RBE setup)would benefit from greenhouse(Setup greenhouse in k8s-infra-prow-build cluster #842) doneThe text was updated successfully, but these errors were encountered: