Classic Automated BuildsEstimated reading time: 2 minutes
With the launch of the new Docker Hub, we are introducing an improved Automated Build experience.
Automated Builds created using an older version of Docker Hub are now labelled “Classic”. If you were using Docker Cloud to manage builds, your builds are already the latest version of Automated Builds.
All automated builds created going forward will get the new experience. If you are creating a new Automated Build for the first time, see docs.
In the coming months, we will gradually convert Classic Automated Builds into new Automated Builds. This should be a seamless process for most users.
Managing Classic Automated Builds
You can manage both Classic and new Automated Builds from the Builds tab
Repository with Classic Automated Build:
Build settings can be configured similarly to those on the old Docker Hub.
If you have previously created an automated build in both the old Docker Hub and Docker Cloud, you can switch between Classic and new Automated Builds.
New Automated Build is displayed by default. You can switch to Classic Automated Build by clicking on this link at the top
Likewise, you can switch back to new Automated Build by clicking on this link at the top
Adding Github webhook manually
A GitHub webhook allows GitHub to notify Docker Hub when something has been committed to a given Git repository.
When you create a Classic Automated Build, a webhook should get automatically added to your GitHub repository.
To add, confirm, or modify the webhook, log in to GitHub, then navigate to the repository. Within the repository, select Settings > Webhooks. You must have admin privileges on the repository to view or modify this setting. Click Add webhook, and use the following settings:
|Which events would you like to trigger this webhook?||Just the push event|
The image below shows the Webhooks/Add webhook form with the above settings reflected:
If configured correctly, you’ll see this in the Webhooks view
Frequently Asked Questions
Q: I’ve previously linked my GitHub/Bitbucket account in the old Docker Hub. Why do I need to re-link it?
A: The new Docker Hub uses a different permissions model. Linking is only a few clicks by going to account settings. with the new Docker Hub.
Note: If you are linking a source code provider to create autobuilds for a team, follow the instructions to create a service account for the team before linking the account as described below.
Q: What happens to automated builds I created in the old Docker Hub?
A: They are now Classic Automated Builds. There are no functional differences with the old automated builds and everything (build triggers, existing build rules) should continue to work seamlessly.
Q: Is it possible to convert an existing Classic Automated Build?
A: This is currently unsupported. However, we are working to transition all builds into new experience in the coming months.automated, build, images