doc: add Retry CI in collaborator guide

PR-URL: #44130 Reviewed-By: Feng Yu <[email protected]> Reviewed-By: Darshan Sen <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Michael Dawson <[email protected]>
nodejs · Aug 22, 2022 · 0fffc24 · 0fffc24
1 parent f1b5f93
commit 0fffc24
Showing 1 changed file with 4 additions and 0 deletions.
diff --git a/doc/contributing/collaborator-guide.md b/doc/contributing/collaborator-guide.md
@@ -253,6 +253,10 @@ current job but re-run 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.
 
+If new commits are pushed to the pull request branch after the latest Jenkins
+CI run, a fresh CI run is required. It can be started by pressing "Retry" on
+the left sidebar, or by adding the `request-ci` label to the pull request.
+
 #### Useful Jenkins CI jobs
 
 * [`node-test-pull-request`](https://ci.nodejs.org/job/node-test-pull-request/)