From e72ba928f98358d090fad68ae3794f494ad971cd Mon Sep 17 00:00:00 2001 From: Jacob Vosmaer Date: Tue, 22 Sep 2015 13:59:40 +0200 Subject: Downtime expectations --- doc/migrate_ci_to_ce/README.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) 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 -- cgit v1.2.1