Skip to content

doc: note resume build should not be on node-test-commit #61373

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
sxa wants to merge 2 commits into from
+8 −6
Closed

doc: note resume build should not be on node-test-commit #61373

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d4068ec
doc: note resume build should not be done on node-test-commit
sxa Jan 13, 2026
a01f45d
Update doc/contributing/collaborator-guide.md
sxa Jan 16, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Update doc/contributing/collaborator-guide.md 
Co-authored-by: Tobias Nießen <tniessen@tnie.de>
  • Loading branch information
@sxa @tniessen
sxa and tniessen authored Jan 16, 2026
commit a01f45dbf2d7243d2956978219ac82756234be34
4 changes: 2 additions & 2 deletions doc/contributing/collaborator-guide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -269,9 +269,9 @@ request, try the "🔄 Re-run all jobs" button, on the right-hand side of the

If there are Jenkins CI failures unrelated to the change in the pull
request, try "Resume Build". It is in the left navigation of the relevant
`node-test-pull-request` job (Do not be tempted to do this on the lower
`node-test-pull-request` job. (Do not be tempted to do this on the lower
level `node-test-commit` job as it will not report the updated result back
to the PR). It will preserve all the green results from the current job but
to the PR.) It will preserve all the green results from the current job but
re-run everything else. Start a fresh CI by pressing "Retry" 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.
Expand Down
Loading