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
Boxiang Sun
gitlab-ce
Commits
e129f66d
Commit
e129f66d
authored
Jun 14, 2016
by
Kamil Trzcinski
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add gitlab-ci.yml documentation for environments
parent
3ade8260
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
27 additions
and
0 deletions
+27
-0
doc/ci/yaml/README.md
doc/ci/yaml/README.md
+27
-0
No files found.
doc/ci/yaml/README.md
View file @
e129f66d
...
...
@@ -28,6 +28,7 @@ If you want a quick introduction to GitLab CI, follow our
-
[
only and except
](
#only-and-except
)
-
[
tags
](
#tags
)
-
[
when
](
#when
)
-
[
environment
](
#environment
)
-
[
artifacts
](
#artifacts
)
-
[
artifacts:name
](
#artifacts-name
)
-
[
artifacts:when
](
#artifacts-when
)
...
...
@@ -353,6 +354,7 @@ job_name:
| cache | no | Define list of files that should be cached between subsequent runs |
| before_script | no | Override a set of commands that are executed before build |
| after_script | no | Override a set of commands that are executed after build |
| environment | no | Defines a name of environment to which deployment is done by this build |
### script
...
...
@@ -524,6 +526,31 @@ The above script will:
1.
Execute
`cleanup_build_job`
only when
`build_job`
fails
2.
Always execute
`cleanup_job`
as the last step in pipeline.
### environment
>**Note:**
Introduced in GitLab v8.9.0.
`environment`
is used to define that job does deployment to specific environment.
This allows to easily track all deployments to your environments straight from GitLab.
If
`environment`
is specified and no environment under that name does exist a new one will be created automatically.
The
`environment`
name must contain only letters, digits, '-' and '_'.
---
**Example configurations**
```
deploy to production:
stage: deploy
script: git push production HEAD:master
environment: production
```
The
`deploy to production`
job will be marked as doing deployment to
`production`
environment.
### artifacts
>**Notes:**
...
...
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