Docker Community Forums

Share and learn in the Docker community.

Autobuilds completely broken after move to GitHub Organization


(Micahzoltu) #1

I recently created a new GitHub organization with the name of my GitHub user (I renamed my GitHub user). After doing that, I followed the instructions online for re-linking my GitHub account to Docker Cloud and I am able to see my organization’s repositories and I am able to create new repositories with auto-builds triggered by pushes to the GitHub organization repositories.

However, existing repositories are currently in a completely broken state and I can’t build any of them.

  1. If I try to trigger a build it fails immediately with no useful error messaging. However, if I look in chrome dev tools I can see the following error:

    { "error": "Error trying to fetch last commit for 'Zoltu/docker-aspnetcore:master': 401 Client Error: Unauthorized for url:"}
  2. If I try to make any changes (even things that shouldn’t require talking to GitHub) to the build configuration the UI again gives me no error messages but again in chrome dev tools I see:

    {"error": "Error trying to create webhook for Zoltu/docker-aspnetcore: 401 Client Error: Unauthorized for url:"}
  3. (see other form post), I am unable to delete and recreate the repository with the same name! I would accept this as a temporary workaround, but I can’t have these repositories changing name yet I need them to be auto-building.

I am open to any suggestions that allow me to get back up and running, at the moment I can’t build any of my repositories other than building locally and pushing manually (unacceptable IMO).

(Ziontech) #2

It sounds like behind the scenes the authorisation token needed to access the GitHub Repo has been saved against the Docker Repo, now this token doesn’t perhaps work with the new GitHub account you’ve linked up and unfortunately every time you interact with the Docker Repo its trying to interact with the GitHub Repo (and breaking).

If you make a ticket at they should be able to disconnect the Docker Repo from the GitHub Repo, then you should be able to reconnect it.

(Ryan Kennedy) #3

@micahzoltu Thanks for the feedback. We are able to reproduce the issue and are working on a fix.

(Micahzoltu) #4

@pkennedyr What is the ETA on the fix? Is there any kind of manual workaround until a full fix is in place?

(Pablo Chico de Guzman Huerta) #5

Which are the affected docker repos? All the ones in the “Zoltu” organisation?
We are working on a proper fix, but I can manually fix your repos to make them working again.

(Micahzoltu) #6

@pchico83 As far as I can tell, all repos in the Zoltu organization are in this broken state. A manual fix would be very much appreciated.

(Pablo Chico de Guzman Huerta) #7

I made the changes manually. Could you confirm if it is working now?

(Micahzoltu) #8

This issue appears to be fixed. Thanks!