Skip to content
Permalink
Browse files

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>
  • Loading branch information
richardlau authored and MylesBorins committed Nov 22, 2019
1 parent 0d6fbe8 commit a493feb863419b0abf941d14731dc1901b58d30c
Showing with 3 additions and 1 deletion.
  1. +3 −1 COLLABORATOR_GUIDE.md
@@ -187,7 +187,9 @@ Do not land any pull requests without passing (green or yellow) CI runs. If
there are CI failures unrelated to the change in the pull request, try "Resume
Build". It is in the left navigation of the relevant `node-test-pull-request`
job. It will preserve all the green results from the current job but re-run
everything else.
everything else. Start a fresh CI if more than seven days have elapsed since
the original failing CI as the compiled binaries for the Windows and ARM
platforms are only kept for seven days.

Some of the CI Jobs may require `GIT_REMOTE_REF` which is the remote portion
of Git refspec. To specify the branch this way `refs/heads/BRANCH` is used

0 comments on commit a493feb

Please sign in to comment.
You can’t perform that action at this time.