Repository navigation
request-ci fails without error when CI is locked down #39746
Copy link
Copy link
Closed as not planned
Labels
buildIssues and PRs related to Node.js builds or CI infrastructure.Issues and PRs related to Node.js builds or CI infrastructure.metaIssues and PRs related to the general management of the project.Issues and PRs related to the general management of the project.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.
Description
Activity
- addedbuildIssues and PRs related to Node.js builds or CI infrastructure.Issues and PRs related to Node.js builds or CI infrastructure.metaIssues and PRs related to the general management of the project.Issues and PRs related to the general management of the project.
on Aug 12, 2021 @nodejs/actions
We should handle the error but during a CI lockdown I think it's expected that
request-ciwould not start CI's.during a CI lockdown I think it's expected that request-ci would not start CI's
agreed
I'm fairly certain this is a node-core-utils issue.
github-actions commented
on Jun 27, 2026 on Jun 27, 2026 – with GitHub ActionsContributorMore actionsThis issue has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.- addedstaleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.
on Jun 27, 2026 github-actions commented
on Jul 28, 2026 on Jul 28, 2026 – with GitHub ActionsContributorMore actionsThis issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 120 days).
If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.
Metadata
Metadata
Assignees
Labels
buildIssues and PRs related to Node.js builds or CI infrastructure.Issues and PRs related to Node.js builds or CI infrastructure.metaIssues and PRs related to the general management of the project.Issues and PRs related to the general management of the project.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.
See #39725 (comment)
The
request-cilabel was removed but therequest-ci-failedlabel was not added.I don't know what the Jenkins API responds in this case, but it doesn't seem like we handle it.
Workflow run: https://github.com/nodejs/node/runs/3296324085?check_suite_focus=true