Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
李少辉-开发者
gitlab-foss
提交
a5cc5f6e
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,发现更多精彩内容 >>
提交
a5cc5f6e
编写于
6月 16, 2019
作者:
E
Evan Read
提交者:
Achilleas Pipinellis
6月 16, 2019
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Edit after script context text
上级
a74c4c6e
变更
2
隐藏空白更改
内联
并排
Showing
2 changed file
with
20 addition
and
14 deletion
+20
-14
doc/ci/variables/where_variables_can_be_used.md
doc/ci/variables/where_variables_can_be_used.md
+5
-4
doc/ci/yaml/README.md
doc/ci/yaml/README.md
+15
-10
未找到文件。
doc/ci/variables/where_variables_can_be_used.md
浏览文件 @
a5cc5f6e
...
...
@@ -89,13 +89,14 @@ Supported:
-
In
`script`
, it will work in the following lines of
`script`
.
-
In
`after_script`
, it will work in following lines of
`after_script`
.
Please notice the specific case of
`after_script`
scripts, that
can:
In the case of
`after_script`
scripts, they
can:
-
Only use variables defined before the script within the same
`after_script`
section.
-
Only use variables defined before the script within the same
`after_script`
section.
-
Not use variables defined in
`before_script`
and
`script`
.
Both restrictions are caused by the fact, that
`after_script`
script is
executed in a
[
separated shell context
](
https://docs.gitlab.com/ee/ci/yaml/README.html
#before_script-and-after_script
)
.
These restrictions are because
`after_script`
scripts are
executed in a
[
separated shell context
](
../yaml/README.md
#before_script-and-after_script
)
.
## Persisted variables
...
...
doc/ci/yaml/README.md
浏览文件 @
a5cc5f6e
...
...
@@ -215,20 +215,25 @@ This can be an array or a multi-line string.
`after_script`
is used to define the command that will be run after all
jobs, including failed ones. This has to be an array or a multi-line string.
Script
specified in
`before_script`
is
:
Script
s specified in
`before_script`
are
:
-
Concatenated with script specified in the main
`script`
. Job-level
`before_script`
definition
override global-level
`before_script`
definition when concatenated with
`script`
definition.
-
Executed together with main
`script`
script as one script in a single shell context.
-
Concatenated with scripts specified in the main
`script`
. Job-level
`before_script`
definition override global-level
`before_script`
definition
when concatenated with
`script`
definition.
-
Executed together with main
`script`
script as one script in a single shell
context.
Script specified in
`after_script`
:
Script
s
specified in
`after_script`
:
-
Have a current working directory set back to the default.
-
Is executed in a shell context separated from
`before_script`
and
`script`
scripts.
-
Because of separated context, cannot see changes done by scripts defined in
`before_script`
or
`script`
scripts:
-
in shell - for example, command aliases and variables exported in
`script`
script,
-
outside of the working tree (depending on the Runner executor) - for example, software installed
by a
`before_script`
or
`script`
script.
-
Are executed in a shell context separated from
`before_script`
and
`script`
scripts.
-
Because of separated context, cannot see changes done by scripts defined
in
`before_script`
or
`script`
scripts, either:
-
In shell. For example, command aliases and variables exported in
`script`
scripts.
-
Outside of the working tree (depending on the Runner executor). For example,
software installed by a
`before_script`
or
`script`
scripts.
It's possible to overwrite the globally defined
`before_script`
and
`after_script`
if you set it per-job:
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录