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
f2318dfc
Commit
f2318dfc
authored
Nov 21, 2015
by
Kamil Trzcinski
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix CI yaml syntax documentation [ci skip]
parent
78be7055
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
41 additions
and
49 deletions
+41
-49
doc/ci/yaml/README.md
doc/ci/yaml/README.md
+41
-49
No files found.
doc/ci/yaml/README.md
View file @
f2318dfc
...
@@ -278,26 +278,23 @@ The above script will:
...
@@ -278,26 +278,23 @@ The above script will:
`artifacts`
is used to specify list of files and directories which should be attached to build after success.
`artifacts`
is used to specify list of files and directories which should be attached to build after success.
1.
Send all files in
`binaries`
and
`.config`
:
1.
Send all files in
`binaries`
and
`.config`
:
```
artifacts:
artifacts:
paths:
paths:
- binaries/
- binaries/
- .config
- .config
```
2.
Send all git untracked files:
2.
Send all git untracked files:
```
artifacts:
artifacts:
untracked: true
untracked: true
```
3.
Send all git untracked files and files in
`binaries`
:
3.
Send all git untracked files and files in
`binaries`
:
```
artifacts:
artifacts:
untracked: true
untracked: true
paths:
paths:
- binaries/
- binaries/
```
The artifacts will be send after the build success to GitLab and will be accessible in GitLab interface to download.
The artifacts will be send after the build success to GitLab and will be accessible in GitLab interface to download.
...
@@ -307,46 +304,41 @@ This feature requires GitLab Runner v0.7.0 or higher.
...
@@ -307,46 +304,41 @@ This feature requires GitLab Runner v0.7.0 or higher.
`cache`
is used to specify list of files and directories which should be cached between builds.
`cache`
is used to specify list of files and directories which should be cached between builds.
1.
Cache all files in
`binaries`
and
`.config`
:
1.
Cache all files in
`binaries`
and
`.config`
:
```
rspec:
rspec:
script: test
script: test
cache:
cache:
paths:
paths:
- binaries/
- binaries/
- .config
- .config
```
2.
Cache all git untracked files:
2.
Cache all git untracked files:
```
rspec:
script: test
cache:
untracked: true
```
rspec:
script: test
cache:
untracked: true
3.
Cache all git untracked files and files in
`binaries`
:
3.
Cache all git untracked files and files in
`binaries`
:
```
rspec:
script: test
cache:
untracked: true
paths:
- binaries/
```
4.
Locally defined cache overwrites globally defined options. This will cache only
`binaries/`
:
rspec:
script: test
cache:
untracked: true
paths:
- binaries/
```
4.
Locally defined cache overwrites globally defined options. This will cache only
`binaries/`
:
cache:
paths:
- my/files
rspec:
cache:
script: test
paths:
cache:
- my/files
paths:
- binaries/
rspec:
```
script: test
cache:
paths:
- binaries/
The cache is provided on best effort basis, so don't expect that cache will be present.
The cache is provided on best effort basis, so don't expect that cache will be present.
For implementation details please check GitLab Runner.
For implementation details please check GitLab Runner.
...
...
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