Skip to content
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.

Sign up for GitHub

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

Jump to bottom

create or update periodic-kubernetes-bazel-build-canary job to run in k8s-infra-prow-build without RBE #18653

Closed
spiffxp opened this issue Aug 4, 2020 · 19 comments
Closed

create or update periodic-kubernetes-bazel-build-canary job to run in k8s-infra-prow-build without RBE #18653

spiffxp opened this issue Aug 4, 2020 · 19 comments
Labels
area/jobs priority/backlog Higher priority than priority/awaiting-more-evidence. sig/release Categorizes an issue or PR as relevant to SIG Release. sig/testing Categorizes an issue or PR as relevant to SIG Testing.
Milestone
v1.21

Comments

@spiffxp
Copy link
Member

spiffxp commented Aug 4, 2020 •
edited
Loading

This is related to but not explicitly part of #18549
This is also related to kubernetes/k8s.io#846

The equivalent to #18607 but for bazel build instead of bazel test

Since jobs in k8s-infra-prow-build can't write to gs://kubernetes-release-dev, write to gs://k8s-release-dev instead (created via kubernetes/k8s.io#1110)

May need some extra attention to the kubernetes_bazel.py scenario to confirm this job wouldn't attempt to overwrite anything done by the non-canary job
@spiffxp
Copy link
Member Author

spiffxp commented Aug 4, 2020

/sig testing
/sig release
/wg k8s-infra
/area jobs

Can't make this help-wanted until GCS bucket name / project is decided and GCS bucket is created

@k8s-ci-robot k8s-ci-robot added sig/testing Categorizes an issue or PR as relevant to SIG Testing. sig/release Categorizes an issue or PR as relevant to SIG Release. wg/k8s-infra area/jobs labels Aug 4, 2020
@spiffxp
Copy link
Member Author

spiffxp commented Aug 4, 2020

Seeing if we can figure out what the GCS bucket name / project names should be kubernetes/k8s.io#846 (comment)

@spiffxp
Copy link
Member Author

spiffxp commented Aug 4, 2020

Opened kubernetes/k8s.io#1110 with proposal for bucket / project names

@spiffxp spiffxp mentioned this issue Aug 8, 2020
Merged
@spiffxp
Copy link
Member Author

spiffxp commented Aug 8, 2020 •
edited
Loading

#18745 repurposes the canary job to run in k8s-infra-prow-build without RBE and to write to the gs://k8s-release-dev bucket created via kubernetes/k8s.io#1110

@spiffxp
Copy link
Member Author

spiffxp commented Aug 8, 2020

/assign

@spiffxp spiffxp mentioned this issue Aug 25, 2020
Merged
@spiffxp
Copy link
Member Author

spiffxp commented Aug 25, 2020

I checked in on https://testgrid.k8s.io/sig-testing-canaries#bazel-build and found it's been failing continuously because of a lack of gcloud. Whoops.

PR to correct the image here #18992

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 24, 2020
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Dec 24, 2020
@spiffxp
Copy link
Member Author

spiffxp commented Jan 7, 2021

/remove-lifecycle rotten

@k8s-ci-robot k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Jan 7, 2021
@spiffxp
Copy link
Member Author

spiffxp commented Jan 19, 2021

https://testgrid.k8s.io/sig-testing-canaries#bazel-build is now passing, not quite sure what next steps are

@spiffxp
Copy link
Member Author

spiffxp commented Jan 28, 2021 •
edited
Loading

Next steps are:

  • decide whether we care about writing to gs://kubernetes-release-dev and gcr.io/kubernetes-ci-images (aka determine whether anything consumes the artifacts produced by this job in those locations)
  • if we do, we'll have to make a new copy writing to k8s-release-dev, and keep the current job around (same issue as ci-kubernetes-build jobs)
  • if we don't, migrate to writing to k8s-release-dev

@spiffxp
Copy link
Member Author

spiffxp commented Jan 28, 2021

/unassign

@spiffxp spiffxp mentioned this issue Jan 28, 2021
Closed
@spiffxp
Copy link
Member Author

spiffxp commented Feb 19, 2021

/priority backlog

@k8s-ci-robot k8s-ci-robot added the priority/backlog Higher priority than priority/awaiting-more-evidence. label Feb 19, 2021
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 20, 2021
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jun 19, 2021
@spiffxp
Copy link
Member Author

spiffxp commented Jul 9, 2021

/close
Closing as obviated by kubernetes/enhancements#2420

@k8s-ci-robot
Copy link
Contributor

@spiffxp: Closing this issue.

In response to this:

/close
Closing as obviated by kubernetes/enhancements#2420

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.

@spiffxp
Copy link
Member Author

spiffxp commented Jul 9, 2021

/remove-lifecycle rotten

@k8s-ci-robot k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Jul 9, 2021
@spiffxp
Copy link
Member Author

spiffxp commented Jul 16, 2021

/milestone v1.21

@k8s-ci-robot k8s-ci-robot added this to the v1.21 milestone Jul 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/jobs priority/backlog Higher priority than priority/awaiting-more-evidence. sig/release Categorizes an issue or PR as relevant to SIG Release. sig/testing Categorizes an issue or PR as relevant to SIG Testing.
Projects
None yet
Milestone
v1.21
Development

No branches or pull requests
3 participants
@spiffxp @k8s-ci-robot @fejta-bot