diff --git a/docker-hub/builds/classic-vs-enhanced.md b/docker-hub/builds/classic-vs-enhanced.md deleted file mode 100644 index 409dafefa9..0000000000 --- a/docker-hub/builds/classic-vs-enhanced.md +++ /dev/null @@ -1,56 +0,0 @@ ---- -description: Explains the differece between Classic and Enhanced Automated Builds -keywords: automated, build, images -title: Classic vs Enhanced Automated Builds ---- - -With the launch of the new Docker Hub, we are introducing Enhanced Automated Build. - -Automated builds created using the old Docker Hub are now Classic Automated Builds, and automated builds created -using the old Docker Cloud are now Enhanced Automated Build. - -All new automated builds created going forward will be Enhanced Automated Build. If you are creating an Enhanced -Automated Build for the first time, see [docs](index.md#configure-automated-build-settings). - -In the coming months, we will gradually convert Classic Automated Builds into Enhanced Automated Builds. This should -be a seamless process for most users. - - -## Managing Classic Automated Builds - -You can manage both Classic and Enhanced Automated Builds from the **Builds** tab - -Repository with Classic Automated Build: - -![A Classic Automated Build dashboard](images/classic-vs-enhanced-classic-only.png) - -You can configure build settings pretty much the same way as 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 Enhanced Automated Builds. - -Enhanced Automated Build is displayed by default. You can switch to Classic Automated Build by clicking on this link at the top - -![Switching to Classic Automated Build](images/classic-vs-enhanced-switch-to-classic.png) - -Likewise, you can switch back to Enhanced Automated Build by clicking on this link at the top - -![Switching to Enhanced Automated Build](images/classic-vs-enhanced-switch-to-enhanced.png) - - -## Frequently asked questions - -1. I've previously linked my Github/Bitbucket account in the old Docker Hub. Do I need to re-link it? - -Unless you've linked your Github/Bitbucket account with the old Docker Cloud previously, you will need to [re-link](link-source.md) it -with the new Docker Hub. - -2. What happens to my old Docker Hub automated builds? - -They are now Classic Automated Builds. There are no functional difference with the old automated builds and everything -(build triggers, existing build rules etc) should continue to work seamlessly - -3. Is it possible to convert an existing Classic Automated Build into Enhanced Automated Build? - -This is currently unsupported. However, we are working to transition all builds into Enhanced Automated Build in -the coming months. diff --git a/docker-hub/builds/classic-vs-new.md b/docker-hub/builds/classic-vs-new.md new file mode 100644 index 0000000000..0e3a3fd29f --- /dev/null +++ b/docker-hub/builds/classic-vs-new.md @@ -0,0 +1,59 @@ +--- +description: Explains the difference between Classic and new Automated Builds +keywords: automated, build, images +title: Classic vs new Automated Builds +--- + +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](index.md#configure-automated-build-settings). + +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: + +![A Classic Automated Build dashboard](images/classic-vs-new-classic-only.png) + + 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 + +![Switching to Classic Automated Build](images/classic-vs-new-switch-to-classic.png) + +Likewise, you can switch back to new Automated Build by clicking on this link at the top + +![Switching to new Automated Build](images/classic-vs-new-switch-to-new.png) + + +## Frequently Asked Questions + +1. I've previously linked my Github/Bitbucket account in the old Docker Hub. Why do I need to re-link it? + +The new Docker Hub uses a different permissions model. [Linking is only a few clicks by going to account settings](link-source.md). +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](automated-build.md#service-users-for-team-autobuilds) for the team before linking the account as described below. + + +2. What happens to automated builds I created in the old Docker Hub? + +They are now Classic Automated Builds. There are no functional differences with the old automated builds and everything +(build triggers, existing build rules etc) should continue to work seamlessly. + +3. Is it possible to convert an existing Classic Automated Build? + +This is currently unsupported. However, we are working to transition all builds into new experience in +the coming months. diff --git a/docker-hub/builds/images/classic-vs-enhanced-classic-only.png b/docker-hub/builds/images/classic-vs-new-classic-only.png similarity index 100% rename from docker-hub/builds/images/classic-vs-enhanced-classic-only.png rename to docker-hub/builds/images/classic-vs-new-classic-only.png diff --git a/docker-hub/builds/images/classic-vs-enhanced-switch-to-classic.png b/docker-hub/builds/images/classic-vs-new-switch-to-classic.png similarity index 100% rename from docker-hub/builds/images/classic-vs-enhanced-switch-to-classic.png rename to docker-hub/builds/images/classic-vs-new-switch-to-classic.png diff --git a/docker-hub/builds/images/classic-vs-enhanced-switch-to-enhanced.png b/docker-hub/builds/images/classic-vs-new-switch-to-new.png similarity index 100% rename from docker-hub/builds/images/classic-vs-enhanced-switch-to-enhanced.png rename to docker-hub/builds/images/classic-vs-new-switch-to-new.png diff --git a/docker-hub/builds/index.md b/docker-hub/builds/index.md index 1345a9274c..0ed1ea6f5f 100644 --- a/docker-hub/builds/index.md +++ b/docker-hub/builds/index.md @@ -35,7 +35,7 @@ image. Automated tests do not push images to the registry on their own. [Learn m ## Configure automated build settings > **Note**: Automated builds created with the old Docker Hub are -now Classic Automated Builds. [Learn more](classic-vs-enhanced.md) +now Classic Automated Builds. [Learn more](classic-vs-new.md) You can configure repositories in Docker Hub so that they automatically build an image each time you push new code to your source provider. If you have