No way to change source project for automated build

[freeformz]

For whatever reason (there are several) heroku/cedar is setup to build from tt/stack-images. We'd like to be able to change the source project to heroku/stack-images instead w/o having to nuke the automated build / project and break everyone's links.

[danlamanna]

+1

[tt]

👍

[hg-jt]

+1

[markshust]

👍

[jlsalvador]

👍 Do you need some help to make that this happens?

[nhumrich]

👍

[kennylim86]

+1

[ghost]

👍

[shokohara]

👍

[zmarty]

👍

[samos123]

+1

[davidcarboni]

+1

[raphi]

+1

[nuxlli]

👍

[sjackman]

👍

[jangorecki]

👍

[btiernay]

👍

[andrew804]

👍

[Mahmoudz]

👍

[greyltc]

👍 This feature is pretty important to me.

[bharath-cchmc]

+1

[Dids]

+1 especially now that Github's gone all unlimited on us, so we can finally move from Bitbucket to Github, which would break automated Docker Hub builds.

[pchico83]

This is supported in Docker Cloud Build service, we are prioritizing build development in Docker Cloud over Docker Hub.

[hurricanehrndz]

+1

[cyrille-leclerc]

+1

[hrchu]

+1

[jljorgenson18]

+1

[svlentink]

+1

[micahwedemeyer]

👍

[elcodedocle]

+1

[rgeorgeoff]

+1

[toschneck]

unfortunately the docker-cloud builds are pretty unstable, so also a 👍 from me!
Especially if you get forced by the Docker brand guidelines https://www.docker.com/brand-guidelines to rename your github repository, you currently have no option to do this without loss of all your docker-hub repository stars and comments 😞

[rafaelstz]

+1

[t3chn0m4g3]

+1

[Arno0x]

+1

[rgerkin]

+1

[pkennedyr]

Support for modifying the source project of an automated build is currently available in Docker Cloud. We encourage you to try out Docker Cloud as this is where you will find support for this and many other autobuild features.

Also, marking this thread as won't fix since product development is currently focused on Docker Cloud: https://forums.docker.com/t/future-updates-on-docker-hub-docker-cloud/20498

[michaelmior]

To clarify how this works (since I just did it for one of my own projects), here are the steps:

1. Log on to Docker Hub and under the Build Settings for the appropriate repository, uncheck " When active, builds will happen automatically on pushes."
2. Log on to Docker Cloud.
3. Under "Cloud Settings" (left menu) click the plug next to GitHub to authenticate.
4. Back on Docker Cloud, go to the Repositories section (left menu).
5. Select the same Docker repository you want to build (which should already exist).
6. Under the Builds tab, select "Configure Automated Builds"
7. Select the new repository and branch from GitHub using the dropdown menus.
8. Select "Build on Docker Cloud's infrastructure" and pick any node type.
9. Click "Save and Build"

Now you're done and the image should be built from the new GitHub repository.

[crayfishx]

I followed the above steps outlined by @michaelmior (thanks for that!). Although the image is now building from the correct source repo there is still an issue with some metadata on the Docker hub site. https://hub.docker.com/r/crayfishx/jerakia/ was moved from the GitHub repo crayfishx/jerakia-docker to crayfishx/jerakia - the build is working but there are two issues....

• The "source repository" link on the main page still points to the old GitHub repo
• Clicking "build details" and the latest build shows the old Dockerfile and build details despite the actual image being correct

Anyone know what I need to do to get Docker Hub to "forget" the old builds and repo?

Thanks

[gdvalderrama]

@mghazizadeh Yes, you can change the repository in docker cloud, but I can't change the service (eg: I can't change the source from bitbucket to github).

[petk]

I understand that there are a lot of old services needed to be maintained but coming from the docs where it says that the hub.docker.php is the main Docker public registry and not having any advanced features there anymore is inconsistency and strange approach. Images are still pulled from hub.docker.com...

Plus not to mention, stars are gone when recreating the repository on hub.docker.com :)

[kjeldflarup]

@petk There is a possibility to create a new image, and then change Dockerfile for the current to

from newimage:tag

[vveider]

@kjeldflarup - that's not it, unfortunately.

[olivierdalang]

@crayfishx Did you find a way to change the link to the source repo and the dockerfiles details ?

[philippgille]

A few weeks ago there has been the announcement that Docker Cloud and Docker Store would now be part of Docker Hub: https://blog.docker.com/2018/12/the-new-docker-hub/

But it seems that it's still not possible to change the underlying GitHub repo of a Docker repo. I'm currently looking on https://cloud.docker.com/repository/docker/<user>/<repo>/hubbuilds.

@pkennedyr: You closed this issue two years ago. Maybe you can reopen it because according to the blog post Docker Hub is now the focus of development and the feature is really useful?