Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
李少辉-开发者
gitlab-foss
提交
15ff8dcb
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,发现更多精彩内容 >>
提交
15ff8dcb
编写于
9月 28, 2016
作者:
N
Nick Thomas
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Document GIT_STRATEGY=none
[ci skip]
上级
bac56e3b
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
26 addition
and
8 deletion
+26
-8
doc/ci/yaml/README.md
doc/ci/yaml/README.md
+26
-8
未找到文件。
doc/ci/yaml/README.md
浏览文件 @
15ff8dcb
...
...
@@ -858,27 +858,45 @@ job:
## Git Strategy
> Introduced in GitLab 8.9 as an experimental feature. May change in future
releases or be removed completely.
> Introduced in GitLab 8.9 as an experimental feature. May change or be removed
completely in future releases.
`GIT_STRATEGY=none`
requires GitLab Runner
v1.7+.
You can set the
`GIT_STRATEGY`
used for getting recent application code, either
in the global
[
`variables`
](
#variables
)
section or the
[
`variables`
](
#job-variables
)
section for individual jobs. If left unspecified, the default from project
settings will be used.
You can set the
`GIT_STRATEGY`
used for getting recent application code.
`clone`
is slower, but makes sure you have a clean directory before every build.
`fetch`
is faster.
`GIT_STRATEGY`
can be specified in the global
`variables`
section or
in the
`variables`
section for individual jobs. If it's not specified, then the
default from project settings will be used.
There are three possible values:
`clone`
,
`fetch`
, and
`none`
.
`clone`
is the slowest option. It clones the repository from scratch for every
job, ensuring that the project workspace is always pristine.
```
variables:
GIT_STRATEGY: clone
```
or
`fetch`
is faster as it re-uses the project workspace (falling back to
`clone`
if it doesn't exist).
`git clean`
is used to undo any changes made by the last
job, and
`git fetch`
is used to retrieve commits made since the last job ran.
```
variables:
GIT_STRATEGY: fetch
```
`none`
also re-uses the project workspace, but skips all Git operations
(including GitLab Runner's pre-clone script, if present). It is mostly useful
for jobs that operate exclusively on artifacts (e.g.,
`deploy`
). Git repository
data may be present, but it is certain to be out of date, so you should only
rely on files brought into the project workspace from cache or artifacts.
```
variables:
GIT_STRATEGY: none
```
## Shallow cloning
> Introduced in GitLab 8.9 as an experimental feature. May change in future
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录