Skip to content

Commit 0fffc24

Browse files
LiviaMedeirosruyadorno
authored andcommitted
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]>
1 parent f1b5f93 commit 0fffc24

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

doc/contributing/collaborator-guide.md

+4
Original file line numberDiff line numberDiff line change
@@ -253,6 +253,10 @@ current job but re-run everything else. Start a fresh CI if more than seven days
253253
have elapsed since the original failing CI as the compiled binaries for the
254254
Windows and ARM platforms are only kept for seven days.
255255

256+
If new commits are pushed to the pull request branch after the latest Jenkins
257+
CI run, a fresh CI run is required. It can be started by pressing "Retry" on
258+
the left sidebar, or by adding the `request-ci` label to the pull request.
259+
256260
#### Useful Jenkins CI jobs
257261

258262
* [`node-test-pull-request`](https://ci.nodejs.org/job/node-test-pull-request/)

0 commit comments

Comments
 (0)