Skip to content

Commit 6060eed

Browse files
SvenDowideitArnaud Porterie
authored andcommitted
The Hub build webhooks now list the images that have been built
And fix some spelling - repo isn't really a word :) Signed-off-by: Sven Dowideit <SvenDowideit@home.org.au>
1 parent d217da8 commit 6060eed

File tree

2 files changed

+18
-10
lines changed

2 files changed

+18
-10
lines changed

docs/sources/docker-hub/builds.md

Lines changed: 12 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ page_keywords: Docker, docker, registry, accounts, plans, Dockerfile, Docker Hub
88

99
*Automated Builds* are a special feature of Docker Hub which allow you to
1010
use [Docker Hub's](https://hub.docker.com) build clusters to automatically
11-
create images from a specified `Dockerfile` and a GitHub or Bitbucket repo
11+
create images from a specified `Dockerfile` and a GitHub or Bitbucket repository
1212
(or "context"). The system will clone your repository and build the image
1313
described by the `Dockerfile` using the repository as the context. The
1414
resulting automated image will then be uploaded to the Docker Hub registry
@@ -148,7 +148,7 @@ https://registry.hub.docker.com/associate/bitbucket/).
148148

149149
Then follow the onscreen instructions to authorize and link your
150150
Bitbucket account to Docker Hub. Once it is linked, you'll be able
151-
to choose a repo from which to create the Automatic Build.
151+
to choose a repository from which to create the Automatic Build.
152152

153153
### Creating an Automated Build
154154

@@ -159,7 +159,7 @@ public or private Bitbucket repositories with a `Dockerfile`.
159159
### Adding a Hook
160160

161161
When you link your Docker Hub account, a `POST` hook should get automatically
162-
added to your Bitbucket repo. Follow the steps below to confirm or modify the
162+
added to your Bitbucket repository. Follow the steps below to confirm or modify the
163163
Bitbucket hooks for your Automated Build:
164164

165165
<table class="table table-bordered">
@@ -195,8 +195,8 @@ Bitbucket hooks for your Automated Build:
195195

196196
During the build process, Docker will copy the contents of your `Dockerfile`.
197197
It will also add it to the [Docker Hub](https://hub.docker.com) for the Docker
198-
community (for public repos) or approved team members/orgs (for private repos)
199-
to see on the repository page.
198+
community (for public repositories) or approved team members/orgs (for private
199+
repositories) to see on the repository page.
200200

201201
### README.md
202202

@@ -217,7 +217,7 @@ Automated Build, it will give you a URL to which you can send POST requests.
217217
This will trigger the Automated Build, much as with a GitHub webhook.
218218

219219
Build triggers are available under the Settings menu of each Automated Build
220-
repo on the Docker Hub.
220+
repository on the Docker Hub.
221221

222222
![Build trigger screen](/docker-hub/hub-images/build-trigger.png)
223223

@@ -249,7 +249,11 @@ payload:
249249
{
250250
"callback_url": "https://registry.hub.docker.com/u/svendowideit/testhook/hook/2141b5bi5i5b02bec211i4eeih0242eg11000a/",
251251
"push_data": {
252-
"images": [],
252+
"images": [
253+
"27d47432a69bca5f2700e4dff7de0388ed65f9d3fb1ec645e2bc24c223dc1cc3",
254+
"51a9c7c1f8bb2fa19bcd09789a34e63f35abb80044bc10196e304f6634cc582c",
255+
...
256+
],
253257
"pushed_at": 1.417566161e+09,
254258
"pusher": "trustedbuilder"
255259
},
@@ -336,7 +340,7 @@ another. If one gets updated,the linking system triggers a rebuild
336340
for the other Automated Build. This makes it easy to keep all your
337341
Automated Builds up to date.
338342

339-
To add a link, go to the repo for the Automated Build you want to
343+
To add a link, go to the repository for the Automated Build you want to
340344
link to and click on *Repository Links* under the Settings menu at
341345
right. Then, enter the name of the repository that you want have linked.
342346

docs/sources/docker-hub/repos.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -111,7 +111,11 @@ similar to the example shown below.
111111
{
112112
"callback_url": "https://registry.hub.docker.com/u/svendowideit/busybox/hook/2141bc0cdec4hebec411i4c1g40242eg110020/",
113113
"push_data": {
114-
"images": [],
114+
"images": [
115+
"27d47432a69bca5f2700e4dff7de0388ed65f9d3fb1ec645e2bc24c223dc1cc3",
116+
"51a9c7c1f8bb2fa19bcd09789a34e63f35abb80044bc10196e304f6634cc582c",
117+
...
118+
],
115119
"pushed_at": 1.417566822e+09,
116120
"pusher": "svendowideit"
117121
},
@@ -135,7 +139,7 @@ similar to the example shown below.
135139

136140
Webhooks allow you to notify people, services and other applications of
137141
new updates to your images and repositories. To get started adding webhooks,
138-
go to the desired repo in the Hub, and click "Webhooks" under the "Settings"
142+
go to the desired repository in the Hub, and click "Webhooks" under the "Settings"
139143
box.
140144

141145
> **Note:** For testing, you can try an HTTP request tool like

0 commit comments

Comments
 (0)