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
5c6a72b4
Commit
5c6a72b4
authored
Nov 18, 2016
by
Achilleas Pipinellis
Browse files
Options
Browse Files
Download
Plain Diff
Merge branch 'docs/grammar-environments' into 'master'
Grammar fix in environments.md: s/base/basis See merge request !7552
parents
91a52bb7
039aae66
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
13 additions
and
9 deletions
+13
-9
environments.md
doc/ci/environments.md
+12
-8
index.md
doc/ci/review_apps/index.md
+1
-1
No files found.
doc/ci/environments.md
View file @
5c6a72b4
...
...
@@ -235,7 +235,7 @@ will help us achieve that.
As the name suggests, it is possible to create environments on the fly by just
declaring their names dynamically in
`.gitlab-ci.yml`
. Dynamic environments is
the bas
e
of
[
Review apps
](
review_apps.md
)
.
the bas
is
of
[
Review apps
](
review_apps.md
)
.
GitLab Runner exposes various
[
environment variables
][
variables
]
when a job runs,
and as such, you can use them as environment names. Let's add another job in
...
...
@@ -344,6 +344,10 @@ review_app:
It is assumed that the user has already setup NGINX and GitLab Runner in the
server this job will run on.
>**Note:**
Be sure to check out the
[
limitations
](
#limitations
)
section for some edge
cases regarding naming of you branches and Review Apps.
---
The development workflow would now be:
...
...
@@ -489,13 +493,13 @@ fetch = +refs/environments/*:refs/remotes/origin/environments/*
## Limitations
-
You are limited to use only the
[
CI predefined variables
][
variables
]
in
the
`environment: name`
. If you try to re-use variables defined inside
`script`
as part of the environment name, it will not work.
-
If the branch name contains special characters and you use the
`$CI_BUILD_REF_NAME`
variable to dynamically create environments, there might
be complications during deployment. Follow the
[
issue 22849
][
ce-22849
]
for
more information
.
1.
If the branch name contains special characters (
`/`
), and you use
the
`$CI_BUILD_REF_NAME`
variable to dynamically create environments, there might
be complications during your Review Apps deployment. Follow the
[
issue 22849
][
ce-22849
]
for more information.
1.
You are limited to use only the
[
CI predefined variables
][
variables
]
in the
`environment: name`
. If you try to re-use variables defined inside
`script`
as part of the environment name, it will not work
.
## Further reading
...
...
doc/ci/review_apps/index.md
View file @
5c6a72b4
...
...
@@ -6,7 +6,7 @@
-
Inspired by
[
Heroku's Review Apps
][
heroku-apps
]
which itself was inspired by
[
Fourchette
]
.
The bas
e
of Review Apps is the
[
dynamic environments
]
which allow you to create
The bas
is
of Review Apps is the
[
dynamic environments
]
which allow you to create
a new environment (dynamically) for each one of your branches.
A Review App can then be visible as a link when you visit the
[
merge request
]
...
...
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