summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJoe Finney <spxtr@users.noreply.github.com>2017-07-05 14:05:18 -0700
committerGitHub <noreply@github.com>2017-07-05 14:05:18 -0700
commit3ef47e333f9024a19851848eb9f7503337e511bd (patch)
tree524a55c45584cff2b9602e7eeb15db2b353755b9
parent82708f9228f71c4c9cccb63354ec5a17be49818a (diff)
parenta04aa3be80366ddee3b69bb4d2fa90f74df74681 (diff)
Merge pull request #761 from spxtr/batchcop
Reword build cop duties for batch merges.
-rw-r--r--contributors/devel/on-call-build-cop.md3
1 files changed, 2 insertions, 1 deletions
diff --git a/contributors/devel/on-call-build-cop.md b/contributors/devel/on-call-build-cop.md
index 6ad64149..e83fd8d0 100644
--- a/contributors/devel/on-call-build-cop.md
+++ b/contributors/devel/on-call-build-cop.md
@@ -31,7 +31,8 @@ longer a part of the mandate.
## Workflow
1. Check the Prow batch dashboard: [https://prow.k8s.io/?type=batch](https://prow.k8s.io/?type=batch)
-to ensure that merges are occurring regularly.
+to ensure that batch jobs are running regularly. It's okay to see occasional flakes. Do not worry
+about manually re-running individual tests, since Prow will rerun them.
2. If there are post-submit blocking jobs (see [link](https://submit-queue.k8s.io/#/e2e)), ensure
that those builds are green and allowing merges to occur.
3. If several batch merges are failing, file an issue for that job and describe the possible