@@ -264,6 +264,12 @@ GitLab CI is capable not only testing or building your projects (Continuous Inte
If the deployment to production is defined strategically and triggered manually we are talking about Continuous Delivery. Continuous Deployment is a software development practice in which every code change goes through the entire pipeline and is put into production automatically ([CI vs. CD vs. CD](https://about.gitlab.com/2016/08/05/continuous-integration-delivery-and-deployment-with-gitlab/)).
Whatever CD strategy we use (manuall or automatic) it contains the three steps of
1. Review
2. Staging
3. Production
All of these three steps use the method of [GitLab Environments](https://gitlab.version.fz-juelich.de/help/ci/environments).
## GitLab Environments
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.
...
...
@@ -273,3 +279,10 @@ GitLab keeps track of your deployments and provides a full history of your deplo
[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.
