Gitlab-ce upgrade 16.0.1 to 17.3.1【Gitlab-ce 16.0.1 升级 17.3.1】

2024-09-05 02:28
文章标签 升级 gitlab 17.3 ce 16.0 upgrade

本文主要是介绍Gitlab-ce upgrade 16.0.1 to 17.3.1【Gitlab-ce 16.0.1 升级 17.3.1】，希望对大家解决编程问题提供一定的参考价值，需要的开发者们随着小编来一起学习吧！

在这里插入图片描述

文章目录

  • 背景
  • gitlab-ce 16.0.1 升级 17.3.1 失败
  • gitlab-ce 16.0.1 升级 16.11.8 失败
  • gitlab-ce 16.0.1 升级 16.7.9 失败
  • gitlab-ce 16.0.1 升级 16.3.8 成功
  • gitlab-ce 16.3.8 升级 16.11.8 失败
  • gitlab-ce 16.3.8 升级 16.7.9 成功
  • gitlab-ce 16.7.9 升级 16.11.8 成功
  • gitlab-ce 16.11.8 升级 17.3.1 成功

背景

当前版本 gitab-ce 16.0.1， 准备升级最新版本（17.3.1）。

在这里插入图片描述

  • 先迁移gitlab数据至测试节点。

文章目录

  • 背景
  • gitlab-ce 16.0.1 升级 17.3.1 失败
  • gitlab-ce 16.0.1 升级 16.11.8 失败
  • gitlab-ce 16.0.1 升级 16.7.9 失败
  • gitlab-ce 16.0.1 升级 16.3.8 成功
  • gitlab-ce 16.3.8 升级 16.11.8 失败
  • gitlab-ce 16.3.8 升级 16.7.9 成功
  • gitlab-ce 16.7.9 升级 16.11.8 成功
  • gitlab-ce 16.11.8 升级 17.3.1 成功

gitlab-ce 16.0.1 升级 17.3.1 失败


#!/bin/bash
GITLAB_HOME='/data/gitlab'
docker run -tid --hostname gitlab.bsgchina.com -p 443:443 -p 80:80 -p 30022:22 --name gitlab-17.3.1-ce --restart always -v $GITLAB_HOME/config:/etc/gitlab:Z -v $GITLAB_HOME/logs:/var/log/gitlab:Z -v $GITLAB_HOME/data:/var/opt/gitlab:Z --shm-size 256m gitlab/gitlab-ce:17.3.1-ce.0
#!/bin/bash
GITLAB_HOME='/data/gitlab'
docker run -tid --hostname gitlab.bsgchina.com -p 443:443 -p 80:80 -p 30022:22 --name gitlab-17.3.1-ce --restart always -v $GITLAB_HOME/config:/etc/gitlab:Z -v $GITLAB_HOME/logs:/var/log/gitlab:Z -v $GITLAB_HOME/data:/var/opt/gitlab:Z --shm-size 256m gitlab/gitlab-ce:17.3.1-ce.0

[root@gitlab-backup2 gitlab]# docker logs -f 55de
Thank you for using GitLab Docker Image!
Current version: gitlab-ce=17.3.1-ce.0Configure GitLab for your system by editing /etc/gitlab/gitlab.rb file
And restart this container to reload settings.
To do it use docker exec:docker exec -it gitlab editor /etc/gitlab/gitlab.rbdocker restart gitlabFor a comprehensive list of configuration options please see the Omnibus GitLab readme
https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/README.mdIf this container fails to start due to permission problems try to fix it by executing:docker exec -it gitlab update-permissionsdocker restart gitlabCleaning stale PIDs & sockets
It seems you are upgrading from 16.0.1 to 17.3.1.
It is required to upgrade to the latest 16.11.x version first before proceeding.
Please follow the upgrade documentation at https://docs.gitlab.com/ee/update/index.html#upgrading-to-a-new-major-version
Thank you for using GitLab Docker Image!
Current version: gitlab-ce=17.3.1-ce.0Configure GitLab for your system by editing /etc/gitlab/gitlab.rb file
And restart this container to reload settings.
To do it use docker exec:docker exec -it gitlab editor /etc/gitlab/gitlab.rbdocker restart gitlabFor a comprehensive list of configuration options please see the Omnibus GitLab readme
https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/README.mdIf this container fails to start due to permission problems try to fix it by executing:docker exec -it gitlab update-permissionsdocker restart gitlabCleaning stale PIDs & sockets
It seems you are upgrading from 16.0.1 to 17.3.1.
It is required to upgrade to the latest 16.11.x version first before proceeding.
Please follow the upgrade documentation at https://docs.gitlab.com/ee/update/index.html#upgrading-to-a-new-major-version
Thank you for using GitLab Docker Image!
Current version: gitlab-ce=17.3.1-ce.0Configure GitLab for your system by editing /etc/gitlab/gitlab.rb file
And restart this container to reload settings.
To do it use docker exec:docker exec -it gitlab editor /etc/gitlab/gitlab.rbdocker restart gitlabFor a comprehensive list of configuration options please see the Omnibus GitLab readme
https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/README.mdIf this container fails to start due to permission problems try to fix it by executing:docker exec -it gitlab update-permissionsdocker restart gitlabCleaning stale PIDs & sockets
It seems you are upgrading from 16.0.1 to 17.3.1.
It is required to upgrade to the latest 16.11.x version first before proceeding.
Please follow the upgrade documentation at https://docs.gitlab.com/ee/update/index.html#upgrading-to-a-new-major-version
[root@gitlab-backup2 gitlab]# docker logs -f 55de

gitlab-ce 16.0.1 升级 16.11.8 失败

#!/bin/bash
GITLAB_HOME='/data/gitlab'
docker run -tid --hostname gitlab.bsgchina.com -p 443:443 -p 80:80 -p 30022:22 --name gitlab-16.11.8-ce --restart always -v $GITLAB_HOME/config:/etc/gitlab:Z -v $GITLAB_HOME/logs:/var/log/gitlab:Z -v $GITLAB_HOME/data:/var/opt/gitlab:Z --shm-size 256m gitlab/gitlab-ce:16.11.8-ce.0

Thank you for using GitLab Docker Image!
Current version: gitlab-ce=16.11.8-ce.0Configure GitLab for your system by editing /etc/gitlab/gitlab.rb file
And restart this container to reload settings.
To do it use docker exec:docker exec -it gitlab editor /etc/gitlab/gitlab.rbdocker restart gitlabFor a comprehensive list of configuration options please see the Omnibus GitLab readme
https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/README.mdIf this container fails to start due to permission problems try to fix it by executing:docker exec -it gitlab update-permissionsdocker restart gitlabCleaning stale PIDs & sockets
It seems you are upgrading from 16.0.1 to 16.11.8.
It is required to upgrade to the latest 16.7.x version first before proceeding.
Please follow the upgrade documentation at https://docs.gitlab.com/ee/update/#upgrade-paths
Thank you for using GitLab Docker Image!
Current version: gitlab-ce=16.11.8-ce.0Configure GitLab for your system by editing /etc/gitlab/gitlab.rb file
And restart this container to reload settings.
To do it use docker exec:docker exec -it gitlab editor /etc/gitlab/gitlab.rbdocker restart gitlabFor a comprehensive list of configuration options please see the Omnibus GitLab readme
https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/README.mdIf this container fails to start due to permission problems try to fix it by executing:docker exec -it gitlab update-permissionsdocker restart gitlabCleaning stale PIDs & sockets
It seems you are upgrading from 16.0.1 to 16.11.8.
It is required to upgrade to the latest 16.7.x version first before proceeding.
Please follow the upgrade documentation at https://docs.gitlab.com/ee/update/#upgrade-paths

gitlab-ce 16.0.1 升级 16.7.9 失败

cat start-16.7.9-ce.0.sh 
#!/bin/bash
GITLAB_HOME='/data/gitlab'
docker run -tid --hostname gitlab.bsgchina.com -p 443:443 -p 80:80 -p 30022:22 --name gitlab-16.7.9-ce.0 --restart always -v $GITLAB_HOME/config:/etc/gitlab:Z -v $GITLAB_HOME/logs:/var/log/gitlab:Z -v $GITLAB_HOME/data:/var/opt/gitlab:Z --shm-size 256m gitlab/gitlab-ce:16.7.9-ce.0

Thank you for using GitLab Docker Image!
Current version: gitlab-ce=16.7.9-ce.0Configure GitLab for your system by editing /etc/gitlab/gitlab.rb file
And restart this container to reload settings.
To do it use docker exec:docker exec -it gitlab editor /etc/gitlab/gitlab.rbdocker restart gitlabFor a comprehensive list of configuration options please see the Omnibus GitLab readme
https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/README.mdIf this container fails to start due to permission problems try to fix it by executing:docker exec -it gitlab update-permissionsdocker restart gitlabCleaning stale PIDs & sockets
It seems you are upgrading from 16.0.1 to 16.7.9.
It is required to upgrade to the latest 16.3.x version first before proceeding.
Please follow the upgrade documentation at https://docs.gitlab.com/ee/update/#upgrade-paths

gitlab-ce 16.0.1 升级 16.3.8 成功

数据保留

$ vim start-16.3.8-ce.0.sh
#!/bin/bash
GITLAB_HOME='/data/gitlab'
docker run -tid --hostname gitlab.bsgchina.com -p 443:443 -p 80:80 -p 30022:22 --name gitlab-16.3.8-ce.0 --restart always -v $GITLAB_HOME/config:/etc/gitlab:Z -v $GITLAB_HOME/logs:/var/log/gitlab:Z -v $GITLAB_HOME/data:/var/opt/gitlab:Z --shm-size 256m gitlab/gitlab-ce:16.3.8-ce.0

查看日志

$ docker logs -f gitlab-16.3.8-ce.0

等待10分钟。

在这里插入图片描述

gitlab-ce 16.3.8 升级 16.11.8 失败

$ cat start-16.11.8-ce.0_2.sh
#!/bin/bash
GITLAB_HOME='/data/gitlab'
docker run -tid --hostname gitlab.bsgchina.com -p 443:443 -p 80:80 -p 30022:22 --name gitlab-16.11.8-ce.0 -v /data/gitlab2/config:/etc/gitlab:Z -v $GITLAB_HOME/logs:/var/log/gitlab:Z -v $GITLAB_HOME/data:/var/opt/gitlab:Z --shm-size 256m gitlab/gitlab-ce:16.11.8-ce.0

Thank you for using GitLab Docker Image!
Current version: gitlab-ce=16.11.8-ce.0Configure GitLab for your system by editing /etc/gitlab/gitlab.rb file
And restart this container to reload settings.
To do it use docker exec:docker exec -it gitlab editor /etc/gitlab/gitlab.rbdocker restart gitlabFor a comprehensive list of configuration options please see the Omnibus GitLab readme
https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/README.mdIf this container fails to start due to permission problems try to fix it by executing:docker exec -it gitlab update-permissionsdocker restart gitlabCleaning stale PIDs & sockets
It seems you are upgrading from 16.3.8 to 16.11.8.
It is required to upgrade to the latest 16.7.x version first before proceeding.
Please follow the upgrade documentation at https://docs.gitlab.com/ee/update/#upgrade-paths

gitlab-ce 16.3.8 升级 16.7.9 成功

项目与用户数据保留完成。gitlab-runner 需要是否重新注册待确认。

$ start-16.7.9-ce.0_2.sh
#!/bin/bash
GITLAB_HOME='/data/gitlab'
docker run -tid --hostname gitlab.bsgchina.com -p 443:443 -p 80:80 -p 30022:22 --name gitlab-16.7.9-ce.0 -v /data/gitlab2/config:/etc/gitlab:Z -v $GITLAB_HOME/logs:/var/log/gitlab:Z -v $GITLAB_HOME/data:/var/opt/gitlab:Z --shm-size 256m gitlab/gitlab-ce:16.7.9-ce.0

项目与用户数据保留完成。

在这里插入图片描述

gitlab-ce 16.7.9 升级 16.11.8 成功

项目与用户数据保留完成。gitlab-runner 需要是否重新注册待确认。

$ cat start-16.11.8-ce.0_2.sh 
#!/bin/bash
GITLAB_HOME='/data/gitlab'
docker run -tid --hostname gitlab.bsgchina.com -p 443:443 -p 80:80 -p 30022:22 --name gitlab-16.11.8-ce.0 -v /data/gitlab2/config:/etc/gitlab:Z -v $GITLAB_HOME/logs:/var/log/gitlab:Z -v $GITLAB_HOME/data:/var/opt/gitlab:Z --shm-size 256m gitlab/gitlab-ce:16.11.8-ce.0

在这里插入图片描述

gitlab-ce 16.11.8 升级 17.3.1 成功

项目与用户数据保留完成。gitlab-runner 需要是否重新注册待确认。

$ cat start-17.3.1-ce.0_2.sh 
#!/bin/bash
GITLAB_HOME='/data/gitlab'
docker run -tid --hostname gitlab.bsgchina.com -p 443:443 -p 80:80 -p 30022:22 --name gitlab-17.3.1-ce.0 -v /data/gitlab2/config:/etc/gitlab:Z -v $GITLAB_HOME/logs:/var/log/gitlab:Z -v $GITLAB_HOME/data:/var/opt/gitlab:Z --shm-size 256m gitlab/gitlab-ce:17.3.1-ce.0

在这里插入图片描述

参考：

  • https://docs.gitlab.com/
  • https://docs.gitlab.com/ee/update/

这篇关于Gitlab-ce upgrade 16.0.1 to 17.3.1【Gitlab-ce 16.0.1 升级 17.3.1】的文章就介绍到这儿，希望我们推荐的文章对编程师们有所帮助！


http://www.chinasem.cn/article/1137704。

相关文章

macOS升级后SVN升级

macOS升级后SVN升级

问题 svn: error: The subversion command line tools are no longer provided by Xcode. 解决 sudo chown -R $(whoami) /usr/local/Cellar brew install svn
阅读更多...
Golang支持平滑升级的HTTP服务

Golang支持平滑升级的HTTP服务

前段时间用Golang在做一个HTTP的接口，因编译型语言的特性，修改了代码需要重新编译可执行文件，关闭正在运行的老程序，并启动新程序。对于访问量较大的面向用户的产品，关闭、重启的过程中势必会出现无法访问的情况，从而影响用户体验。 使用Golang的系统包开发HTTP服务，是无法支持平滑升级（优雅重启）的，本文将探讨如何解决该问题。 一、平滑升级（优雅重启）的一般思路 一般情况下，要实现平滑
阅读更多...
JeecgBoot 升级springboot版本到2.6.0

JeecgBoot 升级springboot版本到2.6.0

1. 环境描述 Jeecgboot 3.0，他所依赖的springboot版本为2.3.5Release，将springboot版本升级为2.6.0。过程全纪录，从2开始描述。 2. 修改springboot版本号 <parent><groupId>org.springframework.boot</groupId><artifactId>spring-boot-starter-pare
阅读更多...
欧拉系统 kernel 升级、降级

欧拉系统 kernel 升级、降级

系统版本  cat  /etc/os-release  NAME="openEuler"VERSION="22.03 (LTS-SP1)"ID="openEuler"VERSION_ID="22.03"PRETTY_NAME="openEuler 22.03 (LTS-SP1)"ANSI_COLOR="0;31" 系统初始 kernel 版本 5.10.0-136.12.0.
阅读更多...
Zookeeper集群是如何升级到新版本的

Zookeeper集群是如何升级到新版本的

方案1：复用老数据方案 这是经过实践的升级方案，该方案是复用旧版本的数据，zk集群拓扑，配置文件都不变，只是启动的程序为最新的版本。 参考文章： Zookeeper集群是如何升级到新版本的 方案2：重新建立数据方案 该方案的思路是：先停掉一台follower的机器上的服务，然后加入一个新版本的zk(zk的数据目录是空的)，然后启动新zk，之后新zk会把旧集群中的数据同步过来。之后再操作另
阅读更多...
Gerrit与Gitlab同步配置replication其他配置

Gerrit与Gitlab同步配置replication其他配置

一、Gerrit与Gitlab同步配置 当配置好gerrit环境后，还需要与现有gitlab库进行同步配置，否则会影响现有开发与打包流程。 1.安装gerrit replication插件 unzip gerrit.warcp WEB-INF/plugins/replication.jar ~/temp/ssh -p 29418 admin@172.19.16.64 gerrit plu
阅读更多...
mysql数据库8.0小版本原地升级

mysql数据库8.0小版本原地升级

mysql数据库8.0小版本原地升级 准备工作升级工作停库使用新版本软件启动数据库更新环境变量重启数据库 升级日志 OS release: CentOS 7.9升级前DB version: MySQL 8.0.30数据库升级安装包：mysql-8.0.36-linux-glibc2.12-x86_64.tar.xzMySQL Shell安装包：mysql-shell-8.0.36
阅读更多...
面试官：synchronized的锁升级过程是怎样的？

面试官：synchronized的锁升级过程是怎样的？

大家好，我是大明哥，一个专注「死磕 Java」系列创作的硬核程序员。 回答 在 JDK 1.6之前，synchronized 是一个重量级、效率比较低下的锁，但是在JDK 1.6后，JVM 为了提高锁的获取与释放效，,对 synchronized 进行了优化，引入了偏向锁和轻量级锁，至此，锁的状态有四种，级别由低到高依次为：无锁、偏向锁、轻量级锁、重量级锁。 锁升级就是无锁 —>
阅读更多...
git命令上传代码到gitHub、gitLab

git命令上传代码到gitHub、gitLab

1 、输入git账号和密码 git config --global user.name"git账号" git config --global user.name"密码" 2.添加要上传的SSH （如果你的文件已经有了SSH，删除本身有的）git remote rm origin 添加 git remote add origin SSH或http 3 添加本地的所有文件  git ad
阅读更多...
自动升级系统OAUS续

自动升级系统OAUS续

一.缘起　　　　 　　自从 自动升级系统的设计与实现（源码） 发布以后，收到了很多使用者的反馈，其中最多的要求就是希望OAUS服务端增加自动检测文件变更的功能，这样每次部署版本升级时，可以节省很多时间，而且可以避免手动修改带来的错误。 　　现在，我就简单介绍一下最新版本的OAUS中关于这个功能的实现。在上一个版本中，我们是这样操作的：         　　每次有版本更新时，我们需
阅读更多...

Copyright China编程 23002807@qq.com

沪ICP备2023033072号-2