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
Jérome Perrin
gitlab-ce
Commits
ff97de61
Commit
ff97de61
authored
Nov 17, 2016
by
Achilleas Pipinellis
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Move name rules under environment:name in yaml readme
parent
3a6e38db
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
17 additions
and
16 deletions
+17
-16
doc/ci/yaml/README.md
doc/ci/yaml/README.md
+17
-16
No files found.
doc/ci/yaml/README.md
View file @
ff97de61
...
@@ -552,28 +552,14 @@ An example usage of manual actions is deployment to production.
...
@@ -552,28 +552,14 @@ An example usage of manual actions is deployment to production.
If
`environment`
is specified and no environment under that name exists, a new
If
`environment`
is specified and no environment under that name exists, a new
one will be created automatically.
one will be created automatically.
The
`environment`
name can contain:
-
letters
-
digits
-
spaces
-
`-`
-
`_`
-
`/`
-
`$`
-
`{`
-
`}`
Common names are
`qa`
,
`staging`
, and
`production`
, but you can use whatever
name works with your workflow.
In its simplest form, the
`environment`
keyword can be defined like:
In its simplest form, the
`environment`
keyword can be defined like:
```
```
deploy to production:
deploy to production:
stage: deploy
stage: deploy
script: git push production HEAD:master
script: git push production HEAD:master
environment: production
environment:
name: production
```
```
In the above example, the
`deploy to production`
job will be marked as doing a
In the above example, the
`deploy to production`
job will be marked as doing a
...
@@ -588,6 +574,21 @@ Before GitLab 8.11, the name of an environment could be defined as a string like
...
@@ -588,6 +574,21 @@ Before GitLab 8.11, the name of an environment could be defined as a string like
`environment: production`
. The recommended way now is to define it under the
`environment: production`
. The recommended way now is to define it under the
`name`
keyword.
`name`
keyword.
The
`environment`
name can contain:
-
letters
-
digits
-
spaces
-
`-`
-
`_`
-
`/`
-
`$`
-
`{`
-
`}`
Common names are
`qa`
,
`staging`
, and
`production`
, but you can use whatever
name works with your workflow.
Instead of defining the name of the environment right after the
`environment`
Instead of defining the name of the environment right after the
`environment`
keyword, it is also possible to define it as a separate value. For that, use
keyword, it is also possible to define it as a separate value. For that, use
the
`name`
keyword under
`environment`
:
the
`name`
keyword under
`environment`
:
...
...
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