Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
李少辉-开发者
gitlab-foss
提交
12969a14
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,发现更多精彩内容 >>
提交
12969a14
编写于
9月 21, 2015
作者:
K
Kamil Trzcinski
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Add commands for Omnibus installation
上级
157ee662
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
62 addition
and
11 deletion
+62
-11
doc/migrate_ci_to_ce/README.md
doc/migrate_ci_to_ce/README.md
+62
-11
未找到文件。
doc/migrate_ci_to_ce/README.md
浏览文件 @
12969a14
...
...
@@ -19,7 +19,7 @@ time. Make sure to plan ahead.
If you are running a version of GitLab CI prior to 8.0 please follow the
appropriate
[
update guide
](
https://gitlab.com/gitlab-org/gitlab-ci/tree/master/doc/update/
)
.
The migration is divided into three parts:
The migration is divided into three parts
and covers manual and omnibus installations
:
1.
[
GitLab CI
](
#part-i-gitlab-ci
)
1.
[
Gitlab CE (or EE)
](
#part-ii-gitlab-ce-or-ee
)
...
...
@@ -29,7 +29,11 @@ The migration is divided into three parts:
#### 1. Stop GitLab CI
# Manual installation
sudo service gitlab_ci stop
# Omnibus installation
sudo gitlab-ctl stop ci-unicorn ci-sidekiq
#### 2. Create a backup
...
...
@@ -41,6 +45,8 @@ If your GitLab CI installation uses **MySQL** and your GitLab CE (or EE)
installation uses
**PostgreSQL**
you'll need to convert the CI database by
setting a
`MYSQL_TO_POSTGRESQL`
flag.
If you use Omnibus package you most likely use the
**PostgreSQL**
on GitLab CE (or EE) and CI.
You can check which database each install is using by viewing their
database configuration files:
...
...
@@ -50,21 +56,26 @@ database configuration files:
-
If both applications use the same database
`adapter`
, create the backup with
this command:
```bash
cd /home/gitlab_ci/gitlab-ci
sudo -u gitlab_ci -H bundle exec backup:create RAILS_ENV=production
```
# Manual installation
cd /home/gitlab_ci/gitlab-ci
sudo -u gitlab_ci -H bundle exec backup:create RAILS_ENV=production
# Omnibus installation
sudo gitlab-ci-rake backup:create
-
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
```
# Manual installation
cd /home/gitlab_ci/gitlab-ci
sudo -u gitlab_ci -H bundle exec backup:create RAILS_ENV=production MYSQL_TO_POSTGRESQL=1
# Omnibus installation
sudo gitlab-ci-rake backup:create MYSQL_TO_POSTGRESQL=1
#### 3. Remove cronjob
#### 3. Remove cronjob
(manual installation)
# Manual installation
cd /home/gitlab_ci/gitlab-ci
sudo -u gitlab_ci -H bundle exec whenever --clear-crontab
...
...
@@ -75,6 +86,8 @@ database configuration files:
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
)
.
If you use Omnibus package simply do
`apt-get upgrade`
to install a new version.
#### 2. Prevent CI usage for time of migration
As Admin go to Admin Area -> Settings -> and uncheck
...
...
@@ -86,20 +99,32 @@ This will prevent from creating the CI projects till you finish migration.
Before you can migrate data you need to stop the GitLab service first:
# Manual installation
sudo service gitlab stop
# Omnibus installation
sudo gitlab-ctl stop unicorn sidekiq
#### 4. Create a backup
This migration poses a
**significant risk**
of breaking your GitLab
installation. Create a backup before proceeding:
# Manual installation
cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
# Omnibus installation
sudo gitlab-rake gitlab:backup:create
It's possible to speedup backup creation. To do that you can skip repositories and uploads.
# Manual installation
cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production SKIP=repositories,uploads
# Omnibus installation
sudo gitlab-rake gitlab:backup:create SKIP=repositories,uploads
#### 5. Copy secret tokens from CI
...
...
@@ -108,11 +133,18 @@ The `secrets.yml` file stores encryption keys for secure variables.
You need to copy the contents of GitLab CI's
`config/secrets.yml`
file to the
same file in GitLab CE:
# Manual installation
sudo cp /home/gitlab_ci/gitlab-ci/config/secrets.yml /home/git/gitlab/config/secrets.yml
sudo chown git:git /home/git/gitlab/config/secrets.yml
sudo chown 0600 /home/git/gitlab/config/secrets.yml
#### 6. New configuration options for `gitlab.yml`
If you use Omnibus installation and your CI server is on the same server as GitLab CE (or EE) you don't need to do anything,
because the secrets are stored in
**/etc/gitlab/gitlab-secrets.json**
.
If you migrate your Omnibus CI server to other server you need to copy
**gitlab_ci**
section of
**/etc/gitlab/gitlab-secrets.json**
to the other server.
#### 6. New configuration options for `gitlab.yml` (manual installation only)
There are new configuration options available for
`gitlab.yml`
. View them with
the command below and apply them manually to your current
`gitlab.yml`
:
...
...
@@ -123,21 +155,34 @@ The new options include configuration settings for GitLab CI.
#### 7. Copy backup from GitLab CI
# Manual installation
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
# Omnibus installation
sudo cp -v /var/opt/gitlab/ci-backups/*_gitlab_ci_backup.tar /var/opt/gitlab/backups/
sudo chown git:git /var/opt/gitlab/backups/*_gitlab_ci_backup.tar
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`
.
# Manual installation
scp /home/gitlab_ci/gitlab-ci/tmp/backups/*_gitlab_ci_backup.tar root@gitlab.example.com:/home/git/gitlab/tmp/backup
# Omnibus installation
scp /var/opt/gitlab/ci-backups/*_gitlab_ci_backup.tar root@gitlab.example.com:/var/opt/gitlab/backups/
#### 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:
# Manual installation
sudo -u git -H bundle exec rake ci:migrate RAILS_ENV=production
# Omnibus installation
sudo gitlab-rake ci:migrate
This task will take some time.
...
...
@@ -145,10 +190,16 @@ This task will take some time.
You can start GitLab CE (or EE) now and see if everything is working:
# Manual installation
sudo service gitlab start
# Omnibus installation
sudo gitlab-ctl restart unicorn sidekiq
### Part III: Finishing Up
This part is only for
**Manual installations**
.
#### 1. Update Nginx configuration
To ensure that your existing CI runners are able to communicate with the
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录