Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
李少辉-开发者
gitlab-foss
提交
c64721f1
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 搜索 >>
提交
c64721f1
编写于
10月 05, 2016
作者:
N
Nick Thomas
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Document the new CI_DEBUG_TRACE variable
[ci skip]
上级
4dc61dc7
变更
2
显示空白变更内容
内联
并排
Showing
2 changed file
with
36 addition
and
0 deletion
+36
-0
doc/ci/pipelines.md
doc/ci/pipelines.md
+2
-0
doc/ci/variables/README.md
doc/ci/variables/README.md
+34
-0
未找到文件。
doc/ci/pipelines.md
浏览文件 @
c64721f1
...
...
@@ -31,6 +31,8 @@ project.
## Seeing build status
Clicking on a pipeline will show the builds that were run for that pipeline.
Clicking on an individual build will show you its build trace, and allow you to
cancel the build, retry it, or erase the build trace.
## Badges
...
...
doc/ci/variables/README.md
浏览文件 @
c64721f1
...
...
@@ -48,6 +48,7 @@ The `API_TOKEN` will take the Secure Variable value: `SECURE`.
|
**CI_RUNNER_ID**
| 8.10 | 0.5 | The unique id of runner being used |
|
**CI_RUNNER_DESCRIPTION**
| 8.10 | 0.5 | The description of the runner as saved in GitLab |
|
**CI_RUNNER_TAGS**
| 8.10 | 0.5 | The defined runner tags |
|
**CI_DEBUG_TRACE**
| all | 1.7 | Whether
[
debug tracing
](
#debug-tracing
)
is enabled |
|
**GITLAB_USER_ID**
| 8.12 | all | The id of the user who started the build |
|
**GITLAB_USER_EMAIL**
| 8.12 | all | The email of the user who started the build |
...
...
@@ -105,6 +106,39 @@ Variables can be defined at a global level, but also at a job level.
More information about Docker integration can be found in
[
Using Docker Images
](
../docker/using_docker_images.md
)
.
#### Debug tracing
> **WARNING:** Enabling debug tracing can have severe security implications. The
output
**will**
contain the content of all your secure variables and any other
secrets! The output
**will**
be uploaded to the GitLab server and made visible
in build traces!
By default, GitLab Runner hides most of the details of what it is doing when
processing a job. This behaviour keeps build traces short, and prevents secrets
from being leaked into the trace unless your script writes them to the screen.
If a job isn't working as expected, this can make the problem difficult to
investigate; in these cases, you can enable debug tracing in
`.gitlab-ci.yml`
.
Available on GitLab Runner v1.7+, this feature enables the shell's execution
trace, resulting in a verbose build trace listing all commands that were run,
variables that were set, etc.
Before enabling this, you should ensure builds are visible to
[
team members only
](
../../../user/permissions.md#project-features
)
. You should
also
[
erase
](
../pipelines.md#seeing-build-traces
)
all generated build traces
before making them visible again.
To enable debug traces, set the
`CI_DEBUG_TRACE`
variable to
`true`
:
```
yaml
job1
:
variables
:
CI_DEBUG_TRACE
:
"
true"
```
The
[
example project
](
https://gitlab.com/gitlab-examples/ci-debug-trace
)
demonstrates a working configuration, including build trace examples.
### User-defined variables (Secure Variables)
**This feature requires GitLab Runner 0.4.0 or higher**
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录