Commit 6a32a68
doc: note resume build should not be done on node-test-commit
Signed-off-by: Stewart X Addison <sxa@ibm.com>
PR-URL: #61373
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com>1 parent a132be7 commit 6a32a68
1 file changed
Lines changed: 8 additions & 6 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -267,12 +267,14 @@ If there are GitHub Actions CI failures unrelated to the change in the pull | |||
| 267 | 267 | request, try the "🔄 Re-run all jobs" button, on the right-hand side of the | |
| 268 | 268 | "Checks" tab. | |
| 269 | 269 | ||
| 270 | - If there are Jenkins CI failures unrelated to the change in the pull request, | ||
| 271 | - try "Resume Build". It is in the left navigation of the relevant | ||
| 272 | - `node-test-pull-request` job. It will preserve all the green results from the | ||
| 273 | - current job but re-run everything else. Start a fresh CI by pressing "Retry" | ||
| 274 | - if more than seven days have elapsed since the original failing CI as the | ||
| 275 | - compiled binaries for the Windows and ARM platforms are only kept for seven days. | ||
| 270 | + If there are Jenkins CI failures unrelated to the change in the pull | ||
| 271 | + request, try "Resume Build". It is in the left navigation of the relevant | ||
| 272 | + `node-test-pull-request` job. (Do not be tempted to do this on the lower | ||
| 273 | + level `node-test-commit` job as it will not report the updated result back | ||
| 274 | + to the PR.) It will preserve all the green results from the current job but | ||
| 275 | + re-run everything else. Start a fresh CI by pressing "Retry" if more than | ||
| 276 | + seven days have elapsed since the original failing CI as the compiled | ||
| 277 | + binaries for the Windows and ARM platforms are only kept for seven days. | ||
| 276 | 278 | ||
| 277 | 279 | If new commits are pushed to the pull request branch after the latest Jenkins | |
| 278 | 280 | CI run, a fresh CI run is required. It can be started by adding the `request-ci` | |
0 commit comments