Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
李少辉-开发者
gitlab-foss
提交
84827c13
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,发现更多精彩内容 >>
提交
84827c13
编写于
9月 01, 2017
作者:
G
Grzegorz Bizon
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Add some basic docs about kubernetes: active feature
上级
6f658392
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
31 addition
and
4 deletion
+31
-4
doc/ci/yaml/README.md
doc/ci/yaml/README.md
+31
-4
未找到文件。
doc/ci/yaml/README.md
浏览文件 @
84827c13
...
...
@@ -427,16 +427,16 @@ a "key: value" pair. Be careful when using special characters:
are executed in
`parallel`
. For more info about the use of
`stage`
please check
[
stages
](
#stages
)
.
### only and except
### only and except
(simplified)
`only`
and
`except`
are two parameters that set a
refs
policy to limit when
jobs are
built
:
`only`
and
`except`
are two parameters that set a
job
policy to limit when
jobs are
created
:
1.
`only`
defines the names of branches and tags for which the job will run.
2.
`except`
defines the names of branches and tags for which the job will
**not**
run.
There are a few rules that apply to the usage of
refs
policy:
There are a few rules that apply to the usage of
job
policy:
*
`only`
and
`except`
are inclusive. If both
`only`
and
`except`
are defined
in a job specification, the ref is filtered by
`only`
and
`except`
.
...
...
@@ -497,6 +497,33 @@ job:
The above example will run
`job`
for all branches on
`gitlab-org/gitlab-ce`
,
except master.
### only and except (complex)
> Introduced in GitLab 10.0
Since GitLab 10.0 it is possible to define a complex only/except job policy
configuration.
GitLab now supports both, simple and complex strategies, so it is possible to
use array and hash scheme configuration.
Two keys are now available:
`refs`
and
`kubernetes`
. Refs strategy equals to
simplified only/except configuration, whereas kubernetes strategy accepts only
`active`
keyword.
See the example below. Job is going to be created only when pipeline has been
scheduled or runs for a
`master`
branch, and only if kubernetes service is
active in the project.
```
yaml
job
:
only
:
refs
:
-
master
-
schedules
kubernetes
:
active
```
### Job variables
It is possible to define job variables using a
`variables`
keyword on a job
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录