Skip to content

Commit a71f31b

Browse files
authored
Merge pull request kubernetes-sigs#9593 from furkatgofurov7/add-task-checkpendingjobs
📖 Add a note to the CI team tasks to check for stuck/pending jobs in CI
2 parents 8cb4600 + 0128846 commit a71f31b

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

docs/release/release-tasks.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -483,13 +483,15 @@ The goal of this task is to keep our tests running in CI stable.
483483
(also dashboards of previous releases). Using the alert mailing list has proven to be a lot less effort though.
484484
2. Subscribe to `CI Activity` notifications for the Cluster API repo.
485485
3. Check the existing **failing-test** and **flaking-test** issue templates under `.github/ISSUE_TEMPLATE/` folder of the repo, used to create an issue for failing or flaking tests respectively. Please make sure they are up-to-date and if not, send a PR to update or improve them.
486-
4. Triage CI failures reported by mail alerts or found by monitoring the testgrid dashboards:
486+
4. Check if there are any existing jobs that got stuck (have been running for more than 12 hours) in a ['pending'](https://prow.k8s.io/?repo=kubernetes-sigs%2Fcluster-api&state=pending) state:
487+
- If that is the case, notify the maintainers and ask them to manually cancel and re-run the stuck jobs.
488+
5. Triage CI failures reported by mail alerts or found by monitoring the testgrid dashboards:
487489
1. Create an issue using an appropriate template (failing-test) in the Cluster API repository to surface the CI failure.
488490
2. Identify if the issue is a known issue, new issue or a regression.
489491
3. Mark the issue as `release-blocking` if applicable.
490-
5. Triage periodic GitHub actions failures, with special attention to image scan results;
492+
6. Triage periodic GitHub actions failures, with special attention to image scan results;
491493
Eventually open issues as described above.
492-
6. Run periodic deep-dive sessions with the CI team to investigate failing and flaking tests. Example session recording: https://www.youtube.com/watch?v=YApWftmiDTg
494+
7. Run periodic deep-dive sessions with the CI team to investigate failing and flaking tests. Example session recording: https://www.youtube.com/watch?v=YApWftmiDTg
493495
494496
#### [Continuously] Reduce the amount of flaky tests
495497

0 commit comments

Comments
 (0)