Commit a493feb
doc: document "Resume Build" limitation
Compiled binaries for fanned CI builds on Windows and ARM are only kept
for seven days.
PR-URL: #30604
Reviewed-By: Beth Griggs <Bethany.Griggs@uk.ibm.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>1 parent 0d6fbe8 commit a493feb
1 file changed
Lines changed: 3 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -187,7 +187,9 @@ Do not land any pull requests without passing (green or yellow) CI runs. If | |||
| 187 | 187 | there are CI failures unrelated to the change in the pull request, try "Resume | |
| 188 | 188 | Build". It is in the left navigation of the relevant `node-test-pull-request` | |
| 189 | 189 | job. It will preserve all the green results from the current job but re-run | |
| 190 | - everything else. | ||
| 190 | + everything else. Start a fresh CI if more than seven days have elapsed since | ||
| 191 | + the original failing CI as the compiled binaries for the Windows and ARM | ||
| 192 | + platforms are only kept for seven days. | ||
| 191 | 193 | ||
| 192 | 194 | Some of the CI Jobs may require `GIT_REMOTE_REF` which is the remote portion | |
| 193 | 195 | of Git refspec. To specify the branch this way `refs/heads/BRANCH` is used | |
0 commit comments