foreword
Well, the blogger here will first post some columns full of dry goods!
The first is a summary of bloggers’ high-quality blogs. The blogs in this column are all the bloggers’ most thoughtful writing. They are full of dry goods. I hope they will be helpful to everyone.
Then there is a column "Git Enterprise Development Control Theory and Practical Operations" that the blogger spends the most time recently. I hope everyone will pay more attention!
Enterprise Development Model
Enterprise-level development process
DevOps
DevOps (a portmanteau of Development and Operations) is a culture, movement or practice that values communication and collaboration between "software developers (Dev)" and "IT operations technicians (Ops)". By automating the "software delivery" and "architecture change" processes, building, testing, and releasing software can be faster, more frequent, and more reliable. The DevOps software development process includes planning, coding, construction, testing, pre-release, release, operation and maintenance, and monitoring, which shows the power of DevOps.
Having said so much, what does this story have to do with Git, the topic of our course?
A very simple example can illustrate this problem. A software iteration, in the eyes of our developers, is simply to iterate the code, so the code needs to be managed. How to manage our code, isn't that Gt (distributed version control system)! So the importance of Git to us developers is self-evident.
System development environment
When it comes to the key environments that developers need to be familiar with during the system development process, the following environments cannot be ignored:
-
Development Environment: A development environment is a platform that developers use exclusively for day-to-day coding and debugging. In this environment, all bug reporting and testing tools are usually enabled to ensure the foundational reliability of the code.
-
Test environment: If a program has problems running in the test environment, it must not be deployed to the production environment. The test environment is a key intermediate stage from the development environment to the production environment, used to transition and verify the stability and correctness of the code.
-
Pre-release environment: In order to avoid potential bug leaks caused by differences between the test environment and the online environment, the pre-release environment came into being. The configuration of this environment is basically the same as that of the production environment. Its main purpose is to provide more reliable verification before the code is officially launched, so it can be regarded as the final gate to ensure the quality of the project. It should be noted that the pre-release environment is separated from the online integration server and is a group of independent machines.
-
Production environment: The production environment refers to the online environment that provides formal services to the outside world, and users can access and use it on mobile or PC. All end users of mobile applications or PC applications interact with the system in this environment.
These environments can be viewed as three key phases of system development: development phase, testing phase, and go-live phase. Below is a diagram to more visually summarize these environments and their role in the development process.
For a slightly larger company, there are more than a few environments. For example, there are simulation/grayscale environments before the project is officially launched, and there are multiple test environments to meet the needs of testing different versions before going online.
Git enterprise branch design specification
Now I will introduce a commonly used branching model, the GitFlow model.
| the branch | name | use environment |
|---|---|---|
| master | main branch | Production Environment |
| release | pre-release branch | pre-release/test environment |
| develop | development branch | development environment |
| feature | Requirements development branch | local |
| hotfix | emergency fix branch | local |
The specific content can be found in the link:
https://baijiahao.baidu.com/s?id=1726693863458796523&wfr=spider&for=pc
Of course, this is not applicable to all cultures of all teams, and different companies may have different models.
Enterprise Project Management
DevOps platform
Many are subject to a fee. The blogger here uses this to demonstrate for everyone for free.
https://gitee.com/enterprises/new?from=gitee.com
New Project.
At this point, we have created a warehouse belonging to the enterprise.
In this way, the warehouse is created, and then we can do our development based on the above branch model.