From ed1d0c92035d3d08116e4d348ff6099a4c370635 Mon Sep 17 00:00:00 2001 From: Livia Medeiros Date: Sun, 7 Aug 2022 08:38:40 +0900 Subject: [PATCH] doc: add Retry CI in collaborator guide PR-URL: https://github.com/nodejs/node/pull/44130 Reviewed-By: Feng Yu Reviewed-By: Darshan Sen Reviewed-By: Antoine du Hamel Reviewed-By: Richard Lau Reviewed-By: Luigi Pinca Reviewed-By: Matteo Collina Reviewed-By: Michael Dawson --- doc/contributing/collaborator-guide.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/doc/contributing/collaborator-guide.md b/doc/contributing/collaborator-guide.md index c145ca8fce03df..dfb23aa53156e7 100644 --- 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/)