---
title: 商派 OMS 模块特征 材料 2025版本 CICD DEVOPS
description: 文本抽取：知识库/04-全渠道业务场景/商派 OMS 模块特征 材料 2025版本 CICD DEVOPS
updated: 2026-11-04
tags: [原始文档, 抽取, 知识库]
source: 知识库/04-全渠道业务场景/商派 OMS 模块特征 材料 2025版本 CICD DEVOPS
source_type: txt
source_hash: 5c894bdb9e62
extracted_at: 2026-11-04
quality: ok
---
---
source: 知识库/04-全渠道业务场景/商派 OMS 模块特征 材料 2025版本 CICD DEVOPS.pptx
type: pptx
size_kb: 111
category: 04-全渠道业务场景
quality: ok
---
## Slide 1
Git版本管理流程
master branch
pre-production branch
production branch
stable-1.0 branch
fix-1.0-[x] branch
核心开发分支，用于日常功能开发与代码集
测试环境分支，用于前后端联调测试
正式环境发布分支，用于预发布演示环境
基于Production发布的稳定版本基准分支
用于修复稳定版本的紧急问题
在本地完成修改后，应拉取远端的最新代码以确保同步。如果出现冲突，需进行合并（merge）。确认本地工程能够正常运行且无误后，方可将更改推送（push）到远端仓库。
需在 GitLab 上手动提交 Merge Request（MR），将远端 master 分支的更新合并至 pre-production 分支。
所有测试通过后，在 GitLab 上手动提交 Merge Request (MR)，将远端 pre-production 分支合并到 production 分支。
在 GitLab 上基于 production 分支创建 Tag，用于标识当前发布版本。
需在 GitLab 上从 Production 分支创建 stable 分支。
在 GitLab 中，应基于 stable 分支创建一个新的 fix 分支，以便在此分支上进行必要的修复工作。
从远端拉取分支到本地进行修改，完成开发和测试后，将更改提交（push）至远端对应分支。
需在 GitLab 上手动创建 Merge Request (MR)，将远端的 fix 分支合并到 stable 分支。 需在 GitLab 上基于 stable 分支创建标签（Tag）。
是否需要修复此 Bug？
Yes
下次迭代开发
No
签出分支
签出分支
tag v1.0.x
tag v1.0.0
## Slide 2
Git版本流程可视化
Master
pre-production
production
Stable
1.0_release
Fix
MR合并
测试通过
创建
版本发布
紧急修复
MR合并
## Slide 3
DevOps
01
02
03
04
项目管理
持续集成和测试
持续交付
持续运维
需求
管理
变更
管理
缺陷
管理
版本
管理
自动
构建
单元
测试
功能
测试
性能
测试
制品管理
自动
部署
配置
变更
监控
管理
知识库
JIRA
Git
代码
评审
Maven
Gradle
Junit
Jest
Selenium
Jmeter
Locust
代码质量分析
Sonarqube
Nexus
Harbor
sftp
Ansible
Docker
K8S
vm
CMDB
Gitea
Grafana
prometheus
Elastic Stack
Confluence
GitLab PR
自动集成
Jenkins
SkyWalking
## Slide 4
Git version management process
master branch
pre-production branch
production branch
stable-1.0 branch
fix-1.0-[x] branch
The core development branch is used for daily function development and code set
The test environment branch is used for front-end and back-end joint debugging tests
The official environment release branch is used for the pre-release demo environment
Based on the stable version benchmark branch released by Production
Used to fix urgent issues in the stable release
After the changes are completed locally, pull the latest code from the remote to ensure synchronization. If there is a conflict, merge (merge) it. Confirm that the local project is working properly and error-free before pushing (push) the changes to the remote repository.
The Merge Request (MR) needs to be manually submitted on the GitLab to merge updates from the remote master branch into the pre-production branch.
After all tests are passed, manually submit the Merge Request (MR) on the GitLab to merge the remote pre-production branch into the production branch.
Create a Tag on the GitLab based on the production branch to identify the current release version.
Create the stable branch from the Production branch on the GitLab.
In GitLab, a new fix branch should be created based on the stable branch so that necessary fixes can be made on this branch.
Pull the branch from the remote to the local for modification. After development and testing, submit (push) the changes to the corresponding branch on the remote.
You need to manually create a Merge Request (MR) on the GitLab and merge the remote fix branch into the stable branch. You need to create a tag (Tag) on the GitLab based on the stable branch.
Is it necessary to fix this Bug?
Yes
Next iteration development
No
Sign out of the branch
Sign out of the branch
tag v1.0.x
tag v1.0.0
## Slide 5
Git version flow visualization
Master
pre-production
production
Stable
1.0_release
Fix
MR merge
pass-test
build
release version
Emergency repair
MR merge
## Slide 6
DevOps
01
02
03
04
project management
Continuous integration and testing
Continuous delivery
Continuous operation and maintenance
requirement
manage
change
manage
defect
manage
edition
manage
voluntarily
structure
cell
testing
function
testing
Performance testing
supervisory control
manage
knowledge base
JIRA
Git
code
review
Maven
Gradle
Junit
Jest
Selenium
Jmeter
Locust
Code quality analysis
Sonarqube
Nexus
Product management
configure
change
Harbor
sftp
Ansible
voluntarily
arrange
Docker
K8S
vm
CMDB
Gitea
Grafana
prometheus
Elastic Stack
Confluence
GitLab PR
Automatic integration
Jenkins
SkyWalking