Skip to content

doc: add Retry CI in collaborator guide #44130

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

Merged
nodejs-github-bot merged 4 commits into from
Aug 6, 2022
Merged

doc: add Retry CI in collaborator guide #44130

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
467a2a6
doc: add Retry CI in collaborator guide
LiviaMedeiros Aug 4, 2022
5b61784
squash: fixup
LiviaMedeiros Aug 4, 2022
b6c73d2
squash: fixup
LiviaMedeiros Aug 4, 2022
57e4b89
squash: fixup
LiviaMedeiros Aug 4, 2022
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
Next Next commit
squash: fixup 
Co-authored-by: Tobias Nießen <tniessen@tnie.de>
  • Loading branch information
@LiviaMedeiros @tniessen
LiviaMedeiros and tniessen authored Aug 4, 2022
commit b6c73d23ae4c65203554f2c68ebb1bbc2af59d61
2 changes: 1 addition & 1 deletion doc/contributing/collaborator-guide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -255,7 +255,7 @@ 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 `request-ci` label to the pull request.
sidebar, or by adding the `request-ci` label to the pull request.

#### Useful Jenkins CI jobs

Expand Down