update: links
This commit is contained in:
Junya Okabe
parent
5c3814e29a
commit
c0e379d50f
|
|
@ -2325,6 +2325,6 @@ Twitter | [Sep 19th](https://twitter.com/stephenaugustus/status/1174797710043430
|
|||
* bentheelder - Shoutout to @jeefy for the really shiny and useful looking structured Kubernetes release notes viewer demo in today's #sig-release meeting, looking forward to seeing more about this!
|
||||
* Maria - shoutout to Silvia Moura Pina (@smourapina) for putting together a workflow to enable the CI signal subteam of the release team keep on top of flagging issues from e2e tests and coordinate follow-ups and to Jorge Alarcon (@Jorge) for spotting an opportunity to offer broader transparency to what the CI signal team is working on, suggesting a structure and kicking off implementation (find current version at [https://github.com/orgs/kubernetes/projects/11](https://github.com/orgs/kubernetes/projects/11))
|
||||
* spiffxp - shouts to Josh Berkus (@jberkus) for taking notes during today’s steering committee meeting, our google doc clearly becomes way more difficult to use with so many people looking at it, and the written record is invaluable
|
||||
* spiffxp - shoutout to Katharine Berry (@Katharine) for moving us from gubernator to spyglass for all of our test result viewing needs! [https://git.k8s.io/test-infra/prow/spyglass ](https://git.k8s.io/test-infra/prow/spyglass)
|
||||
* spiffxp - shoutout to Katharine Berry (@Katharine) for moving us from gubernator to spyglass for all of our test result viewing needs! [http://sigs.k8s.io/prow/pkg/spyglass ](http://sigs.k8s.io/prow/pkg/spyglass)
|
||||
* codenrhoden - Shoutout to Michelle Au (@msau42) for her patience and helpful guidance in getting a very large PR merged!
|
||||
* @strebel - @jeefy and @onyiny-ang for all their awesome work on the Release-Notes team for 1.14. Especially @jeefy’s work on the Release-Notes website concept
|
||||
|
|
@ -9,7 +9,7 @@ processes.
|
|||
## Tide
|
||||
|
||||
This project formerly used a Submit Queue, it has since been replaced by
|
||||
[Tide](https://git.k8s.io/test-infra/prow/cmd/tide).
|
||||
[Tide](http://sigs.k8s.io/prow/cmd/tide).
|
||||
|
||||
### Ready to merge status
|
||||
|
||||
|
|
|
|||
|
|
@ -644,7 +644,7 @@ A quick overview of how we run e2e CI on Kubernetes.
|
|||
|
||||
We run a battery of [release-blocking jobs](https://testgrid.k8s.io/sig-release-master-blocking)
|
||||
against `HEAD` of the master branch on a continuous basis, and block merges
|
||||
via [Tide](https://git.k8s.io/test-infra/prow/cmd/tide) on a subset of those
|
||||
via [Tide](http://sigs.k8s.io/prow/cmd/tide) on a subset of those
|
||||
tests if they fail.
|
||||
|
||||
CI results can be found at [ci-test.k8s.io](http://ci-test.k8s.io), e.g.
|
||||
|
|
|
|||
|
|
@ -229,7 +229,7 @@ If the failure seems unrelated to the change you're submitting:
|
|||
- if you don't get a response in 24 hours, engage with the SIG on their channel on the [Kubernetes slack](http://slack.k8s.io/) and/or attend one of the [SIG meetings][sig-meetings] to ask for input.
|
||||
|
||||
[prow-url]: https://prow.k8s.io
|
||||
[prow-git]: https://git.k8s.io/test-infra/prow
|
||||
[prow-git]: http://sigs.k8s.io/prow/pkg
|
||||
[prow-doc]: https://kubernetes.io/blog/2018/08/29/the-machines-can-do-the-work-a-story-of-kubernetes-testing-ci-and-automating-the-contributor-experience/#enter-prow
|
||||
[membership]: https://github.com/kubernetes/community/blob/master/community-membership.md#member
|
||||
[k-teams]: https://github.com/orgs/kubernetes/teams
|
||||
|
|
|
|||
|
|
@ -365,7 +365,7 @@ anderer Beitragenden zu überlassen, die als Reviewer und Approver für den PR z
|
|||
[Kubernetes Forum]: https://discuss.kubernetes.io/
|
||||
[Pull-Request Prozess]: /contributors/guide/pull-requests.md
|
||||
[GitHub Workflow]: /contributors/guide/github-workflow.md
|
||||
[Prow]: https://git.k8s.io/test-infra/prow#prow
|
||||
[Prow]: http://sigs.k8s.io/prow/pkg#prow
|
||||
[cla]: /CLA.md#how-do-i-sign
|
||||
[CLA troubleshooting guidelines]: /CLA.md#troubleshooting
|
||||
[commands]: https://prow.k8s.io/command-help
|
||||
|
|
|
|||
|
|
@ -306,7 +306,7 @@ Si vous ne savez pas si vous devez faire un squash de vos commits, il est préf
|
|||
[kubernetes forum]: https://discuss.kubernetes.io/
|
||||
[pull request process]: /contributors/guide/pull-requests.md
|
||||
[github workflow]: /contributors/guide/github-workflow.md
|
||||
[prow]: https://git.k8s.io/test-infra/prow#prow
|
||||
[prow]: http://sigs.k8s.io/prow/pkg#prow
|
||||
[cla]: /CLA.md#how-do-i-sign
|
||||
[cla troubleshooting guidelines]: /CLA.md#troubleshooting
|
||||
[commands]: https://prow.k8s.io/command-help
|
||||
|
|
|
|||
|
|
@ -297,7 +297,7 @@ PR संशोधन का चरण। यदि आप अनिश्चि
|
|||
[कुबरनेट्स फ़ोरम]: https://discuss.kubernetes.io/
|
||||
[पुल अनुरोध प्रक्रिया]: /contributors/guide/pull-requests.md
|
||||
[github वर्कफ़्लो]: /contributors/guide/github-workflow.md
|
||||
[prow]: https://git.k8s.io/test-infra/prow#prow
|
||||
[prow]: http://sigs.k8s.io/prow/pkg#prow
|
||||
[CLA]: /CLA.md#how-do-i-sign
|
||||
[CLA समस्या निवारण दिशा निर्देशों]: /CLA.md#troubleshooting
|
||||
[आदेश]: https://prow.k8s.io/command-help
|
||||
|
|
|
|||
|
|
@ -366,7 +366,7 @@ _squashing_ perlu dilakukan atau tidak.
|
|||
[forum kubernetes]: https://discuss.kubernetes.io/
|
||||
[pull request process]: /contributors/guide/pull-requests.md
|
||||
[github workflow]: /contributors/guide/github-workflow.md
|
||||
[prow]: https://git.k8s.io/test-infra/prow#prow
|
||||
[prow]: http://sigs.k8s.io/prow/pkg#prow
|
||||
[cla]: /CLA.md#how-do-i-sign
|
||||
[petunjuk _troubleshooting_ cla]: /CLA.md#troubleshooting
|
||||
[perintah]: https://prow.k8s.io/command-help
|
||||
|
|
|
|||
|
|
@ -373,7 +373,7 @@ git push --force
|
|||
[kubernetes forum]: https://discuss.kubernetes.io/
|
||||
[pull request process]: /contributors/guide/pull-requests.md
|
||||
[github workflow]: /contributors/guide/github-workflow.md
|
||||
[prow]: https://git.k8s.io/test-infra/prow#prow
|
||||
[prow]: http://sigs.k8s.io/prow/pkg#prow
|
||||
[cla]: /CLA.md#how-do-i-sign
|
||||
[cla troubleshooting guidelines]: /CLA.md#troubleshooting
|
||||
[commands]: https://prow.k8s.io/command-help
|
||||
|
|
|
|||
|
|
@ -322,7 +322,7 @@ git push --force
|
|||
[kubernetesフォーラム]: https://discuss.kubernetes.io/
|
||||
[pull request process]: /contributors/guide/pull-requests.md
|
||||
[github workflow]: /contributors/guide/github-workflow.md
|
||||
[prow]: https://git.k8s.io/test-infra/prow#prow
|
||||
[prow]: http://sigs.k8s.io/prow/pkg#prow
|
||||
[cla]: /CLA.md#how-do-i-sign
|
||||
[claトラブルシューティングガイドライン]: /CLA.md#troubleshooting
|
||||
[コマンド]: https://prow.k8s.io/command-help
|
||||
|
|
|
|||
|
|
@ -370,7 +370,7 @@ PR을 검토하고 승인하도록 지정된 다른 참여자의 판단에 맡
|
|||
[쿠버네티스 포럼]: https://discuss.kubernetes.io/
|
||||
[풀 리퀘스트 과정]: /contributors/guide/pull-requests.md
|
||||
[github 작업 흐름]: /contributors/guide/github-workflow.md
|
||||
[prow]: https://git.k8s.io/test-infra/prow#prow
|
||||
[prow]: http://sigs.k8s.io/prow/pkg#prow
|
||||
[cla]: /CLA.md#how-do-i-sign
|
||||
[CLA 문제해결 가이드라인]: /CLA.md#troubleshooting
|
||||
[commands]: https://prow.k8s.io/command-help
|
||||
|
|
|
|||
|
|
@ -352,7 +352,7 @@ fase de uma revisão do PR. Se você não tem certeza se deve efetuar o squashin
|
|||
[Fórum do Kubernetes]: https://discuss.kubernetes.io/
|
||||
[Processo de pull request]: /contributors/guide/pull-requests.md
|
||||
[github workflow]: /contributors/guide/github-workflow.md
|
||||
[prow]: https://git.k8s.io/test-infra/prow#prow
|
||||
[prow]: http://sigs.k8s.io/prow/pkg#prow
|
||||
[cla]: /CLA.md#how-do-i-sign
|
||||
[solucionando problemas do cla]: /CLA.md#troubleshooting
|
||||
[commands]: https://prow.k8s.io/command-help
|
||||
|
|
|
|||
|
|
@ -298,7 +298,7 @@ git checkout -b myfeature
|
|||
[Kubernetes форум]: https://discuss.kubernetes.io/
|
||||
[Процес pull request]: /contributors/guide/pull-requests.md
|
||||
[Робочий процес у github]: /contributors/guide/github-workflow.md
|
||||
[prow]: https://git.k8s.io/test-infra/prow#prow
|
||||
[prow]: http://sigs.k8s.io/prow/pkg#prow
|
||||
[cla]: /CLA.md#how-do-i-sign
|
||||
[інструкції з вирішення проблем CLA]: /CLA.md#troubleshooting
|
||||
[commands]: https://prow.k8s.io/command-help
|
||||
|
|
|
|||
|
|
@ -303,7 +303,7 @@ git checkout -b myfeature
|
|||
[Kubernetes 论坛]: https://discuss.kubernetes.io/
|
||||
[Pull request 处理]: /contributors/guide/pull-requests.md
|
||||
[GitHub 工作流程]: /contributors/guide/github-workflow.md
|
||||
[prow]: https://git.k8s.io/test-infra/prow#prow
|
||||
[prow]: http://sigs.k8s.io/prow/pkg#prow
|
||||
[cla]: /CLA.md#how-do-i-sign
|
||||
[cla 故障排除指南]: /CLA.md#troubleshooting
|
||||
[命令]: https://prow.k8s.io/command-help
|
||||
|
|
|
|||
|
|
@ -399,7 +399,7 @@ git push --force
|
|||
[kubernetes forum]: https://discuss.kubernetes.io/
|
||||
[pull request process]: /contributors/guide/pull-requests.md
|
||||
[github workflow]: /contributors/guide/github-workflow.md
|
||||
[prow]: https://git.k8s.io/test-infra/prow#prow
|
||||
[prow]: https://sigs.k8s.io/prow/pkg#prow
|
||||
[cla]: /CLA.md#how-do-i-sign
|
||||
[cla troubleshooting guidelines]: /CLA.md#troubleshooting
|
||||
[commands]: https://prow.k8s.io/command-help
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@ of OWNERS files.
|
|||
|
||||
## OWNERS spec
|
||||
|
||||
The [k8s.io/test-infra/prow/repoowners package](https://git.k8s.io/test-infra/prow/repoowners/repoowners.go)
|
||||
The [k8s.io/test-infra/prow/repoowners package](http://sigs.k8s.io/prow/pkg/repoowners/repoowners.go)
|
||||
is the main consumer of OWNERS files. If this page is out of date, look there.
|
||||
|
||||
### OWNERS
|
||||
|
|
@ -253,20 +253,20 @@ Kubernetes uses the Prow Blunderbuss plugin and Tide.
|
|||
Tide uses GitHub queries to select PRs into “tide pools”, runs as many in a
|
||||
batch as it can (“tide comes in”), and merges them (“tide goes out”).
|
||||
|
||||
- [Blunderbuss plugin](https://git.k8s.io/test-infra/prow/plugins/blunderbuss):
|
||||
- [Blunderbuss plugin](http://sigs.k8s.io/prow/pkg/plugins/blunderbuss):
|
||||
- responsible for determining **reviewers**
|
||||
- [Tide](https://git.k8s.io/test-infra/prow/cmd/tide):
|
||||
- [Tide](http://sigs.k8s.io/prow/cmd/tide):
|
||||
- responsible for automatically running batch tests and merging multiple PRs together whenever possible.
|
||||
- responsible for retriggering stale PR tests.
|
||||
- responsible for updating a GitHub status check explaining why a PR can't be merged (eg: a
|
||||
missing `lgtm` or `approved` label)
|
||||
|
||||
### [`prow`](https://git.k8s.io/test-infra/prow)
|
||||
### [`prow`](http://sigs.k8s.io/prow/pkg)
|
||||
|
||||
Prow receives events from GitHub, and reacts to them. It is effectively stateless. The following
|
||||
pieces of prow are used to implement the code review process above.
|
||||
|
||||
- [cmd: tide](https://git.k8s.io/test-infra/prow/cmd/tide)
|
||||
- [cmd: tide](http://sigs.k8s.io/prow/cmd/tide)
|
||||
- per-repo configuration:
|
||||
- `labels`: list of labels required to be present for merge (eg: `lgtm`)
|
||||
- `missingLabels`: list of labels required to be missing for merge (eg: `do-not-merge/hold`)
|
||||
|
|
@ -278,10 +278,10 @@ pieces of prow are used to implement the code review process above.
|
|||
- merges PR's once they meet the appropriate criteria as configured above
|
||||
- if there are any presubmit prow jobs for the repo the PR is against, they will be re-run one
|
||||
final time just prior to merge
|
||||
- [plugin: assign](https://git.k8s.io/test-infra/prow/plugins/assign)
|
||||
- [plugin: assign](http://sigs.k8s.io/prow/pkg/plugins/assign)
|
||||
- assigns GitHub users in response to `/assign` comments on a PR
|
||||
- unassigns GitHub users in response to `/unassign` comments on a PR
|
||||
- [plugin: approve](https://git.k8s.io/test-infra/prow/plugins/approve)
|
||||
- [plugin: approve](http://sigs.k8s.io/prow/pkg/plugins/approve)
|
||||
- per-repo configuration:
|
||||
- `issue_required`: defaults to `false`; when `true`, require that the PR description link to
|
||||
an issue, or that at least one **approver** issues a `/approve no-issue`
|
||||
|
|
@ -291,12 +291,12 @@ pieces of prow are used to implement the code review process above.
|
|||
OWNERS files has `/approve`'d
|
||||
- comments as required OWNERS files are satisfied
|
||||
- removes outdated approval status comments
|
||||
- [plugin: blunderbuss](https://git.k8s.io/test-infra/prow/plugins/blunderbuss)
|
||||
- [plugin: blunderbuss](http://sigs.k8s.io/prow/pkg/plugins/blunderbuss)
|
||||
- determines **reviewers** and requests their reviews on PR's
|
||||
- [plugin: lgtm](https://git.k8s.io/test-infra/prow/plugins/lgtm)
|
||||
- [plugin: lgtm](http://sigs.k8s.io/prow/pkg/plugins/lgtm)
|
||||
- adds the `lgtm` label when a **reviewer** comments `/lgtm` on a PR
|
||||
- the **PR author** may not `/lgtm` their own PR
|
||||
- [pkg: k8s.io/test-infra/prow/repoowners](https://git.k8s.io/test-infra/prow/repoowners/repoowners.go)
|
||||
- [pkg: k8s.io/test-infra/prow/repoowners](http://sigs.k8s.io/prow/pkg/repoowners/repoowners.go)
|
||||
- parses OWNERS and OWNERS_ALIAS files
|
||||
- if the `no_parent_owners` option is encountered, parent owners are excluded from having
|
||||
any influence over files adjacent to or underneath of the current OWNERS file
|
||||
|
|
|
|||
|
|
@ -595,7 +595,7 @@ Once the tests pass, and the reviewer adds the `lgtm` and `approved` labels, the
|
|||
The merge pool is needed to make sure no incompatible changes have been introduced by other pull requests since the tests were last run on your pull request.
|
||||
<!-- TODO: create parallel instructions for reviewers -->
|
||||
|
||||
[Tide](https://git.k8s.io/test-infra/prow/cmd/tide) will manage the merge pool
|
||||
[Tide](http://sigs.k8s.io/prow/cmd/tide) will manage the merge pool
|
||||
automatically. It uses GitHub queries to select PRs into “tide pools”,
|
||||
runs as many in a batch as it can (“tide comes in”), and merges them (“tide goes out”).
|
||||
|
||||
|
|
|
|||
|
|
@ -145,7 +145,7 @@ git checkout foo
|
|||
[KEEP THE SPACE SHUTTLE FLYING]: https://github.com/kubernetes/kubernetes/blob/master/pkg/controller/volume/persistentvolume/pv_controller.go#L57-L117
|
||||
[commit message guidelines]: ./pull-requests.md#7-commit-message-guidelines
|
||||
[GitHub Status]: https://help.github.com/en/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#setting-a-status
|
||||
[Blunderbuss]: https://git.k8s.io/test-infra/prow/plugins/approve/approvers/README.md#blunderbuss-and-reviewers
|
||||
[Blunderbuss]: http://sigs.k8s.io/prow/pkg/plugins/approve/approvers/
|
||||
[emeritus_approver]: ./owners.md#emeritus
|
||||
[Keeping the Bar High - How to be a bad ass Code Reviewer, Tim Hockin]: https://www.youtube.com/watch?v=OZVv7-o8i40
|
||||
[Kubernetes Code Reviewing with Tim Hockin]: https://docs.google.com/document/d/15y8nIgWMzptHcYIeqf4vLJPttE3Fj_ht4I6Nj4ghDLA/edit#heading=h.3dchnigrxf5y
|
||||
|
|
|
|||
|
|
@ -635,7 +635,7 @@ relative links. However, how and what they're being linked to can vary widely.
|
|||
```
|
||||
The super cool [prow tool] resides in the test-infra repo under the kubernetes organization
|
||||
|
||||
[prow tool]: https://git.k8s.io/test-infra/prow/README.md
|
||||
[prow tool]: http://sigs.k8s.io/prow/README.md
|
||||
```
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -103,13 +103,13 @@ intentions. [For more details please see community issue #1407](https://github.c
|
|||
|
||||
We have created a number of tools to help with the management of or Github
|
||||
repositories and organizations:
|
||||
- [prow](https://git.k8s.io/test-infra/prow): Prow is our system for handling
|
||||
- [prow](http://sigs.k8s.io/prow/pkg): Prow is our system for handling
|
||||
GitHub events and commands for Kubernetes. It is comprised of a number of
|
||||
modules/plugins. A couple key ones for GitHub management are below, but a full
|
||||
list of commands is available [here](https://go.k8s.io/bot-commands)
|
||||
- [branchprotector](https://git.k8s.io/test-infra/prow/cmd/branchprotector):
|
||||
- [branchprotector](http://sigs.k8s.io/prow/cmd/branchprotector):
|
||||
enforce branch protection settings across an organization
|
||||
- [peribolos](https://git.k8s.io/test-infra/prow/cmd/peribolos): Manage Github
|
||||
- [peribolos](http://sigs.k8s.io/prow/cmd/peribolos): Manage Github
|
||||
organization and team membership based on a defined YAML configuration
|
||||
- [label_sync](https://git.k8s.io/test-infra/label_sync): Add, modify, delete,
|
||||
and migrate labels across an entire organization based on a defined YAML
|
||||
|
|
|
|||
|
|
@ -200,7 +200,7 @@ from the above procedure:
|
|||
* Grant the [@kubernetes/stage-bots] team admin access to the repo.
|
||||
* Setup branch protection and enable access to the
|
||||
`stage-bots` team by adding the repo in
|
||||
[`prow/config.yaml`](https://git.k8s.io/test-infra/prow/config.yaml). See
|
||||
[`prow/config.yaml`](https://git.k8s.io/test-infra/config/prow/config.yaml). See
|
||||
[kubernetes/test-infra#9292](https://github.com/kubernetes/test-infra/pull/9292)
|
||||
for an example.
|
||||
* Once the repo has been created, add the repo to
|
||||
|
|
|
|||
|
|
@ -97,6 +97,6 @@ member in the organization.
|
|||
[org permissions]:
|
||||
https://help.github.com/articles/permission-levels-for-an-organization/
|
||||
[OWNERS]: /contributors/guide/owners.md
|
||||
[peribolos]: https://git.k8s.io/test-infra/prow/cmd/peribolos
|
||||
[peribolos]: http://sigs.k8s.io/prow/cmd/peribolos
|
||||
[repo permissions]:
|
||||
https://help.github.com/articles/repository-permission-levels-for-an-organization/
|
||||
|
|
|
|||
|
|
@ -61,7 +61,7 @@ instead of direct pushing that will never kick off a CLA check.
|
|||
## Label automation
|
||||
|
||||
The label automation is done using the [CLA plugin in
|
||||
prow](https://git.k8s.io/test-infra/prow/plugins/cla). In order to turn on the
|
||||
prow](http://sigs.k8s.io/prow/pkg/plugins/cla). In order to turn on the
|
||||
CLA labels on your repo, add it as appropriate within the
|
||||
[plugins.yaml](https://git.k8s.io/test-infra/config/prow/plugins.yaml), and add the cla
|
||||
plugin to it.
|
||||
|
|
|
|||
Loading…
Reference in New Issue