Use K8s Infra GCS bucket for uploading release artifacts #616
Assignees
Labels
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Comments
|
All releases have been uploaded to the new bucket! Backfill log: $ time gh2gcs --log-level debug --org kubernetes-sigs --repo cri-tools --bucket k8s-artifacts-cri-tools --release-dir release |
|
And here's a current listing of the bucket contents: |
|
@saschagrunert -- I'll leave you to handle the k/k re-revert of kubernetes/kubernetes#91239, and I'll take care of the k/release changes. |
Sounds good, thank you! I'll re-open the PR and change the scripts to point to the new location. |
|
@saschagrunert -- FYI, you'll want to cherry pick the bucket location change in kubernetes/kubernetes#91564 as well. |
This was referenced Jun 2, 2020
|
Yep, the changes for the master has been merged. The release branch PRs are: |
|
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. |
k8s-ci-robot
added
the
lifecycle/stale
|
@saschagrunert -- Let's please work on getting the cherry picks approved, so we can close this out. /remove-lifecycle stale |
k8s-ci-robot
removed
the
lifecycle/stale
Yes, master and 1.16 are now done. Just waiting for 1.17 and 1.18. |
|
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. |
k8s-ci-robot
added
the
lifecycle/stale
|
/remove-lifecycle stale |
k8s-ci-robot
removed
the
lifecycle/stale
|
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
k8s-ci-robot
added
the
lifecycle/stale
|
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
k8s-ci-robot
added
lifecycle/rotten
|
Rotten issues close after 30d of inactivity. Send feedback to sig-contributor-experience at kubernetes/community. |
|
@fejta-bot: 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. |
|
/remove-lifecycle rotten Continuing work on this in kubernetes/k8s.io#2663. |
|
@justaugustus: Reopened 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. |
k8s-ci-robot
removed
the
lifecycle/rotten
|
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
k8s-ci-robot
added
the
lifecycle/stale
|
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
k8s-ci-robot
added
lifecycle/rotten
|
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close |
|
@k8s-triage-robot: 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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
(Carrying this over from my personal TODOs now that the bucket exists...)
k8s-artifacts-cri-toolsprod GCS bucket for uploading release artifactsmasterbranch: Update cri-tools to v1.18.0 (#2) kubernetes/kubernetes#91564release-1.18branch:release-1.17branch:release-1.16branch:masterbranch: kubepkg: Use k8s-artifacts-cri-tools GCS bucket as source for CRI tools kubernetes/release#1321build-adminsbranch: Use k8s-artifacts-cri-tools GCS bucket as source for CRI tools kubernetes/release#1322ref: kubernetes/kubernetes#91239, kubernetes/k8s.io#896
/assign @justaugustus @saschagrunert
cc: @feiskyer
The text was updated successfully, but these errors were encountered: