doc: add note on visibility of CI failures to new contributor guide

sxa · aduh95 · commit f072603344bb · 2026-07-21T15:24:49.000+02:00
Signed-off-by: Stewart X Addison <sxa@ibm.com> PR-URL: #64256 Reviewed-By: Richard Lau <richard.lau@ibm.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: Ulises Gascón <ulisesgascongonzalez@gmail.com>
diff --git a/doc/contributing/first-contributions.md b/doc/contributing/first-contributions.md
@@ -168,6 +168,15 @@ before approving the CI runs. Similar to the review process, be patient and resp
 the volunteers' time when you are asking for help to trigger the CI runs, this helps build
 trust to make future contributions smoother.
 
+### Q: The Jenkins CI failed, but when I clicked the CI link, it shows "Access Denied". What should I do?
+
+Read access to the Jenkins CI is restricted to a few teams in the Node.js organization. You will
+need to ask a member of these teams (for example, any of the collaborators) to show you the details
+of the failures. If after a day or so from a collaborator triggering a Jenkins CI your PR shows a
+failure in either the `node-test-pull-request` or `node-test-commit-*` checks it's worth adding a
+comment to the PR asking what tests are failed, as the collaborator may not realise that you cannot
+see the results directly.
+
 ### Q: The CI runs showed some failures that seem unrelated to my change. What should I do?
 
 The Node.js CIs are known to be flaky. Consult the daily reports in
