Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
李少辉-开发者
gitlab-foss
提交
e45372b7
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,发现更多精彩内容 >>
提交
e45372b7
编写于
6月 14, 2016
作者:
M
Mark Pundsack
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Grammar and typographic changes to artifacts documentation
上级
20a06798
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
19 addition
and
17 deletion
+19
-17
doc/ci/yaml/README.md
doc/ci/yaml/README.md
+19
-17
未找到文件。
doc/ci/yaml/README.md
浏览文件 @
e45372b7
...
...
@@ -479,10 +479,10 @@ failure.
`when`
can be set to one of the following values:
1.
`on_success`
- execute build only when all builds from prior stages
succeed
ed
. This is the default.
succeed. This is the default.
1.
`on_failure`
- execute build only when at least one build from prior stages
fail
ed
.
1.
`always`
- execute build
despite
the status of builds from prior stages.
fail
s
.
1.
`always`
- execute build
regardless of
the status of builds from prior stages.
For example:
...
...
@@ -559,10 +559,10 @@ The `deploy to production` job will be marked as doing deployment to `production
> - Introduced in GitLab Runner v0.7.0 for non-Windows platforms.
> - Windows support was added in GitLab Runner v.1.0.0.
> - Currently not all executors are supported.
> - Build artifacts are only collected for successful builds.
> - Build artifacts are only collected for successful builds
by default
.
`artifacts`
is used to specify list of files and directories which should be
attached to build after success. To pass artifacts between different builds,
`artifacts`
is used to specify
a
list of files and directories which should be
attached to
the
build after success. To pass artifacts between different builds,
see
[
dependencies
](
#dependencies
)
.
Below are some examples.
...
...
@@ -690,9 +690,9 @@ failure.
`artifacts:when`
can be set to one of the following values:
1.
`on_success`
- upload artifacts only when
build succeeds. This is the default
1.
`on_failure`
- upload artifacts only when
build fails
1.
`always`
- upload artifacts
despite the build status
1.
`on_success`
- upload artifacts only when
the build succeeds. This is the default.
1.
`on_failure`
- upload artifacts only when
the build fails.
1.
`always`
- upload artifacts
regardless of the build status.
---
...
...
@@ -711,16 +711,18 @@ job:
>**Note:**
Introduced in GitLab 8.9 and GitLab Runner v1.3.0.
`artifacts:expire_in`
is used to
remove uploaded artifacts after specified time.
By default artifacts are stored on GitLab forver.
`expire_in`
allows to specify after what time the artifacts should be removed.
The artifacts will expire counting from the moment when
they are uploaded and stored on GitLab.
`artifacts:expire_in`
is used to
delete uploaded artifacts after the specified
time. By default, artifacts are stored on GitLab forever.
`expire_in`
allows you
to specify how long artifacts should live before they expire, counting from the
time
they are uploaded and stored on GitLab.
After artifacts uploading you can use the
**Keep**
button on build page to keep the artifacts forever.
You can use the
**Keep**
button on the build page to override expiration and
keep artifacts forever.
Artifacts are removed every hour, but they are not accessible after expire date.
By default, artifacts are deleted hourly (via a cron job), but they are not
accessible after expiry.
The value of
`expire_in`
is a
elapsed time. The example of pars
able values:
The value of
`expire_in`
is a
n elapsed time. Examples of parse
able values:
-
'3 mins 4 sec'
-
'2 hrs 20 min'
-
'2h20min'
...
...
@@ -732,7 +734,7 @@ The value of `expire_in` is a elapsed time. The example of parsable values:
**Example configurations**
To expire artifacts
after 1 week from the moment that they are
uploaded:
To expire artifacts
1 week after being
uploaded:
```
yaml
job
:
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录