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
fbe5e7b3
Commit
fbe5e7b3
authored
Oct 06, 2020
by
Suzanne Selhorn
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Docs: Fixed Vale long sentence errors
Related to:
https://gitlab.com/gitlab-org/gitlab/-/issues/234029
parent
b33510a2
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
9 additions
and
10 deletions
+9
-10
doc/ci/yaml/README.md
doc/ci/yaml/README.md
+9
-10
No files found.
doc/ci/yaml/README.md
View file @
fbe5e7b3
...
...
@@ -492,8 +492,8 @@ include:
file
:
'
/templates/.gitlab-ci-template.yml'
```
All
[
nested includes
](
#nested-includes
)
are executed in the scope of the target project
,
so it's possible to use local (relative to target project), project, remote
All
[
nested includes
](
#nested-includes
)
are executed in the scope of the target project
.
This means you can use local (relative to target project), project, remote,
or template includes.
#### `include:remote`
...
...
@@ -632,10 +632,9 @@ job:
-
bundle exec rspec
```
NOTE:
**Note:**
Sometimes,
`script`
commands must be wrapped in single or double quotes.
For example, commands that contain a colon (
`:`
) must be wrapped in quotes
so
that the YAML parser knows to interpret the whole thing
as a string rather than
For example, commands that contain a colon (
`:`
) must be wrapped in quotes
.
The YAML parser needs to interpret the text
as a string rather than
a "key: value" pair. Be careful when using special characters:
`:`
,
`{`
,
`}`
,
`[`
,
`]`
,
`,`
,
`&`
,
`*`
,
`#`
,
`?`
,
`|`
,
`-`
,
`<`
,
`>`
,
`=`
,
`!`
,
`%`
,
`@`
,
`` ` ``
.
...
...
@@ -741,11 +740,11 @@ using [`|` (literal) and `>` (folded) YAML multi-line block scalar indicators](h
CAUTION:
**Warning:**
If multiple commands are combined into one command string, only the last command's
failure or success is reported
,
[
incorrectly ignoring failures from earlier commands
due to a bug
](
https://gitlab.com/gitlab-org/gitlab-runner/-/issues/25394
)
.
If the success of the job depends on the success or failure of these command
s,
you can run the commands as separate
`script:`
items, or add
`exit 1`
commands
as appropriate to the command string where needed
.
failure or success is reported
.
[
Failures from earlier commands are ignored
due to a bug
](
https://gitlab.com/gitlab-org/gitlab-runner/-/issues/25394
)
.
To work around thi
s,
run each command as a separate
`script:`
item, or add an
`exit 1`
command
to each command string
.
You can use the
`|`
(literal) YAML multiline block scalar indicator to write
commands over multiple lines in the
`script`
section of a job description.
...
...
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