Description
Expected Behavior
GITHUB_CHECK_SUITE_ID is reliably available in tasks for PR builds.
Real Behavior
GITHUB_CHECK_SUITE_ID is often not set in tasks for first build in PR. Sometimes it is.
We're using a script to send information about the Cirrus task/build and GitHub check suite id to a separate API outside of Cirrus. It seems that for the first build after opening a PR, most of the time, the tasks do not have GITHUB_CHECK_SUITE_ID set in their environment. For subsequent builds triggered by pushes to the same branch, GITHUB_CHECK_SUITE_ID is set. For some tasks from PRs, GITHUB_CHECK_SUITE_ID is set in the first build, however.
Related Info
Example tasks with missing GITHUB_CHECK_SUITE_ID
https://cirrus-ci.com/task/4921244521332736
https://cirrus-ci.com/task/5722400206094336
Example task with GITHUB_CHECK_SUITE_ID set
https://cirrus-ci.com/task/5242627394633728
Let me know if I can provide any more information. Thanks.
This is a (tick one of the following):
- Website issue
- Link to page:
- Task issue
- OS: (Docker, macOS, Windows, FreeBSD)
- Task name: ubuntu22
- Script/cache name (if applies):