Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
李少辉-开发者
gitlab-foss
提交
bfdac632
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,发现更多精彩内容 >>
提交
bfdac632
编写于
10月 04, 2018
作者:
G
Grzegorz Bizon
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Copy-edit documentation for only/except changes feature
上级
40003585
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
25 addition
and
13 deletion
+25
-13
doc/ci/yaml/README.md
doc/ci/yaml/README.md
+25
-13
未找到文件。
doc/ci/yaml/README.md
浏览文件 @
bfdac632
...
...
@@ -388,7 +388,7 @@ except master.
>
> `variables` policy introduced in 10.7
>
> `changes` policy
introduced in 11.4
> `changes` policy
[introduced in 11.4][changes-policy-issue]
CAUTION:
**Warning:**
This an _alpha_ feature, and it it subject to change at any time without
...
...
@@ -455,7 +455,9 @@ Learn more about variables expressions on [a separate page][variables-expression
### `changes`
Using
`changes`
keyword with
`only`
or
`except`
makes it possible to define if
a job should be created, based on files modified by a git push event.
a job should be created based on files modified by a git push event.
For example:
```
yaml
docker build
:
...
...
@@ -466,20 +468,29 @@ docker build:
-
docker/scripts/*
```
In the scenario above, if you are pushing multiple commits to GitLab, to an
exising branch, GitLab is going to create and trigger
`docker build`
job,
provided that one of the commits contains changes to the
`Dockerfile`
file or
changes to any of the files inside
`docker/scripts/`
directory.
In the scenario above, if you are pushing multiple commits to GitLab to an
existing branch, GitLab creates and triggers
`docker build`
job, provided that
one of the commits contains changes to either:
-
The
`Dockerfile`
file.
-
Any of the files inside
`docker/scripts/`
directory.
CAUTION:
**Warning:**
If you are pushing a
**new**
branch or a new tag to GitLab, only/changes is
going to always evaluate to truth and GitLab will create a job. This feature is
not combined with merge requests yet, and because GitLab is creating pipelines
There are some caveats when using this feature with new branches and tags. See
the section below.
#### Using `changes` with new branches and tags
If you are pushing a
**new**
branch or a
**new**
tag to GitLab, the policy
always evaluates to truth and GitLab will create a job. This feature is not
connected with merge requests yet, and because GitLab is creating pipelines
before an user can create a merge request we don't know a target branch at
this point. Without a target branch it is not possible to know what the common
ancestor is, thus we always create a job in that case. This feature works best for
stable branches like
`master`
because in that case GitLab uses previous commit,
that is present in a branch, to compare against a newly pushed latest SHA.
this point.
Without a target branch, it is not possible to know what the common ancestor is,
thus we always create a job in that case. This feature works best for stable
branches like
`master`
because in that case GitLab uses the previous commit
that is present in a branch to compare against the latest SHA that was pushed.
## `tags`
...
...
@@ -1976,3 +1987,4 @@ CI with various languages.
[
ce-12909
]:
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/12909
[
schedules
]:
../../user/project/pipelines/schedules.md
[
variables-expressions
]:
../variables/README.md#variables-expressions
[
changes-policy-issue
]:
https://gitlab.com/gitlab-org/gitlab-ce/issues/19232
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录