Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
李少辉-开发者
gitlab-foss
提交
de7466af
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 搜索 >>
未验证
提交
de7466af
编写于
12月 18, 2018
作者:
A
Achilleas Pipinellis
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Refactor the pipelines for merge requests docs
上级
257a61e8
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
15 addition
and
16 deletion
+15
-16
doc/ci/merge_request_pipelines/index.md
doc/ci/merge_request_pipelines/index.md
+15
-16
未找到文件。
doc/ci/merge_request_pipelines/index.md
浏览文件 @
de7466af
# Pipelines for merge requests
> [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/issues/15310) in GitLab 11.6
> [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/issues/15310) in GitLab 11.6
.
Usually, when
a developer creates
a new merge request, a pipeline runs on the
Usually, when
you create
a new merge request, a pipeline runs on the
new change and checks if it's qualified to be merged into a target branch. This
pipeline should contain only necessary jobs for checking the new changes.
For example, unit tests, lint checks, and Review Apps are often used in this cycle.
For example, unit tests, lint checks, and
[
Review Apps
](
../review_apps/index.md
)
are often used in this cycle.
With pipelines for merge requests, you can design a specific pipeline structure
for merge requests. All you need to do is just adding
`only: [merge_requests]`
to
...
...
@@ -14,10 +15,10 @@ Every time, when developers create or update merge requests, a pipeline runs on
their new commits at every push to GitLab.
NOTE:
**Note**
:
If you use both this feature and
the
[
Merge When Pipeline Succeeds
](
../../user/project/merge_requests/merge_when_pipeline_succeeds.md
)
feature, pipelines for merge requests take precen
dence over the other regular pipelines.
If you use both this feature and
[
Merge When Pipeline Succeeds
](
../../user/project/merge_requests/merge_when_pipeline_succeeds.md
)
,
pipelines for merge requests take prece
dence over the other regular pipelines.
For example, consider
a GitLab CI/CD configuration in .gitlab-ci.yml as follows
:
For example, consider
the following
[
`.gitlab-ci.yml`
](
../yaml/README.md
)
:
```
yaml
build
:
...
...
@@ -39,20 +40,18 @@ deploy:
script
:
./deploy
```
After
a developer updated code in a merge request with whatever methods (e.g.
`git push`
),
GitLab detects that the code is updated and create
a new pipeline for the merge request.
After
the merge request is updated with new commits, GitLab detects that changes
have occurred and creates
a new pipeline for the merge request.
The pipeline fetches the latest code from the source branch and run tests against it.
In th
is
example, the pipeline contains only
`build`
and
`test`
jobs.
Since
`deploy`
job does no
t have the
`only: [merge_requests]`
rule,
In th
e above
example, the pipeline contains only
`build`
and
`test`
jobs.
Since
the
`deploy`
job doesn'
t have the
`only: [merge_requests]`
rule,
deployment jobs will not happen in the merge request.
Consider this pipeline list viewed from the
**Pipelines**
tab in a merge request:
Pipelines tagged as
**merge request**
indicate that they were triggered
when a merge request was created or updated.
![
Merge request page
](
img/merge_request.png
)
Note that pipelines tagged as
**merge request**
indicate that they were triggered
when a merge request was created or updated.
The same tag is shown on the pipeline's details:
![
Pipeline's details
](
img/pipeline_detail.png
)
...
...
@@ -66,7 +65,7 @@ flow, external contributors follow the following steps:
1.
Create a merge request from the forked project that targets the
`master`
branch
in the parent project.
1.
A pipeline runs on the merge request.
1.
A main
at
iner from the parent project checks the pipeline result, and merge
1.
A main
ta
iner from the parent project checks the pipeline result, and merge
into a target branch if the latest pipeline has passed.
Currently, those pipelines are created in a
**forked**
project, not in the
...
...
@@ -77,7 +76,7 @@ by tweaking their GitLab Runner in the forked project.
There are multiple reasons about why GitLab doesn't allow those pipelines to be
created in the parent project, but one of the biggest reasons is security concern.
External users could steal secret variables from the parent project by modifying
.gitlab-ci.yml
, which could be some sort of credentials. This should not happen.
`.gitlab-ci.yml`
, which could be some sort of credentials. This should not happen.
We're discussing a secure solution of running pipelines for merge requests
that submitted from forked projects,
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录