Skip to content
This repository has been archived by the owner on Mar 3, 2021. It is now read-only.

Buildkite builds cannot report status #84

Open
ash2k opened this issue Apr 8, 2020 · 0 comments
Open

Buildkite builds cannot report status #84

ash2k opened this issue Apr 8, 2020 · 0 comments

Comments

@ash2k
Copy link
Contributor

ash2k commented Apr 8, 2020

@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:

https://help.github.com/articles/enabling-third-party-application-restrictions-for-your-organization/

If that's the case, you'll need to "Grant or Request Access to Buildkite" here:

https://github.com/settings/connections/applications/3c5a9a8d50182605e362

Another thing to check is that your GitHub user account is connected to Buildkite, and has write access to the repositories:

https://buildkite.com/user/connected-apps

Once you've followed the above steps, check "Update commit statuses" here and save:

https://buildkite.com/bazel/atlassian-bazel-tools/settings/repository

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!).

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 :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant