Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
192eaa41
Commit
192eaa41
authored
Feb 12, 2019
by
Evan Read
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix spelling and remove quoting for bridge jobs
parent
23e9b9b1
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
6 additions
and
6 deletions
+6
-6
doc/ci/multi_project_pipelines.md
doc/ci/multi_project_pipelines.md
+5
-5
doc/ci/yaml/README.md
doc/ci/yaml/README.md
+1
-1
No files found.
doc/ci/multi_project_pipelines.md
View file @
192eaa41
...
...
@@ -68,7 +68,7 @@ staging:
```
In the example above, as soon as
`rspec`
job succeeds in the
`test`
stage,
the
`staging`
"bridge"
job is going to be started. The initial status of this
the
`staging`
bridge
job is going to be started. The initial status of this
job will be
`pending`
. GitLab will create a downstream pipeline in the
`my/deployment`
project and, as soon as the pipeline gets created, the
`staging`
job will succeed.
`my/deployment`
is a full path to that project.
...
...
@@ -85,8 +85,8 @@ GitLab does not support status attribution yet, however adding first-class
[
status attribution
](
https://gitlab.com/gitlab-org/gitlab-ce/issues/39640
)
.
NOTE:
**Note:**
"Bridge"
jobs do not support every configuration entry that a user can use
in the case of regular jobs.
"Bridge"
jobs will not to be picked by a Runner,
Bridge
jobs do not support every configuration entry that a user can use
in the case of regular jobs.
Bridge
jobs will not to be picked by a Runner,
thus there is no point in adding support for
`script`
, for example. If a user
tries to use unsupported configuration syntax, YAML validation will fail upon
pipeline creation.
...
...
@@ -136,13 +136,13 @@ pipeline. It will be available as an environment variable when GitLab Runner pic
### Limitations
Because
"bridge"
jobs are a little different to regular jobs, it is not
Because
bridge
jobs are a little different to regular jobs, it is not
possible to use exactly the same configuration syntax here, as one would
normally do when defining a regular job that will be picked by a runner.
Some features are not implemented yet. For example, support for environments.
[
Configuration keywords
](
yaml/README.md
)
available for
"bridge"
jobs are:
[
Configuration keywords
](
yaml/README.md
)
available for
bridge
jobs are:
-
`trigger`
(to define a downstream pipeline trigger)
-
`stage`
...
...
doc/ci/yaml/README.md
View file @
192eaa41
...
...
@@ -1539,7 +1539,7 @@ test:
from
`trigger`
definition is started by GitLab, a downstream pipeline gets
created.
Lear
m
more about
[
multi-project pipelines
](
../multi_project_pipelines.md#creating-cross-project-pipelines-from-gitlab-ci-yml
)
.
Lear
n
more about
[
multi-project pipelines
](
../multi_project_pipelines.md#creating-cross-project-pipelines-from-gitlab-ci-yml
)
.
### Simple `trigger` syntax
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment