kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity

Add global numbering

Browse source
This commit is contained in:
Jacob Vosmaer 2015-09-22 14:02:36 +02:00
parent e72ba928f9
commit f0f5be82b0
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
doc/migrate_ci_to_ce/README.md
View file

@ -89,7 +89,7 @@ traces is `/var/opt/gitlab/gitlab-ci/builds` (Omnibus) or
a special location, or if you are using NFS, you should make sure that you a special location, or if you are using NFS, you should make sure that you
store build traces on the same storage as your Git repositories. store build traces on the same storage as your Git repositories.
### Upgrading ### I. Upgrading
From this point on, GitLab CI will be unavailable for your end users. From this point on, GitLab CI will be unavailable for your end users.
@ -119,7 +119,7 @@ cd /home/gitlab_ci/gitlab-ci
sudo -u gitlab_ci -H bundle exec whenever --clear-crontab sudo -u gitlab_ci -H bundle exec whenever --clear-crontab
``` ```
### Moving data ### II. Moving data
- (1) Move the database encryption key from your CI server to your GitLab - (1) Move the database encryption key from your CI server to your GitLab
server. The command below will show you what you need to copy-paste to your server. The command below will show you what you need to copy-paste to your
@ -201,7 +201,7 @@ sudo gitlab-ctl restart sidekiq
sudo service gitlab reload sudo service gitlab reload
``` ```
### Redirecting traffic ### III. Redirecting traffic
If you were running GitLab CI with Omnibus packages and you were using the If you were running GitLab CI with Omnibus packages and you were using the
internal NGINX configuration your CI service should now be available both at internal NGINX configuration your CI service should now be available both at