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
66b08e05
Commit
66b08e05
authored
Dec 15, 2019
by
Marcel Amirault
Committed by
Evan Read
Dec 15, 2019
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add languages to code blocks in CI reference
parent
ecb4afd3
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
12 additions
and
11 deletions
+12
-11
doc/ci/yaml/README.md
doc/ci/yaml/README.md
+12
-11
No files found.
doc/ci/yaml/README.md
View file @
66b08e05
...
@@ -2478,12 +2478,13 @@ sequentially from `job_name 1/N` to `job_name N/N`.
...
@@ -2478,12 +2478,13 @@ sequentially from `job_name 1/N` to `job_name N/N`.
For every job,
`CI_NODE_INDEX`
and
`CI_NODE_TOTAL`
[
environment variables
](
../variables/README.md#predefined-environment-variables
)
are set.
For every job,
`CI_NODE_INDEX`
and
`CI_NODE_TOTAL`
[
environment variables
](
../variables/README.md#predefined-environment-variables
)
are set.
Marking a job to be run in parallel requires only a simple addition to your configuration file:
Marking a job to be run in parallel requires adding
`parallel`
to your configuration
file. For example:
```
diff
```
yaml
test:
test
:
script
:
rspec
script
:
rspec
+
parallel: 5
parallel
:
5
```
```
TIP:
**Tip:**
TIP:
**Tip:**
...
@@ -2531,7 +2532,7 @@ triggers being used.
...
@@ -2531,7 +2532,7 @@ triggers being used.
#### Simple `trigger` syntax
#### Simple `trigger` syntax
The
most simple way to configure a downstream trigger
to use
`trigger`
keyword
The
simplest way to configure a downstream trigger is
to use
`trigger`
keyword
with a full path to a downstream project:
with a full path to a downstream project:
```
yaml
```
yaml
...
@@ -2563,7 +2564,7 @@ staging:
...
@@ -2563,7 +2564,7 @@ staging:
It is possible to mirror the status from a triggered pipeline:
It is possible to mirror the status from a triggered pipeline:
```
```
yaml
trigger_job
:
trigger_job
:
trigger
:
trigger
:
project
:
my/project
project
:
my/project
...
@@ -2572,7 +2573,7 @@ trigger_job:
...
@@ -2572,7 +2573,7 @@ trigger_job:
It is possible to mirror the status from an upstream pipeline:
It is possible to mirror the status from an upstream pipeline:
```
```
yaml
upstream_bridge
:
upstream_bridge
:
stage
:
test
stage
:
test
needs
:
needs
:
...
@@ -3286,7 +3287,7 @@ There are three possible values: `none`, `normal`, and `recursive`:
...
@@ -3286,7 +3287,7 @@ There are three possible values: `none`, `normal`, and `recursive`:
-
`normal`
means that only the top-level submodules will be included. It is
-
`normal`
means that only the top-level submodules will be included. It is
equivalent to:
equivalent to:
```
```
shell
git submodule
sync
git submodule
sync
git submodule update
--init
git submodule update
--init
```
```
...
@@ -3296,7 +3297,7 @@ There are three possible values: `none`, `normal`, and `recursive`:
...
@@ -3296,7 +3297,7 @@ There are three possible values: `none`, `normal`, and `recursive`:
GitLab Runner with an executor not based on Docker, make sure the Git version
GitLab Runner with an executor not based on Docker, make sure the Git version
meets that requirement. It is equivalent to:
meets that requirement. It is equivalent to:
```
```
shell
git submodule
sync
--recursive
git submodule
sync
--recursive
git submodule update
--init
--recursive
git submodule update
--init
--recursive
```
```
...
@@ -3557,7 +3558,7 @@ Read more about the various [YAML features](https://learnxinyminutes.com/docs/ya
...
@@ -3557,7 +3558,7 @@ Read more about the various [YAML features](https://learnxinyminutes.com/docs/ya
If you want to temporarily 'disable' a job, rather than commenting out all the
If you want to temporarily 'disable' a job, rather than commenting out all the
lines where the job is defined:
lines where the job is defined:
```
```
yaml
#hidden_job:
#hidden_job:
# script:
# script:
# - run test
# - run test
...
...
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