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
a6f53042
Commit
a6f53042
authored
Mar 14, 2016
by
Achilleas Pipinellis
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Merge duplicate cache entry in CI docs
[ci skip]
parent
b782e7c9
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
48 additions
and
60 deletions
+48
-60
doc/ci/yaml/README.md
doc/ci/yaml/README.md
+48
-60
No files found.
doc/ci/yaml/README.md
View file @
a6f53042
...
...
@@ -134,6 +134,9 @@ thus allowing to fine tune them.
### cache
>**Note:**
Introduced in GitLab Runner v0.7.0.
`cache`
is used to specify a list of files and directories which should be
cached between builds.
...
...
@@ -142,18 +145,59 @@ cached between builds.
If
`cache`
is defined outside the scope of the jobs, it means it is set
globally and all jobs will use its definition.
To cache all git untracked files and files in
`binaries
`
:
Cache all files in
`binaries`
and
`.config
`
:
```
yaml
cache
:
rspec
:
script
:
test
cache
:
paths
:
-
binaries/
-
.config
```
Cache all Git untracked files:
```
yaml
rspec
:
script
:
test
cache
:
untracked
:
true
```
Cache all Git untracked files and files in
`binaries`
:
```
yaml
rspec
:
script
:
test
cache
:
untracked
:
true
paths
:
-
binaries/
```
Locally defined cache overwrites globally defined options. This will cache only
`binaries/`
:
```
yaml
cache
:
paths
:
-
my/files
rspec
:
script
:
test
cache
:
paths
:
-
binaries/
```
The cache is provided on best effort basis, so don't expect that cache will be
always present. For implementation details please check GitLab Runner.
#### cache:key
_**Note:** Introduced in GitLab Runner v1.0.0._
>**Note:**
Introduced in GitLab Runner v1.0.0.
The
`key`
directive allows you to define the affinity of caching
between jobs, allowing to have a single cache for all jobs,
...
...
@@ -453,62 +497,6 @@ release-job:
The artifacts will be sent to GitLab after a successful build and will
be available for download in the GitLab UI.
### cache
_**Note:** Introduced in GitLab Runner v0.7.0._
`cache`
is used to specify list of files and directories which should be cached
between builds. Below are some examples:
Cache all files in
`binaries`
and
`.config`
:
```
yaml
rspec
:
script
:
test
cache
:
paths
:
-
binaries/
-
.config
```
Cache all git untracked files:
```
yaml
rspec
:
script
:
test
cache
:
untracked
:
true
```
Cache all git untracked files and files in
`binaries`
:
```
yaml
rspec
:
script
:
test
cache
:
untracked
:
true
paths
:
-
binaries/
```
Locally defined cache overwrites globally defined options. This will cache only
`binaries/`
:
```
yaml
cache
:
paths
:
-
my/files
rspec
:
script
:
test
cache
:
paths
:
-
binaries/
```
The cache is provided on best effort basis, so don't expect that cache will be
always present. For implementation details please check GitLab Runner.
## Validate the .gitlab-ci.yml
Each instance of GitLab CI has an embedded debug tool called Lint.
...
...
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