clearlinux/docker
2
0
Fork 0
mirror of https://github.com/clearlinux/docker.git synced 2026-10-03 15:28:35 +00:00
Code Issues Packages Projects Releases Wiki Activity

Changed all references from Trusted Builds to Automated Builds

Browse Source 
* Updated docker images output
* Deprecated docker images -t/--trusted option and replace with --automated
* Changed *trusted variables to *automated
* Changed added support for is_automated alongside deprecated is_trusted
* Updated man pages, docs and completion
* Updated API documentation

Docker-DCO-1.1-Signed-off-by: James Turnbull <james@lovedthanlost.net> (github: jamtur01)
This commit is contained in:
James Turnbull
2014-06-03 12:55:30 -07:00
parent 2f514fb891
commit 9fc8028c98
12 changed files with 36 additions and 31 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/sources/docker-io/builds.md
+5 -6
View File
@@ -1,6 +1,6 @@
page_title: Automated Builds on Docker.io
page_description: Docker.io Automated Builds
page_keywords: Docker, docker, registry, accounts, plans, Dockerfile, Docker.io, docs, documentation, trusted, builds, trusted builds, automated builds
page_keywords: Docker, docker, registry, accounts, plans, Dockerfile, Docker.io, docs, documentation, trusted, builds, trusted builds, automated, automated builds
# Automated Builds on Docker.io
## Automated Builds
@@ -101,10 +101,9 @@ to Docker.io.
#### Creating an Automated Build
You can [create a Trusted
Build](https://index.docker.io/builds/bitbucket/select/)
from any of your public or private BitBucket repositories with a
`Dockerfile`.
You can [create an Automated
Build](https://index.docker.io/builds/bitbucket/select/) from any of
your public or private BitBucket repositories with a `Dockerfile`.
### The Dockerfile and Automated Builds
@@ -162,7 +161,7 @@ payload:
"repository":{
"status":"Active",
"description":"my docker repo that does cool things",
"is_trusted":false,
"is_automated":false,
"full_description":"This is my full description",
"repo_url":"https://index.docker.io/u/username/reponame/",
"owner":"username",
docs/sources/docker-io/repos.md
+1 -1
View File
@@ -81,7 +81,7 @@ with a JSON payload similar to the example shown below.
"repository":{
"status":"Active",
"description":"my docker repo that does cool things",
"is_trusted":false,
"is_automated":false,
"full_description":"This is my full description",
"repo_url":"https://index.docker.io/u/username/reponame/",
"owner":"username",
docs/sources/examples/mongodb.md
+1 -1
View File
@@ -151,4 +151,4 @@ as daemon process(es).
- [Linking containers](/userguide/dockerlinks)
- [Cross-host linking containers](/articles/ambassador_pattern_linking/)
- [Creating a Trusted Build](/docker-io/builds/#trusted-builds)
- [Creating an Automated Build](/docker-io/builds/#automated-builds)
docs/sources/reference/api/docker_remote_api.md
+3
View File
@@ -47,6 +47,9 @@ Build now has support for the `forcerm` parameter to always remove containers
**New!**
All the JSON keys are now in CamelCase
**New!**
Trusted builds are now Automated Builds - `is_trusted` is now `is_automated`.
## v1.11
### Full Documentation
docs/sources/reference/api/docker_remote_api_v1.12.md
+3 -3
View File
@@ -1002,21 +1002,21 @@ Search for an image on [Docker.io](https://index.docker.io).
{
"description": "",
"is_official": false,
"is_trusted": false,
"is_automated": false,
"name": "wma55/u1210sshd",
"star_count": 0
},
{
"description": "",
"is_official": false,
"is_trusted": false,
"is_automated": false,
"name": "jdswinbank/sshd",
"star_count": 0
},
{
"description": "",
"is_official": false,
"is_trusted": false,
"is_automated": false,
"name": "vgauthier/sshd",
"star_count": 0
}
docs/sources/reference/commandline/cli.md
+1 -1
View File
@@ -1124,7 +1124,7 @@ Search [Docker.io](https://index.docker.io) for images
--no-trunc=false Don't truncate output
-s, --stars=0 Only displays with at least xxx stars
-t, --trusted=false Only show trusted builds
--automated=false Only show automated builds
See [*Find Public Images on Docker.io*](
/userguide/dockerrepos/#find-public-images-on-dockerio) for
docs/sources/userguide/dockerimages.md
+6 -4
View File
@@ -116,7 +116,7 @@ by using the `docker search` command to find all the images that contain the
term `sinatra`.
$ sudo docker search sinatra
NAME DESCRIPTION STARS OFFICIAL TRUSTED
NAME DESCRIPTION STARS OFFICIAL AUTOMATED
training/sinatra Sinatra training image 0 [OK]
marceldegraaf/sinatra Sinatra test app 0
mattwarren/docker-sinatra-demo 0 [OK]
@@ -129,9 +129,11 @@ term `sinatra`.
We can see we've returned a lot of images that use the term `sinatra`. We've
returned a list of image names, descriptions, Stars (which measure the social
popularity of images - if a user likes an image then they can "star" it), and
the Official and Trusted statuses. Official repositories are XXX and Trusted
repositories are [Trusted Build](/userguide/dockerrepos/) that allow you to
validate the source and content of an image.
the Official and Automated build statuses. Official repositories are built and
maintained by the [Stackbrew](https://github.com/dotcloud/stackbrew) project,
and Automated repositories are [Automated Builds](
/userguide/dockerrepos/#automated-builds) that allow you to validate the source
and content of an image.
We've reviewed the images available to use and we decided to use the
`training/sinatra` image. So far we've seen two types of images repositories,
docs/sources/userguide/index.md
+1 -1
View File
@@ -76,7 +76,7 @@ Go to [Managing Data in Containers](/userguide/dockervolumes).
Now we've learned a bit more about how to use Docker we're going to see
how to combine Docker with the services available on Docker.io including
Trusted Builds and private repositories.
Automated Builds and private repositories.
Go to [Working with Docker.io](/userguide/dockerrepos).