Skip to content

Commit cc84898

Browse files
aduh95RafaelGSS
authored andcommitted
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 <[email protected]> Reviewed-By: Paolo Insogna <[email protected]> Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Chengzhong Wu <[email protected]> Reviewed-By: Marco Ippolito <[email protected]> Reviewed-By: Rafael Gonzaga <[email protected]> Reviewed-By: Darshan Sen <[email protected]> Reviewed-By: Ulises Gascón <[email protected]> Reviewed-By: James M Snell <[email protected]>
1 parent 9af8b92 commit cc84898

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

doc/contributing/collaborator-guide.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -252,13 +252,13 @@ request, try the "🔄 Re-run all jobs" button, on the right-hand side of the
252252
If there are Jenkins CI failures unrelated to the change in the pull request,
253253
try "Resume Build". It is in the left navigation of the relevant
254254
`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.
258258

259259
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.
262262

263263
#### Useful Jenkins CI jobs
264264

0 commit comments

Comments
 (0)