summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJacob Vosmaer <contact@jacobvosmaer.nl>2015-09-22 13:59:40 +0200
committerJacob Vosmaer <contact@jacobvosmaer.nl>2015-09-22 13:59:40 +0200
commite72ba928f98358d090fad68ae3794f494ad971cd (patch)
tree9c594030e696bfc0a81a14329ad26a4b3c6489ed
parent917c9ea9278d3f3d3ae925351911e8ecc5c55a1f (diff)
downloadgitlab-ce-e72ba928f98358d090fad68ae3794f494ad971cd.tar.gz
Downtime expectations
-rw-r--r--doc/migrate_ci_to_ce/README.md5
1 files changed, 4 insertions, 1 deletions
diff --git a/doc/migrate_ci_to_ce/README.md b/doc/migrate_ci_to_ce/README.md
index 4070d15808c..838832d5cd4 100644
--- a/doc/migrate_ci_to_ce/README.md
+++ b/doc/migrate_ci_to_ce/README.md
@@ -21,7 +21,10 @@ The migration consists of three parts: updating GitLab and GitLab CI, moving
data, and redirecting traffic.
Please note that CI builds triggered on your GitLab server in the time between
-updating to 8.0 and finishing the migration will be lost.
+updating to 8.0 and finishing the migration will be lost. Your GitLab server
+can be online for most of the procedure; the only GitLab downtime (if any) is
+during the upgrade to 8.0. Your CI service will be offline from the moment you
+upgrade to 8.0 until you finish the migration procedure.
### Before upgrading