Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
李少辉-开发者
gitlab-foss
提交
4495abcd
G
gitlab-foss
项目概览
李少辉-开发者
/
gitlab-foss
通知
15
Star
0
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
G
gitlab-foss
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
提交
4495abcd
编写于
7月 25, 2018
作者:
T
Tobias Hernstig
提交者:
Achilleas Pipinellis
7月 25, 2018
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Update doc/ci/docker/using_docker_build.md
上级
6cb30f83
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
6 addition
and
4 deletion
+6
-4
doc/ci/docker/using_docker_build.md
doc/ci/docker/using_docker_build.md
+6
-4
未找到文件。
doc/ci/docker/using_docker_build.md
浏览文件 @
4495abcd
...
@@ -427,7 +427,7 @@ services:
...
@@ -427,7 +427,7 @@ services:
variables
:
variables
:
DOCKER_HOST
:
tcp://docker:2375
DOCKER_HOST
:
tcp://docker:2375
DOCKER_DRIVER
:
overlay2
DOCKER_DRIVER
:
overlay2
IMAGE_TAG
:
$CI_REGISTRY_IMAGE:$CI_COMMIT_REF_
NAME
IMAGE_TAG
:
$CI_REGISTRY_IMAGE:$CI_COMMIT_REF_
SLUG
before_script
:
before_script
:
-
docker login -u gitlab-ci-token -p $CI_JOB_TOKEN $CI_REGISTRY
-
docker login -u gitlab-ci-token -p $CI_JOB_TOKEN $CI_REGISTRY
...
@@ -440,8 +440,10 @@ build:
...
@@ -440,8 +440,10 @@ build:
```
```
Here,
`$CI_REGISTRY_IMAGE`
would be resolved to the address of the registry tied
Here,
`$CI_REGISTRY_IMAGE`
would be resolved to the address of the registry tied
to this project, and
`$CI_COMMIT_REF_NAME`
would be resolved to the branch or
to this project. Since
`$CI_COMMIT_REF_NAME`
resolves to the branch or tag name,
tag name for this particular job. We also declare our own variable,
`$IMAGE_TAG`
,
and your branch-name can contain forward slashes (e.g., feature/my-feature), it is
safer to use
`$CI_COMMIT_REF_SLUG`
as the image tag. This is due to that image tags
cannot contain forward slashes. We also declare our own variable,
`$IMAGE_TAG`
,
combining the two to save us some typing in the
`script`
section.
combining the two to save us some typing in the
`script`
section.
Here's a more elaborate example that splits up the tasks into 4 pipeline stages,
Here's a more elaborate example that splits up the tasks into 4 pipeline stages,
...
@@ -464,7 +466,7 @@ stages:
...
@@ -464,7 +466,7 @@ stages:
variables
:
variables
:
DOCKER_HOST
:
tcp://docker:2375
DOCKER_HOST
:
tcp://docker:2375
DOCKER_DRIVER
:
overlay2
DOCKER_DRIVER
:
overlay2
CONTAINER_TEST_IMAGE
:
registry.example.com/my-group/my-project/my-image:$CI_COMMIT_REF_
NAME
CONTAINER_TEST_IMAGE
:
registry.example.com/my-group/my-project/my-image:$CI_COMMIT_REF_
SLUG
CONTAINER_RELEASE_IMAGE
:
registry.example.com/my-group/my-project/my-image:latest
CONTAINER_RELEASE_IMAGE
:
registry.example.com/my-group/my-project/my-image:latest
before_script
:
before_script
:
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录