diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2019-11-21 21:06:37 +0000 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2019-11-21 21:06:37 +0000 |
commit | 7f15e74dae019ac96c65ec769eae2d67aae65a8c (patch) | |
tree | b770f8e25a2c1edbb53fbc80ecba547f087db052 /doc/ci | |
parent | 7aada820a908502f40080274fb181281afd44615 (diff) | |
download | gitlab-ce-7f15e74dae019ac96c65ec769eae2d67aae65a8c.tar.gz |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/ci')
-rw-r--r-- | doc/ci/environments.md | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/ci/environments.md b/doc/ci/environments.md index 0f978a8f3a9..bd989157486 100644 --- a/doc/ci/environments.md +++ b/doc/ci/environments.md @@ -485,6 +485,13 @@ To retry or rollback a deployment: - **Retry** button next to the last deployment, to retry that deployment. - **Rollback** button next to a previously successful deployment, to roll back to that deployment. +#### What to expect with a rollback + +Pressing the **Rollback** button on a specific commit will trigger a _new_ deployment with its +own unique job ID. + +This means that you will see a new deployment that points to the commit you are rolling back to. + NOTE: **Note:** The defined deployment process in the job's `script` determines whether the rollback succeeds or not. |