GeezerVison

The World Wide Web, restored to 800 pixels of glory.

GeezerVison is showing github.com — doc: update CI instructions by aduh95 · Pull Request #57743 · nodejs/node

doc: update CI instructions #57743

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.

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

Merged

nodejs-github-bot merged 1 commit into nodejs:main from aduh95:retry-ci-changes

Apr 6, 2025

Uh oh!

There was an error while loading. Please reload this page.

Merged

doc: update CI instructions #57743

Changes from all commits

Commits

Show all changes

1 commit

Select commit

43939bc

doc: update CI instructions

aduh95 Apr 4, 2025

File filter

Filter by extension .md (1) All 1 file type selected

Viewed files

Clear filters

Conversations

Failed to load comments.

Uh oh!

There was an error while loading. Please reload this page.

Jump to

Jump to file

Failed to load files.

Uh oh!

There was an error while loading. Please reload this page.

Diff view

Unified

Split

Hide whitespace

Diff view

Unified

Split

Hide whitespace

There are no files selected for viewing

10 changes: 5 additions & 5 deletions 10 doc/contributing/collaborator-guide.md

Show comments

View file

Open in desktop

Original file line number	Diff line number	Diff line change
Expand Up		@@ -252,13 +252,13 @@ 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. It will preserve all the green results from the
		current job but re-run everything else. Start a fresh CI 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.
		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 pressing "Retry" on
		the left sidebar, or by adding the `request-ci` label to the pull request.
		CI run, a fresh CI run is required. It can be started by adding the `request-ci`
		label to the pull request.

		#### Useful Jenkins CI jobs

Expand Down

Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.

You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.