You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 3, 2021. It is now read-only.
@obweger
Hi Hannes!
Could you help me re-enable the Buildkite integration for this repo please?
The webhook is configured correctly and builds are triggered, but they don't have permissions to report back. I've got this in the email from Buildkite:
Buildkite has automatically turned off GitHub commit status updates for the atlassian/bazel-tools pipeline. We kept getting 404's when trying to make API requests.
This can happen if someone has left your Buildkite or GitHub organization, or you've recently enabled third-party access restrictions:
If everything is set up correctly, GitHub commit status updates should start working again. If you keep seeing this issue, reply to this email and we'll dig further into what might be going wrong.
Status reporting stopped working when I left the company and I cannot seem to fix it even though I have access to this repository now (thanks, btw!).
I don't know what exactly is broken or needs to be done to fix the issue, but I also cannot troubleshoot because I'm no longer an org owner. Please help :)
The text was updated successfully, but these errors were encountered:
@obweger
Hi Hannes!
Could you help me re-enable the Buildkite integration for this repo please?
The webhook is configured correctly and builds are triggered, but they don't have permissions to report back. I've got this in the email from Buildkite:
Status reporting stopped working when I left the company and I cannot seem to fix it even though I have access to this repository now (thanks, btw!).
Builds are here and you can see there are daily builds but also builds for branches/PRs (i.e. the webhook works) https://buildkite.com/bazel/atlassian-bazel-tools
I don't know what exactly is broken or needs to be done to fix the issue, but I also cannot troubleshoot because I'm no longer an org owner. Please help :)
The text was updated successfully, but these errors were encountered: