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

Open
sxa wants to merge 1 commit into
base: main
Choose a base branch
from
+8 −6
Open

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

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
14 changes: 8 additions & 6 deletions doc/contributing/collaborator-guide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -267,12 +267,14 @@ If there are GitHub Actions CI failures unrelated to the change in the pull
request, try the "🔄 Re-run all jobs" button, on the right-hand side of the
"Checks" tab.

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. 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.
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
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
Comment on lines +271 to +274
Copy link
Member

@tniessen tniessen Jan 14, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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
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
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
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

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.

If new commits are pushed to the pull request branch after the latest Jenkins
CI run, a fresh CI run is required. It can be started by adding the `request-ci`
Expand Down
Loading