Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
李少辉-开发者
gitlab-foss
提交
d2ab95d1
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,发现更多精彩内容 >>
提交
d2ab95d1
编写于
9月 22, 2015
作者:
J
Jacob Vosmaer
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Make code block comments more verbose
上级
3e926c6e
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
10 addition
and
10 deletion
+10
-10
doc/migrate_ci_to_ce/README.md
doc/migrate_ci_to_ce/README.md
+10
-10
未找到文件。
doc/migrate_ci_to_ce/README.md
浏览文件 @
d2ab95d1
...
...
@@ -33,7 +33,7 @@ upgrade to 8.0 until you finish the migration procedure.
Make sure that the backup script on both servers can connect to the database.
```
#
CI server
#
On your CI server:
# Omnibus
sudo gitlab-ci-rake backup:create
...
...
@@ -45,7 +45,7 @@ sudo -u gitlab_ci -H bundle exec rake backup:create RAILS_ENV=production
Also check on your GitLab server.
```
#
GitLab server
#
On your GitLab server:
# Omnibus
sudo gitlab-rake gitlab:backup:create SKIP=repositories,uploads
...
...
@@ -67,7 +67,7 @@ during the 'Moving data' part. **If your CI server uses PostgreSQL and your
GitLab server uses MySQL you cannot migrate your CI data to GitLab 8.0.
**
```
#
CI server
#
On your CI server:
# Omnibus
sudo gitlab-ci-rake env:info
...
...
@@ -77,7 +77,7 @@ sudo -u gitlab_ci -H bundle exec rake env:info RAILS_ENV=production
```
```
#
GitLab server
#
On your GitLab server:
# Omnibus
sudo gitlab-rake gitlab:env:info
...
...
@@ -127,7 +127,7 @@ Now upgrade GitLab CI to version 8.0. If you are using Omnibus packages,
Disable GitLab CI after upgrading to 8.0.
```
#
CI server
#
On your CI server:
# Omnibus
sudo gitlab-ctl stop ci-unicorn
sudo gitlab-ctl stop ci-sidekiq
...
...
@@ -149,7 +149,7 @@ GitLab server. On Omnibus GitLab servers you will have to add a line to
to replace the contents of
`/home/git/gitlab/config/secrets.yml`
.
```
#
CI server
#
On your CI server:
# Omnibus
sudo gitlab-ci-rake backup:show_secrets
...
...
@@ -166,7 +166,7 @@ the command finishes it will print the path to your data export archive; you
will need this file later.
```
#
CI server
#
On your CI server:
# Omnibus
sudo gitlab-ci-rake backup:create
...
...
@@ -198,7 +198,7 @@ Make the CI data archive discoverable for GitLab. We assume below that you
store backups in the default path, adjust the command if necessary.
```
#
GitLab server
#
On your GitLab server:
# Omnibus
sudo mv /path/to/12345_gitlab_ci_backup.tar /var/opt/gitlab/backups/
...
...
@@ -212,7 +212,7 @@ This step will delete any existing CI data on your GitLab server. There should
be no CI data yet because you turned CI on the GitLab server off earlier.
```
#
GitLab server
#
On your GitLab server:
# Omnibus
sudo gitlab-rake ci:migrate
...
...
@@ -224,7 +224,7 @@ sudo -u git -H bundle exec rake ci:migrate RAILS_ENV=production
#### 6. Restart GitLab
```
#
GitLab server
#
On your GitLab server:
# Omnibus
sudo gitlab-ctl hup unicorn
sudo gitlab-ctl restart sidekiq
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录