BigW Consortium Gitlab
Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
G
gitlab-ce
Project
Overview
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
Registry
Registry
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Commits
Issue Boards
Open sidebar
Forest Godfrey
gitlab-ce
Commits
19d1455a
Commit
19d1455a
authored
Mar 12, 2016
by
Achilleas Pipinellis
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Change notes to new styleguide using blockquotes
parent
8c543e60
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
16 additions
and
11 deletions
+16
-11
README.md
doc/ci/yaml/README.md
+16
-11
No files found.
doc/ci/yaml/README.md
View file @
19d1455a
...
...
@@ -116,7 +116,8 @@ Alias for [stages](#stages).
### variables
_**Note:** Introduced in GitLab Runner v0.5.0._
>**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
...
...
@@ -153,7 +154,8 @@ cache:
#### 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,
...
...
@@ -394,12 +396,12 @@ The above script will:
### artifacts
_**Note:** Introduced in GitLab Runner v0.7.0 for non-Windows platforms._
_
**Note:**
Limited Windows support was added in GitLab Runner v.1.0.0.
Currently not all executors are supported._
_**Note:** Build artifacts are only collected for successful builds._
>**Notes:**
>
> - Introduced in GitLab Runner v0.7.0 for non-Windows platforms.
> - Limited Windows support was added in GitLab Runner v.1.0.0.
> - Currently not all executors are supported.
> - Build artifacts are only collected for successful builds.
`artifacts`
is used to specify list of files and directories which should be
attached to build after success. Below are some examples.
...
...
@@ -456,7 +458,8 @@ be available for download in the GitLab UI.
#### artifacts:name
_**Note:** Introduced in GitLab 8.6 and GitLab Runner v1.1.0._
>**Note:**
Introduced in GitLab 8.6 and GitLab Runner v1.1.0.
The
`name`
directive allows you to define the name of created artifacts archive.
...
...
@@ -517,7 +520,8 @@ job:
### dependencies
_**Note:** Introduced in GitLab 8.6 and GitLab Runner v1.1.1._
>**Note:**
Introduced in GitLab 8.6 and GitLab Runner v1.1.1.
This feature should be used with
`artifacts`
and allows to define artifacts passing between different builds.
...
...
@@ -571,7 +575,8 @@ However, only the `build:osx` and `build:linux` exports artifacts so only these
### cache
_**Note:** Introduced in GitLab Runner v0.7.0._
>**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:
...
...
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