@@ -29,7 +29,7 @@ That way you can prevent bugs not only in your software, but in the deployment p
The process from code development to shipping the software can be defined in a workflow with the major parts of
***Continuous Integration (CI) pipeline**
***Continuous Delivery and -Deloyment (CDs) pipeline**.
***Continuous Delivery and -Deployment (CDs) pipeline**.
How to use Git to accomplish this work in a consistent and productive manner can be described by a [Git Workflow](https://www.atlassian.com/git/tutorials/comparing-workflows). It encourage users to leverage Git effectively and consistently.
...
...
@@ -249,22 +249,22 @@ In this project the [CI Job "deploy-doc"](https://gitlab.version.fz-juelich.de/v
# Continuous Delivery and -Deloyment (CDs) Pipeline
# Continuous Delivery and -Deployment (CDs) Pipeline
| **Note:** GitLab's Continuous Delivery and -Deloyment (CDs) Pipeline can do any automatic delivery and deployment for you defined in [.gitlab-ci.yml.](https://docs.gitlab.com/ee/ci/yaml/README.html).
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.
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 (Continuous Delivery)
* before you release it to the public (Continuous Deployment).
That way you can prevent bugs not only in your software, but in the deployment process as well.
GitLab CI is capable of not only testing or building your projects, but also deploying them in your infrastructure, with the added benefit of giving you 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.
GitLab CI is capable of not only testing or building your projects (Continuous Integration (CI)), but also delivering/deploying them in your infrastructure, with the added benefit of giving you a way to track your deliverys/deployments. In other words, you can always know what is currently being delivered/deployed or has been delivered/deployed on your servers.
## GitLab Environments
With [GitLab Environments](https://gitlab.version.fz-juelich.de/help/ci/environments), you can control the Continuous 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.
[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 [jobs](yaml/README.md#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. If you have a deployment service such as [Kubernetes](../user/project/clusters/index.md) enabled for your project, you can use it to assist with your deployments, and can even access a [web terminal](#web-terminals) for your environment from within GitLab!, you can control the Continuous Deployment of your software all within GitLab. All you need to do is define them in your project's [`.gitlab-ci.yml`](yaml/README.md) 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 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.
Environments are like tags for your CI jobs, describing where code gets deployed. Deployments are created when [jobs](yaml/README.md#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. If you have a deployment service such as [Kubernetes](../user/project/clusters/index.md) enabled for your project, you can use it to assist with your deployments, and can even access a [web terminal](#web-terminals) for your environment from within GitLab!
\ No newline at end of file
[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.
