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

相关文章

华为鸿蒙HarmonyOS 5.1官宣7月开启升级! 首批支持名单公布

《华为鸿蒙HarmonyOS5.1官宣7月开启升级!首批支持名单公布》在刚刚结束的华为Pura80系列及全场景新品发布会上,除了众多新品的发布,还有一个消息也点燃了所有鸿蒙用户的期待,那就是Ha... 在今日的华为 Pura 80 系列及全场景新品发布会上,华为宣布鸿蒙 HarmonyOS 5.1 将于 7

GitLab文件的上传与下载方式

《GitLab文件的上传与下载方式》:本文主要介绍GitLab文件的上传与下载方式,具有很好的参考价值,希望对大家有所帮助,如有错误或未考虑完全的地方,望不吝赐教... 目录GitLab 项目拉取到本地GitLab 项目上传方法方法 1:本地项目未初始化Git方法 2:本地项目已初始化GitGitLab 上

ubuntu系统使用官方操作命令升级Dify指南

《ubuntu系统使用官方操作命令升级Dify指南》Dify支持自动化执行、日志记录和结果管理,适用于数据处理、模型训练和部署等场景,今天我们就来看看ubuntu系统中使用官方操作命令升级Dify的方... Dify 是一个基于 docker 的工作流管理工具,旨在简化机器学习和数据科学领域的多步骤工作流。

将Mybatis升级为Mybatis-Plus的详细过程

《将Mybatis升级为Mybatis-Plus的详细过程》本文详细介绍了在若依管理系统(v3.8.8)中将MyBatis升级为MyBatis-Plus的过程,旨在提升开发效率,通过本文,开发者可实现... 目录说明流程增加依赖修改配置文件注释掉MyBATisConfig里面的Bean代码生成使用IDEA生

linux环境openssl、openssh升级流程

《linux环境openssl、openssh升级流程》该文章详细介绍了在Ubuntu22.04系统上升级OpenSSL和OpenSSH的方法,首先,升级OpenSSL的步骤包括下载最新版本、安装编译... 目录一.升级openssl1.官网下载最新版openssl2.安装编译环境3.下载后解压安装4.备份

怎么关闭Ubuntu无人值守升级? Ubuntu禁止自动更新的技巧

《怎么关闭Ubuntu无人值守升级?Ubuntu禁止自动更新的技巧》UbuntuLinux系统禁止自动更新的时候,提示“无人值守升级在关机期间,请不要关闭计算机进程”,该怎么解决这个问题?详细请看... 本教程教你如何处理无人值守的升级,即 Ubuntu linux 的自动系统更新。来源:https://

你的华为手机升级了吗? 鸿蒙NEXT多连推5.0.123版本变化颇多

《你的华为手机升级了吗?鸿蒙NEXT多连推5.0.123版本变化颇多》现在的手机系统更新可不仅仅是修修补补那么简单了,华为手机的鸿蒙系统最近可是动作频频,给用户们带来了不少惊喜... 为了让用户的使用体验变得很好,华为手机不仅发布了一系列给力的新机,还在操作系统方面进行了疯狂的发力。尤其是近期,不仅鸿蒙O

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服务,是无法支持平滑升级(优雅重启)的,本文将探讨如何解决该问题。 一、平滑升级(优雅重启)的一般思路 一般情况下,要实现平滑

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