Merge branch '47532-follow-up-from-resolve-add-deploy-strategies-to-auto-devops-settings' into 'master'
Resolve "Follow-up from "Resolve "Add deploy strategies to Auto DevOps settings""" Closes #47532 See merge request gitlab-org/gitlab-ce!19554
This commit is contained in:
commit
b32f3685ae
1 changed files with 27 additions and 3 deletions
|
@ -213,11 +213,11 @@ full use of Auto DevOps. If this is your fist time, we recommend you follow the
|
||||||
To enable Auto DevOps to your project:
|
To enable Auto DevOps to your project:
|
||||||
|
|
||||||
1. Check that your project doesn't have a `.gitlab-ci.yml`, or remove it otherwise
|
1. Check that your project doesn't have a `.gitlab-ci.yml`, or remove it otherwise
|
||||||
1. Go to your project's **Settings > CI/CD > General pipelines settings** and
|
1. Go to your project's **Settings > CI/CD > Auto DevOps**
|
||||||
find the Auto DevOps section
|
|
||||||
1. Select "Enable Auto DevOps"
|
1. Select "Enable Auto DevOps"
|
||||||
1. Optionally, but recommended, add in the [base domain](#auto-devops-base-domain)
|
1. Optionally, but recommended, add in the [base domain](#auto-devops-base-domain)
|
||||||
that will be used by Kubernetes to deploy your application
|
that will be used by Kubernetes to [deploy your application](#auto-deploy)
|
||||||
|
and choose the [deployment strategy](#deployment-strategy)
|
||||||
1. Hit **Save changes** for the changes to take effect
|
1. Hit **Save changes** for the changes to take effect
|
||||||
|
|
||||||
Once saved, an Auto DevOps pipeline will be triggered on the default branch.
|
Once saved, an Auto DevOps pipeline will be triggered on the default branch.
|
||||||
|
@ -234,6 +234,24 @@ in **Admin Area > Settings > Continuous Integration and Deployment**. Doing that
|
||||||
all the projects that haven't explicitly set an option will have Auto DevOps
|
all the projects that haven't explicitly set an option will have Auto DevOps
|
||||||
enabled by default.
|
enabled by default.
|
||||||
|
|
||||||
|
### Deployment strategy
|
||||||
|
|
||||||
|
> [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/issues/38542) in GitLab 11.0.
|
||||||
|
|
||||||
|
You can change the deployment strategy used by Auto DevOps by going to your
|
||||||
|
project's **Settings > CI/CD > Auto DevOps**.
|
||||||
|
|
||||||
|
The available options are:
|
||||||
|
|
||||||
|
- **Continuous deployment to production** - enables [Auto Deploy](#auto-deploy)
|
||||||
|
by setting the [`STAGING_ENABLED`](#deploy-policy-for-staging-and-production-environments) and
|
||||||
|
[`INCREMENTAL_ROLLOUT_ENABLED`](#incremental-rollout-to-production) variables
|
||||||
|
to false.
|
||||||
|
- **Automatic deployment to staging, manual deployment to production** - sets the
|
||||||
|
[`STAGING_ENABLED`](#deploy-policy-for-staging-and-production-environments) and
|
||||||
|
[`INCREMENTAL_ROLLOUT_ENABLED`](#incremental-rollout-to-production) variables
|
||||||
|
to true, and the user is responsible for manually deploying to staging and production.
|
||||||
|
|
||||||
## Stages of Auto DevOps
|
## Stages of Auto DevOps
|
||||||
|
|
||||||
The following sections describe the stages of Auto DevOps. Read them carefully
|
The following sections describe the stages of Auto DevOps. Read them carefully
|
||||||
|
@ -652,6 +670,9 @@ service:
|
||||||
> [Introduced](https://gitlab.com/gitlab-org/gitlab-ci-yml/merge_requests/160)
|
> [Introduced](https://gitlab.com/gitlab-org/gitlab-ci-yml/merge_requests/160)
|
||||||
in GitLab 10.8.
|
in GitLab 10.8.
|
||||||
|
|
||||||
|
TIP: **Tip:**
|
||||||
|
You can also set this inside your [project's settings](#deployment-strategy).
|
||||||
|
|
||||||
The normal behavior of Auto DevOps is to use Continuous Deployment, pushing
|
The normal behavior of Auto DevOps is to use Continuous Deployment, pushing
|
||||||
automatically to the `production` environment every time a new pipeline is run
|
automatically to the `production` environment every time a new pipeline is run
|
||||||
on the default branch. However, there are cases where you might want to use a
|
on the default branch. However, there are cases where you might want to use a
|
||||||
|
@ -682,6 +703,9 @@ If `CANARY_ENABLED` is defined in your project (e.g., set `CANARY_ENABLED` to
|
||||||
|
|
||||||
> [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/issues/5415) in GitLab 10.8.
|
> [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/issues/5415) in GitLab 10.8.
|
||||||
|
|
||||||
|
TIP: **Tip:**
|
||||||
|
You can also set this inside your [project's settings](#deployment-strategy).
|
||||||
|
|
||||||
When you have a new version of your app to deploy in production, you may want
|
When you have a new version of your app to deploy in production, you may want
|
||||||
to use an incremental rollout to replace just a few pods with the latest code.
|
to use an incremental rollout to replace just a few pods with the latest code.
|
||||||
This will allow you to first check how the app is behaving, and later manually
|
This will allow you to first check how the app is behaving, and later manually
|
||||||
|
|
Loading…
Reference in a new issue