archive-gh-me/docker-gitlab
1
0
Fork 0
mirror of https://github.com/sameersbn/docker-gitlab.git synced 2026-01-18 13:58:25 +00:00
Code Issues Projects Releases Wiki Activity

fix CI migration guide, Closes #484

Browse Source
This commit is contained in:
Sameer Naik 2015-10-27 22:10:53 +05:30
parent 3d1ccdc1cb
commit 37e0e885bf
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
CI_MIGRATION.md
View File

@ -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