Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
李少辉-开发者
gitlab-foss
提交
157ee662
G
gitlab-foss
项目概览
李少辉-开发者
/
gitlab-foss
通知
15
Star
0
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
G
gitlab-foss
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
提交
157ee662
编写于
9月 21, 2015
作者:
K
Kamil Trzcinski
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Update guide
上级
d511edc9
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
32 addition
and
19 deletion
+32
-19
doc/migrate_ci_to_ce/README.md
doc/migrate_ci_to_ce/README.md
+32
-19
未找到文件。
doc/migrate_ci_to_ce/README.md
浏览文件 @
157ee662
...
...
@@ -30,7 +30,7 @@ The migration is divided into three parts:
#### 1. Stop GitLab CI
sudo service gitlab_ci stop
#### 2. Create a backup
The migration procedure modifies the structure of the CI database. If something
...
...
@@ -44,10 +44,8 @@ setting a `MYSQL_TO_POSTGRESQL` flag.
You can check which database each install is using by viewing their
database configuration files:
```
sh
cat
/home/gitlab_ci/gitlab-ci/config/database.yml
cat
/home/git/gitlab/config/database.yml
```
cat /home/gitlab_ci/gitlab-ci/config/database.yml
cat /home/git/gitlab/config/database.yml
-
If both applications use the same database
`adapter`
, create the backup with
this command:
...
...
@@ -56,22 +54,19 @@ cat /home/git/gitlab/config/database.yml
cd /home/gitlab_ci/gitlab-ci
sudo -u gitlab_ci -H bundle exec backup:create RAILS_ENV=production
```
-
If CI uses MySQL, and CE (or EE) uses PostgreSQL, create the backup with this
command (note the
`MYSQL_TO_POSTGRESQL`
flag):
```bash
cd /home/gitlab_ci/gitlab-ci
sudo -u gitlab_ci -H bundle exec backup:create RAILS_ENV=production MYSQL_TO_POSTGRESQL=1
```
#### 3. Remove cronjob
```
cd /home/gitlab_ci/gitlab-ci
sudo -u gitlab_ci -H bundle exec whenever --clear-crontab
```
cd /home/gitlab_ci/gitlab-ci
sudo -u gitlab_ci -H bundle exec whenever --clear-crontab
### Part II: GitLab CE (or EE)
...
...
@@ -80,21 +75,33 @@ sudo -u gitlab_ci -H bundle exec whenever --clear-crontab
Your GitLab CE or EE installation
**must be version 8.0**
. If it's not, follow
the
[
update guide
](
https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/update/7.14-to-8.0.md
)
.
#### 2. Stop GitLab
#### 2. Prevent CI usage for time of migration
As Admin go to Admin Area -> Settings -> and uncheck
**Disable to prevent CI usage until rake ci:migrate is run (8.0 only)**
.
This will prevent from creating the CI projects till you finish migration.
#### 3. Stop GitLab
Before you can migrate data you need to stop the GitLab service first:
sudo service gitlab stop
####
3
. Create a backup
####
4
. Create a backup
This migration poses a
**significant risk**
of breaking your GitLab
installation. Create a backup before proceeding:
cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
It's possible to speedup backup creation. To do that you can skip repositories and uploads.
#### 4. Copy secret tokens from CI
cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production SKIP=repositories,uploads
#### 5. Copy secret tokens from CI
The
`secrets.yml`
file stores encryption keys for secure variables.
...
...
@@ -105,7 +112,7 @@ same file in GitLab CE:
sudo chown git:git /home/git/gitlab/config/secrets.yml
sudo chown 0600 /home/git/gitlab/config/secrets.yml
####
5
. New configuration options for `gitlab.yml`
####
6
. New configuration options for `gitlab.yml`
There are new configuration options available for
`gitlab.yml`
. View them with
the command below and apply them manually to your current
`gitlab.yml`
:
...
...
@@ -114,12 +121,18 @@ the command below and apply them manually to your current `gitlab.yml`:
The new options include configuration settings for GitLab CI.
####
6
. Copy backup from GitLab CI
####
7
. Copy backup from GitLab CI
sudo cp -v /home/gitlab_ci/gitlab-ci/tmp/backups/*_gitlab_ci_backup.tar /home/git/gitlab/tmp/backups
sudo chown git:git /home/git/gitlab/tmp/backups/*_gitlab_ci_backup.tar
#### 7. Import GitLab CI backup
If moving across the servers you can use
**scp**
.
However, this requires you to provide authorized key or password to login to GitLab CE servers from CI server.
You can try to use ssh-agent from your local machine to have that: login to your GitLab CI server using
`ssh -A`
.
scp /home/gitlab_ci/gitlab-ci/tmp/backups/*_gitlab_ci_backup.tar root@gitlab.example.com:/home/git/gitlab/tmp/backup
#### 8. Import GitLab CI backup
Now you'll import the GitLab CI database dump that you created earlier into the
GitLab CE or EE database:
...
...
@@ -128,7 +141,7 @@ GitLab CE or EE database:
This task will take some time.
####
8
. Start GitLab
####
9
. Start GitLab
You can start GitLab CE (or EE) now and see if everything is working:
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录