Commit a9d28e2
committed
doc: update CI instructions
The recent changes made to better protect CI against malicious PRs have
changed how the `Retry` button can be used, it will no longer be
useful when follow up commits were pushed due to the non-matching
commit SHA.
PR-URL: #57743
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Paolo Insogna <paolo@cowtech.it>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Chengzhong Wu <legendecas@gmail.com>
Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com>
Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com>
Reviewed-By: Darshan Sen <raisinten@gmail.com>
Reviewed-By: Ulises Gascón <ulisesgascongonzalez@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>1 parent a3be0df commit a9d28e2
1 file changed
Lines changed: 5 additions & 5 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -252,13 +252,13 @@ request, try the "🔄 Re-run all jobs" button, on the right-hand side of the | |||
| 252 | 252 | If there are Jenkins CI failures unrelated to the change in the pull request, | |
| 253 | 253 | try "Resume Build". It is in the left navigation of the relevant | |
| 254 | 254 | `node-test-pull-request` job. It will preserve all the green results from the | |
| 255 | - current job but re-run everything else. Start a fresh CI if more than seven days | ||
| 256 | - have elapsed since the original failing CI as the compiled binaries for the | ||
| 257 | - Windows and ARM platforms are only kept for seven days. | ||
| 255 | + current job but re-run everything else. Start a fresh CI by pressing "Retry" | ||
| 256 | + if more than seven days have elapsed since the original failing CI as the | ||
| 257 | + compiled binaries for the Windows and ARM platforms are only kept for seven days. | ||
| 258 | 258 | ||
| 259 | 259 | If new commits are pushed to the pull request branch after the latest Jenkins | |
| 260 | - CI run, a fresh CI run is required. It can be started by pressing "Retry" on | ||
| 261 | - the left sidebar, or by adding the `request-ci` label to the pull request. | ||
| 260 | + CI run, a fresh CI run is required. It can be started by adding the `request-ci` | ||
| 261 | + label to the pull request. | ||
| 262 | 262 | ||
| 263 | 263 | #### Useful Jenkins CI jobs | |
| 264 | 264 | ||
0 commit comments