GeezerVison

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

GeezerVison is showing github.com — doc: add Retry CI in collaborator guide · nodejs/node@eded43c

File tree

Expand file treeCollapse file tree

Open diff view settings

Filter options

doc/contributing
- collaborator-guide.md

Expand file treeCollapse file tree

Open diff view settings

Collapse file

`‎doc/contributing/collaborator-guide.md‎`

Copy file name to clipboardExpand all lines: doc/contributing/collaborator-guide.md

+4Lines changed: 4 additions & 0 deletions

Display the source diff
Display the rich diff

Original file line number	Diff line number	Diff line change
`@@ -253,6 +253,10 @@ current job but re-run everything else. Start a fresh CI if more than seven days`
`253`	`253`	`have elapsed since the original failing CI as the compiled binaries for the`
`254`	`254`	`Windows and ARM platforms are only kept for seven days.`
`255`	`255`
	`256`	`+If new commits are pushed to the pull request branch after the latest Jenkins`
	`257`	`+CI run, a fresh CI run is required. It can be started by pressing "Retry" on`
	`258`	+the left sidebar, or by adding the `request-ci` label to the pull request.
	`259`	`+`
`256`	`260`	`#### Useful Jenkins CI jobs`
`257`	`261`
`258`	`262`	* [`node-test-pull-request`](https://ci.nodejs.org/job/node-test-pull-request/)

0 commit comments

Comments

0 (0)

You are visitor 01402503 — 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.