Commit eded43c
doc: add Retry CI in collaborator guide
PR-URL: #44130
Reviewed-By: Feng Yu <F3n67u@outlook.com>
Reviewed-By: Darshan Sen <raisinten@gmail.com>
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
Reviewed-By: Richard Lau <rlau@redhat.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Michael Dawson <midawson@redhat.com>1 parent 1598894 commit eded43c
1 file changed
Lines changed: 4 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -253,6 +253,10 @@ current job but re-run everything else. Start a fresh CI if more than seven days | |||
| 253 | 253 | have elapsed since the original failing CI as the compiled binaries for the | |
| 254 | 254 | Windows and ARM platforms are only kept for seven days. | |
| 255 | 255 | ||
| 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 | + | ||
| 256 | 260 | #### Useful Jenkins CI jobs | |
| 257 | 261 | ||
| 258 | 262 | * [`node-test-pull-request`](https://ci.nodejs.org/job/node-test-pull-request/) | |
0 commit comments