If you are using a released version of Kubernetes, you should refer to the docs that go with that version.
The latest release of this document can be found [here](http://releases.k8s.io/release-1.1/docs/devel/automation.md).Kubernetes uses a variety of automated tools in an attempt to relieve developers of repeptitive, low brain power work. This document attempts to describe these processes.
In an effort to
We have added an automated submit-queue to the github "munger" for kubernetes.
The submit-queue does the following:
for _, pr := range readyToMergePRs() {
if testsAreStable() {
mergePR(pr)
}
}
The status of the submit-queue is online.
A PR is considered "ready for merging" if it matches the following:
lgtm
label, and that lgtm
is newer than the latest commitcla:yes
labelok-to-merge
labele2e-not-required
labelNote that the combined whitelist/committer list is available at submit-queue.k8s.io
Merges only occur when the critical builds
(Jenkins e2e for gce, gke, scalability, upgrade) are passing.
We're open to including more builds here, let us know...
Merges are serialized, so only a single PR is merged at a time, to ensure against races.
If the PR has the e2e-not-required
label, it is simply merged.
If the PR does not have this label, e2e tests are re-run, if these new tests pass, the PR is merged.
If e2e flakes or is currently buggy, the PR will not be merged, but it will be re-run on the following pass.
We also run a github "munger"
This runs repeatedly over github pulls and issues and runs modular "mungers" similar to "mungedocs"
Currently this runs:
needs-rebase
to PRs that aren't currently mergeable, and removes it from those that are.size/xs
- size/xxl
labels to PRsok-to-test
message to PRs that have an lgtm
but the e2e-builder would otherwise not test due to whitelistlgtm
label from PRs where there are commits that are newer than the lgtm
labelIn the works:
support
issue, bug
or feature
Please feel free to unleash your creativity on this tool, send us new mungers that you think will help support the Kubernetes development process.
We also run a robotic PR builder that attempts to run e2e tests for each PR.
Before a PR from an unknown user is run, the PR builder bot (k8s-bot
) asks to a message from a
contributor that a PR is "ok to test", the contributor replies with that message. Contributors can also
add users to the whitelist by replying with the message "add to whitelist" ("please" is optional, but
remember to treat your robots with kindness...)
If a PR is approved for testing, and tests either haven't run, or need to be re-run, you can ask the
PR builder to re-run the tests. To do this, reply to the PR with a message that begins with @k8s-bot test this
, this should trigger a re-build/re-test.
Right now you have to ask a contributor (this may be you!) to re-run the test with "@k8s-bot test this"
Right now the easiest way is to close and then immediately re-open the PR.
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。