Welcome to mirror list, hosted at ThFree Co, Russian Federation.

gitlab.com/gitlab-org/gitlab-foss.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorZ.J. van de Weg <zegerjan@gitlab.com>2016-09-30 16:45:27 +0300
committerZ.J. van de Weg <zegerjan@gitlab.com>2016-10-04 10:54:31 +0300
commit7d46bd6128309e6ef1f3f4785889f5a0fef4de8f (patch)
tree2f278e639671954edc943ad212e305a929485517 /doc
parent4be63f5b5bd9c0859f5ba2b91ecdbdcc57b69b98 (diff)
Save a fetchable ref per deployement
Diffstat (limited to 'doc')
-rw-r--r--doc/ci/environments.md13
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/ci/environments.md b/doc/ci/environments.md
index d85b8a34ced..081766d5ee9 100644
--- a/doc/ci/environments.md
+++ b/doc/ci/environments.md
@@ -14,6 +14,19 @@ Defining environments in a project's `.gitlab-ci.yml` lets developers track
Deployments are created when [jobs] deploy versions of code to [environments].
+### Checkout deployments locally
+
+Since 8.13, a reference in the git repository is saved for each deployment. So
+knowing what the state is of your current environments is only a `git fetch`
+away.
+
+In your git config, append the `[remote "<your-remote>"] block with an extra
+fetch line:
+
+```
+fetch = +refs/environments/*:refs/remotes/origin/environments/*
+```
+
## Defining environments
You can create and delete environments manually in the web interface, but we