From 37e0e885bf46fbda20fb2ba8670707ee9be8ac20 Mon Sep 17 00:00:00 2001 From: Sameer Naik Date: Tue, 27 Oct 2015 22:10:53 +0530 Subject: [PATCH] fix CI migration guide, Closes #484 --- CI_MIGRATION.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/CI_MIGRATION.md b/CI_MIGRATION.md index ec2d58b3..d83e6bcf 100644 --- a/CI_MIGRATION.md +++ b/CI_MIGRATION.md @@ -89,16 +89,16 @@ We are done with CI. If the rest of the migration goes was planned you will not ## Step 5 - Upgrade GitLab -Before we can upgrade to `quay.io/sameersbn/gitlab:8.1.2`, we need to assign the value of `GITLAB_CI_SECRETS_DB_KEY_BASE` (from CI) to `GITLAB_SECRETS_DB_KEY_BASE` in GitLab's environment. +Before we can upgrade to `quay.io/sameersbn/gitlab:8.0.5-1`, we need to assign the value of `GITLAB_CI_SECRETS_DB_KEY_BASE` (from CI) to `GITLAB_SECRETS_DB_KEY_BASE` in GitLab's environment. Next you also need to set the environment variable `GITLAB_CI_HOST` to the address of your CI server, eg. `ci.example.com`. This will make sure that your existing runners will be able to communicate to GitLab with the old url. -### Upgrade to `quay.io/sameersbn/gitlab:8.1.2` +### Upgrade to `quay.io/sameersbn/gitlab:8.0.5-1` ```bash docker run -it --rm [OPTIONS] \ --env GITLAB_CI_HOST=ci.example.com --env GITLAB_SECRETS_DB_KEY_BASE=xxxxxx \ - quay.io/sameersbn/gitlab:8.1.2 app:init + quay.io/sameersbn/gitlab:8.0.5-1 app:init ``` ### Migrate CI data @@ -106,7 +106,7 @@ docker run -it --rm [OPTIONS] \ ```bash docker run -it --rm [OPTIONS] \ --env GITLAB_CI_HOST=ci.example.com --env GITLAB_SECRETS_DB_KEY_BASE=xxxxxx \ - quay.io/sameersbn/gitlab:8.1.2 app:rake ci:migrate + quay.io/sameersbn/gitlab:8.0.5-1 app:rake ci:migrate ``` ## Step 6 - Fix DNS and reverse proxy configurations