@@ -274,10 +274,13 @@ All of these three steps use the method of [GitLab Environments](https://gitlab.
With [GitLab Environments](https://gitlab.version.fz-juelich.de/help/ci/environments), you can control the Continuous Delivery/Deployment of your software all within GitLab.
All you need to do is define Environments in your project's [.gitlab-ci.yml](https://docs.gitlab.com/ee/ci/yaml/README.html).
GitLab keeps track of your deployments and provides a full history of your deployments per every environment, so you always know what is currently being deployed on your servers.
[GitLab Environments](https://gitlab.version.fz-juelich.de/help/ci/environments) are like tags for your CI jobs, describing where code gets deployed.
Deployments are created when CI Jobs deploy versions of code to environments, so every environment can have one or more deployments.
GitLab keeps track of your deployments and provides a full history of your deployments per every environment, so you always know what is currently being deployed on your servers. Deployments are created when CI Jobs deploy versions of code to environments, so every environment can have one or more deployments.
But keep in mind, GitLab Environments are for **controling** the Continuous Delivery/Deployment, not actually doing it!
| **Note:**[GitLab Environments](https://gitlab.version.fz-juelich.de/help/ci/environments) are only like tags for your CI jobs, recording that a CI Job was executed. They do **NOT** trigger anything - your CI Script has to do all the hard work!
