GeezerVison is showing github.com — doc: add note on visibility of CI failures to new contributor guide · nodejs/node@da88f70
File tree
Expand file treeCollapse file tree
Open diff view settings
Expand file treeCollapse file tree
Open diff view settings
Collapse file
Copy file name to clipboardExpand all lines: doc/contributing/first-contributions.md +9Lines changed: 9 additions & 0 deletions - Display the source diff
- Display the rich diff
| Original file line number | Diff line number | Diff line change |
|---|
@@ -168,6 +168,15 @@ before approving the CI runs. Similar to the review process, be patient and resp |
168 | 168 | the volunteers' time when you are asking for help to trigger the CI runs, this helps build |
169 | 169 | trust to make future contributions smoother. |
170 | 170 |
|
| 171 | +### Q: The Jenkins CI failed, but when I clicked the CI link, it shows "Access Denied". What should I do? |
| 172 | + |
| 173 | +Read access to the Jenkins CI is restricted to a few teams in the Node.js organization. You will |
| 174 | +need to ask a member of these teams (for example, any of the collaborators) to show you the details |
| 175 | +of the failures. If after a day or so from a collaborator triggering a Jenkins CI your PR shows a |
| 176 | +failure in either the `node-test-pull-request` or `node-test-commit-*` checks it's worth adding a |
| 177 | +comment to the PR asking what tests are failed, as the collaborator may not realise that you cannot |
| 178 | +see the results directly. |
| 179 | + |
171 | 180 | ### Q: The CI runs showed some failures that seem unrelated to my change. What should I do? |
172 | 181 |
|
173 | 182 | The Node.js CIs are known to be flaky. Consult the daily reports in |
|