Skip to content

Commit a923fa5

Browse files
feedback1
Signed-off-by: Craig <[email protected]>
1 parent 387d34c commit a923fa5

File tree

2 files changed

+12
-14
lines changed

2 files changed

+12
-14
lines changed

content/manuals/docker-hub/repos/manage/builds/_index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ image. The built image is then pushed to Docker Hub.
2828
> You can still use `docker push` to push pre-built images to
2929
repositories with automated builds configured.
3030

31-
If you have automated tests configured, these run after building but before
31+
If you have automated tests configured, these run after building, but before
3232
pushing to the registry. You can use these tests to create a continuous
3333
integration workflow where a build that fails its tests doesn't push the built
3434
image. Automated tests don't push images to the registry on their own. [Learn about automated image testing](automated-testing.md).

content/manuals/docker-hub/repos/manage/builds/setup.md

Lines changed: 11 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -15,11 +15,6 @@ aliases:
1515
> Automated builds require a
1616
> Docker Pro, Team, or Business subscription.
1717
18-
This page contains information on:
19-
- [Configuring automated builds](#configure-automated-builds)
20-
- [Advanced automated build options](#advanced-automated-build-options)
21-
- [Automated builds for teams](#autobuild-for-teams)
22-
2318
## Configure automated builds
2419

2520
You can configure repositories in Docker Hub so that they automatically
@@ -47,7 +42,7 @@ when the tests succeed.
4742
> the source code provider. Once you select a user, source code
4843
> repositories appear in the **Select repository** drop-down list.
4944
50-
5. Optional: Enable [autotests](automated-testing.md#enable-automated-tests-on-a-repository).
45+
5. Optional. Enable [autotests](automated-testing.md#enable-automated-tests-on-a-repository).
5146

5247
6. Review the default **Build Rules**.
5348

@@ -56,10 +51,11 @@ when the tests succeed.
5651
within the Docker repository.
5752

5853
A default build rule is set up for you, which you can edit or delete. This
59-
default rule sets builds from the `Branch` in your source code repository called
60-
`master` or `main`, and creates a Docker image tagged with `latest`. For more information, see [set up build rules](#set-up-build-rules)
54+
default rule sets builds from the `Branch` in your source code repository
55+
called `master` or `main`, and creates a Docker image tagged with `latest`.
56+
For more information, see [set up build rules](#set-up-build-rules).
6157

62-
7. Optional: Select the **plus** icon to add and [configure more build rules](#set-up-build-rules).
58+
7. Optional. Select the **plus** icon to add and [configure more build rules](#set-up-build-rules).
6359

6460
8. For each branch or tag, enable or disable the **Autobuild** toggle.
6561

@@ -279,9 +275,11 @@ variable to automated builds associated with the account. For more information,
279275
2. Create a "build" team in your organization.
280276
3. Ensure that the new "build" team has access to each repository and submodule you need to build.
281277

282-
Go to the repository's **Settings** page. On GitHub, add the new "build" team
283-
to the list of **Collaborators and Teams**. On Bitbucket, add the "build" team
284-
to the list of approved users on the **Access management** screen.
278+
1. On GitHub or Bitbucket, go to the repository's **Settings** page.
279+
2. Add the new "build" team to the list of approved users.
280+
281+
- GitHub: Add the team in **Collaborators and Teams**.
282+
- Bitbucket: Add the team in **Access management**.
285283

286284
4. Add the service user to the "build" team on the source provider.
287285

@@ -291,7 +289,7 @@ variable to automated builds associated with the account. For more information,
291289
>
292290
> You may need to sign out of your individual account on the source code provider to create the link to the service account.
293291
294-
6. Optional: Use the SSH keys you generated to set up any builds with private submodules, using the service account and [the previous instructions](troubleshoot.md#build-repositories-with-linked-private-submodules).
292+
6. Optional. Use the SSH keys you generated to set up any builds with private submodules, using the service account and [the previous instructions](troubleshoot.md#build-repositories-with-linked-private-submodules).
295293

296294
## What's Next?
297295

0 commit comments

Comments
 (0)