docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

added step to choose stable or edge version in Cloud autobuilds (#3395) 

Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
This commit is contained in:
Victoria Bialas 2017-05-24 14:55:29 -07:00 committed by GitHub
parent fdedf787fa
commit 559bb0d668
1 changed files with 44 additions and 24 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

68
docker-cloud/builds/automated-build.md
View File

@ -58,17 +58,31 @@ the code repository service where the image's source code is stored.
5. Choose where to run your build processes. 5. Choose where to run your build processes.
You can either run the process on your own infrastructure and optionally You can either run the process on your own infrastructure and optionally [set up specific nodes to build on](automated-build.md#set-up-builder-nodes), or select **Build on Docker Cloud’s infrastructure** you can use the hosted build service
[set up specific nodes to build on](automated-build.md#set-up-builder-nodes), or you can use the offered on Docker Cloud's infrastructure. If you use
hosted build service offered on Docker Cloud's infrastructure. If you use Docker's infrastructure, select a builder size to run the build
Docker's infrastructure, select a builder size to run the build process on. process on. This hosted build service is free while it is in Beta.
This hosted build service is free while it is in Beta.
![](images/edit-repository-builds.png) ![](images/edit-repository-builds.png)
6. Optionally, enable [autotests](automated-testing.md#enable-automated-tests-on-a-repository). 6. If in the previous step you selected **Build on Docker
Cloud’s infrastructure**, then you are given the option to select the
**Docker Version** used to build this repository. You can choose between
the **Stable** and **Edge** versions of Docker.
8. Review the default **Build Rules**, and optionally click the **plus sign** to add and configure more build rules. Selecting **Edge** lets you to take advantage of [multi-stage builds](/engine/userguide/eng-image/multistage-build/). This requires
you to have a `Dockerfile.multi`, and to specify this file in
the `Dockerfile location` field of `Build Rules`. For more information
and examples, see the topic on how to [use multi-stage builds](/engine/userguide/eng-image/multistage-build/#use-multi-stage-builds).
You can learn more about **stable** and **edge** channels in the
[Install Docker overview](https://docs.docker.com/engine/installation/)
and the [Docker CE Edge](https://docs.docker.com/edge/) topics.
7. Optionally, enable [autotests](automated-testing.md#enable-automated-tests-on-a-repository).
8. Review the default **Build Rules**, and optionally click the
**plus sign** to add and configure more build rules.
_Build rules_ control what Docker Cloud builds into images from the contents _Build rules_ control what Docker Cloud builds into images from the contents
of the source code repository, and how the resulting images are tagged of the source code repository, and how the resulting images are tagged
@ -87,7 +101,10 @@ the code repository service where the image's source code is stored.
10. For each branch or tag, enable or disable the **Build Caching** toggle. 10. For each branch or tag, enable or disable the **Build Caching** toggle.
[Build caching](/engine/userguide/eng-image/dockerfile_best-practices/#/build-cache) can save time if you are building a large image frequently or have many dependencies. You might want to leave build caching disabled to make sure all of your dependencies are resolved at build time, or if you have a large layer that is quicker to build locally. [Build caching](/engine/userguide/eng-image/dockerfile_best-practices/#/build-cache) can save time if you are building a large image frequently or have
many dependencies. You might want to leave build caching disabled to
make sure all of your dependencies are resolved at build time, or if
you have a large layer that is quicker to build locally.
11. Click **Save** to save the settings, or click **Save and build** to save and 11. Click **Save** to save the settings, or click **Save and build** to save and
run an initial test. run an initial test.
@ -98,33 +115,36 @@ run an initial test.
### Set up build rules ### Set up build rules
By default when you set up autobuilds, a basic build rule is created for you.
This default rule watches for changes to the `master` branch in your source code
repository, and builds the `master` branch into a Docker image tagged with
`latest`. You
By default when you set up autobuilds, a basic build rule is created for you. This default rule watches for changes to the `master` branch in your source code repository, and builds the `master` branch into a Docker image tagged with `latest`. You In the **Build Rules** section, enter one or more sources to build.
For each source:
8. In the **Build Rules** section, enter one or more sources to build. * Select the **Source type** to build either a **tag** or a
For each source:
* Select the **Source type** to build either a **tag** or a
**branch**. This tells the build system what to look for in the source code **branch**. This tells the build system what to look for in the source code
repository. repository.
* Enter the name of the **Source** branch or tag you want to build. * Enter the name of the **Source** branch or tag you want to build.
The first time you configure automated builds, a default build rule is set up for you. This default set builds from the `Branch` in your source code called `master`, and creates a Docker image tagged with `latest`. The first time you configure automated builds, a default build rule is set up
for you. This default set builds from the `Branch` in your source code called
`master`, and creates a Docker image tagged with `latest`.
You can also use a regex to select which source branches or tags to build. You can also use a regex to select which source branches or tags to build.
To learn more, see To learn more, see
[regexes](automated-build.md#regexes-and-automated-builds). [regexes](automated-build.md#regexes-and-automated-builds).
* Enter the tag to apply to Docker images built from this source. * Enter the tag to apply to Docker images built from this source.
If you configured a regex to select the source, you can reference the If you configured a regex to select the source, you can reference the
capture groups and use its result as part of the tag. To learn more, see capture groups and use its result as part of the tag. To learn more, see
[regexes](automated-build.md#regexes-and-automated-builds). [regexes](automated-build.md#regexes-and-automated-builds).
* Specify the **Dockerfile location** as a path relative to the root of the source code repository. (If the Dockerfile is at the repository root, leave this path set to `/`.) * Specify the **Dockerfile location** as a path relative to the root of the source code repository. (If the Dockerfile is at the repository root, leave this path set to `/`.)
> **Note:** When Docker Cloud pulls a branch from a source code repository, it performs > **Note:** When Docker Cloud pulls a branch from a source code repository, it performs
a shallow clone (only the tip of the specified branch). Refer to [Advanced options for Autobuild and Autotest](advanced.md) a shallow clone (only the tip of the specified branch). Refer to [Advanced options for Autobuild and Autotest](advanced.md)