Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
李少辉-开发者
gitlab-foss
提交
5de95d4e
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,体验更适合开发者的 AI 搜索 >>
提交
5de95d4e
编写于
6月 17, 2016
作者:
M
Mark Pundsack
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Update GIT_DEPTH wording
上级
4e0f9eeb
变更
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
浏览文件 @
5de95d4e
...
...
@@ -819,11 +819,14 @@ job:
## Git Strategy
>**Note:**
Introduced in GitLab 8.9 as an experimental feature
Introduced in GitLab 8.9 as an experimental feature. May change in future
releases or be removed completely.
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. If specified, it will override the project settings in the web UI.
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.
```
variables:
...
...
@@ -840,17 +843,32 @@ variables:
## Shallow cloning
>**Note:**
Introduced in GitLab 8.9 as an experimental feature
Introduced in GitLab 8.9 as an experimental feature. May change in future
releases or be removed completely.
You can specify the depth of fetching and cloning using
`GIT_DEPTH`
. This allows
shallow cloning of the repository. The value is passed to
`git fetch`
and
`git
clone`
. If set while cloning, it will imply
`--shallow-modules`
, which means
submodules will be cloned with a depth of 1 regardless of the value of
`GIT_DEPTH`
.
shallow cloning of the repository which can significantly speed up cloning for
repositories with a large number of commits or old, large binaries. The value is
passed to
`git fetch`
and
`git clone`
.
>**Note:**
If you use a depth of 1 and have a queue of builds or retry
builds, jobs may fail.
Since Git fetching and cloning is based on a ref, such as a branch name, runners
can't clone a specific commit SHA. If there are multiple builds in the queue, or
you are retrying an old build, the commit to be tested needs to be within the
git history that is cloned. Setting too small a value for
`GIT_DEPTH`
can make
it impossible to run these old commits. You will see
`unresolved reference`
in
build logs. You should then reconsider changing
`GIT_DEPTH`
to a higher value.
Builds that rely on
`git describe`
may not work correctly when
`GIT_DEPTH`
is
set since only part of the git history is present.
To fetch or clone only the last 3 commits:
```
variables:
GIT_DEPTH: "
1
"
GIT_DEPTH: "
3
"
```
## Hidden jobs
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录