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
0
Merge Requests
0
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
iv
gitlab-ce
Commits
20a06798
Commit
20a06798
authored
Jun 14, 2016
by
Mark Pundsack
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Tweak grammar
parent
00906b5b
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
6 additions
and
6 deletions
+6
-6
doc/ci/yaml/README.md
doc/ci/yaml/README.md
+6
-6
No files found.
doc/ci/yaml/README.md
View file @
20a06798
...
...
@@ -167,7 +167,7 @@ There are also two edge cases worth mentioning:
1.
If no
`stages`
is defined in
`.gitlab-ci.yml`
, then by default the
`build`
,
`test`
and
`deploy`
are allowed to be used as job's stage by default.
2.
If a job doesn't specify
`stage`
, the job is assigned the
`test`
stage.
2.
If a job doesn't specify
a
`stage`
, the job is assigned the
`test`
stage.
### types
...
...
@@ -178,9 +178,9 @@ Alias for [stages](#stages).
>**Note:**
Introduced in GitLab Runner v0.5.0.
GitLab CI allows you to add
to
`.gitlab-ci.yml`
variables that are set in build
environment. The variables are stored in the git repository and are meant to
store non-sensitive project configuration, for example:
GitLab CI allows you to add
variables to
`.gitlab-ci.yml`
that are set in the
build environment. The variables are stored in the git repository and are meant
to
store non-sensitive project configuration, for example:
```
yaml
variables
:
...
...
@@ -253,8 +253,8 @@ rspec:
-
binaries/
```
The cache is provided on
best effort basis, so don't expect that cache will b
e
always present. For implementation details
please check GitLab Runner.
The cache is provided on
a best-effort basis, so don't expect that the cach
e
will be always present. For implementation details,
please check GitLab Runner.
#### cache:key
...
...
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