Add release-1.18 publishing rules #88431
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
k8s-ci-robot
added
the
release-note-none
k8s-ci-robot
added
kind/cleanup
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: liggitt The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
approved
|
LGTM, but I'll let a @kubernetes/publishing-bot-reviewers sign off officially. |
| branch: release-1.18 | ||
| dir: staging/src/k8s.io/code-generator | ||
| name: release-1.18 | ||
| go: 1.13.4 |
There was a problem hiding this comment.
@liggitt -- Should these be 1.13.6?
There was a problem hiding this comment.
it doesn't really matter, this is just for the bot to test with, and 1.13.x is sufficient. If we want to update this we should do it separately and update the levels for all the branches
There was a problem hiding this comment.
SGTM. We can take care of that after the 1.13.7 bump.
nikhita
reviewed
Feb 23, 2020
| @@ -124,10 +145,21 @@ rules: | |||
| branch: release-1.17 | |||
| - repository: api | |||
| branch: release-1.17 | |||
| - source: | |||
| branch: release-1.18 | |||
There was a problem hiding this comment.
Nice to see client-go following the branch nomenclature as other repos :)
k8s-ci-robot
added
the
lgtm
|
/retest
…On Sun, Feb 23, 2020 at 1:01 PM Kubernetes Prow Robot < ***@***.***> wrote:
@liggitt <https://github.com/liggitt>: The following test *failed*, say
/retest to rerun all failed tests:
Test name Commit Details Rerun command
pull-kubernetes-e2e-gce a6dc7ba
<a6dc7ba>
link
<https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/pull/88431/pull-kubernetes-e2e-gce/1231467089533865988/> /test
pull-kubernetes-e2e-gce
Full PR test history
<https://prow.k8s.io/pr-history?org=kubernetes&repo=kubernetes&pr=88431>. Your
PR dashboard <https://gubernator.k8s.io/pr/liggitt>. Please help us cut
down on flakes by linking to
<https://git.k8s.io/community/contributors/devel/sig-testing/flaky-tests.md#filing-issues-for-flaky-tests>
an open issue
<https://github.com/kubernetes/kubernetes/issues?q=is:issue+is:open> when
you hit one in your PR.
Instructions for interacting with me using PR comments are available here
<https://git.k8s.io/community/contributors/guide/pull-requests.md>. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
<https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:>
repository. I understand the commands that are listed here
<https://go.k8s.io/bot-commands>.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#88431?email_source=notifications&email_token=AD24BUCWIM3JWI5OYJFVZQTREIQ3NA5CNFSM4KZWBRJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMVTWWQ#issuecomment-590035802>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AD24BUFBOKH5TJESGPP6VTTREIQ3NANCNFSM4KZWBRJA>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Adds staging repo publishing rules for release-1.18
Which issue(s) this PR fixes:
Fixes #88376
Fixes #88277
/sig release
/cc @sttts @nikhita @justaugustus