diff options
| author | Joe Finney <spxtr@google.com> | 2017-06-23 14:59:49 -0700 |
|---|---|---|
| committer | Joe Finney <spxtr@google.com> | 2017-06-23 17:59:27 -0700 |
| commit | a04aa3be80366ddee3b69bb4d2fa90f74df74681 (patch) | |
| tree | ef63f3e7207f97ea95f96593b5bf8cc2db30d6d6 | |
| parent | c9912ffb895690472f4c1796dfa0813915e36e2d (diff) | |
Reword build cop duties for batch merges.
| -rw-r--r-- | contributors/devel/on-call-build-cop.md | 3 |
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 |