@@ -257,19 +257,19 @@ In this project the [CI Job "deploy-doc"](https://gitlab.version.fz-juelich.de/v
During the development of software, there can be many stages until it's ready for public consumption.
You sure want to first test your code and then deploy it in a testing or staging environment before you release it to the public. That way you can prevent bugs not only in your software, but in the deployment process as well.
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/)).
| **Note:** If the deployment to production is defined strategically and triggered manually we are talking about **Continuous Delivery**.
GitLab CI is capable not only testing or building your projects (Continuous Integration (CI)), but also deploying them with one of the strategies of Continuous Delivery or Continuous Deployment in your infrastructure. This enables a way to track your deployments. In other words, you can always know what is currently being deployed or has been deployed on your servers and you can even roll it back, if major bugs are found.
| **Note:** If code change goes through the entire pipeline and are put into production automatically we are talking about **Continuous Deployment**.
| **Note:** If the deployment to production is defined strategically and triggered manually we are talking about **Continuous Delivery**. If code change goes through the entire pipeline and are put into production automatically we are talking about **Continuous Deployment**.|
GitLab CI is capable of not only testing or building your projects (Continuous Integration (CI)), but also deploying them with the strategy of Continuous Delivery or Continuous Deployment in your infrastructure. This enables a way to track your deployments. In other words, you can always know what is currently being deployed or has been deployed on your servers and you can even roll it back, if major bugs are found.
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/)).
## GitLab Environments
With [GitLab Environments](https://gitlab.version.fz-juelich.de/help/ci/environments), you can control the Continuous Delivery and -Deployment of your software all within GitLab.
All you need to do is define them in your project's [.gitlab-ci.yml](https://docs.gitlab.com/ee/ci/yaml/README.html) as we will explore below. GitLab provides a full history of your deployments per every environment.
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 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, so you always know what is currently being deployed on your servers. It full history of your deployments per every environment.
