Front-end collaborative development management and automatic construction deployment method and system, terminal and storage medium

Abstract

The invention discloses a front-end collaborative development management and automatic construction deployment method and system, a terminal and a storage medium. The method comprises the following steps: selecting a corresponding version control tool according to a front-end collaborative development task; performing unified standardization processing on the code format of the front-end collaborative development task based on the selected version control tool; performing branch standardization processing on the version iteration code of the development process of the front-end collaborative development task; and merging all developed code versions of the developer according to the user type, and deploying the merged code versions. According to the method, code merging conflicts can be effectively reduced, the construction and deployment efficiency is improved, and therefore the development efficiency and the product iteration speed are remarkably improved.

Description

Technical Field

[0001] The present invention relates to the field of front-end development technology, and in particular to a front-end collaborative development management and automated construction and deployment method, system, terminal and storage medium. Background Art

[0002] In today's internet industry, medium-to-large front-end projects often involve large teams of developers, frequently changing requirements, and the need for rapid iteration and continuous delivery. In these situations, incorrect management can lead to widespread code conflicts between versions, making manual builds and deployments time-consuming and labor-intensive, resulting in low development efficiency.

[0003] For front-end development project management, existing project management methods are developed for specific project types. Although this specific project management method can improve the management efficiency of a certain type of front-end development project, it cannot adapt to a variety of different front-end development projects, resulting in low compatibility. On the other hand, it adopts a general management method for management. This method cannot effectively reduce code merging conflicts, resulting in reduced development efficiency and product iteration speed.

[0004] Therefore, the existing technology needs to be improved. Summary of the Invention

[0005] The technical problem to be solved by the present invention is that, in response to the defects of the existing technology, the present invention provides a front-end collaborative development management and automated construction and deployment method, system, terminal and storage medium to solve the problem that the existing manual construction and deployment are time-consuming and labor-intensive, resulting in low development efficiency and product iteration speed.

[0006] The technical solutions adopted by the present invention to solve the technical problems are as follows: In a first aspect, the present invention provides a front-end collaborative development management and automated construction and deployment method, comprising: Select the corresponding version control tool based on the front-end collaborative development task; Standardize the code format of the front-end collaborative development task based on the selected version control tool; Performing branch normalization processing on the version iteration code of the development process of the front-end collaborative development task; Merge all code versions developed by developers according to user type and deploy the merged code versions.

[0007] In one implementation, selecting a corresponding version control tool according to the front-end collaborative development task includes: According to the front-end collaborative development task, a cloud-based collaborative development platform that supports code hosting, continuous integration, continuous deployment, issue tracking, and code review is selected as the version control tool.

[0008] In one implementation, the selected version control tool performs unified standardization processing on the code format of the front-end collaborative development task, including: Set development tool formatting rules for all developers; According to the formatting rules of the development tool, the code format of the front-end collaborative development task is uniformly standardized to obtain a code with a uniform format.

[0009] In one implementation, the development tool formatting rules include: one or a combination of code indentation space number, code line break word number, and code automation space rules.

[0010] In one implementation, the branch normalization processing of the version iteration code of the development process of the front-end collaborative development task includes: Build version iteration code branch architecture; Obtaining the main branch of the iterative code in the development process of the front-end collaborative development task; When the code version corresponding to the main branch is updated, a new version branch is pulled based on the main branch, and the current code version is iterated in the pulled new version branch.

[0011] In one implementation, merging all code versions developed by developers according to user type and deploying the merged code versions includes: Based on the version merge operation tool, selectively copy specific code versions and submit them to the selected branch in turn, and merge all code versions developed by the current developer; Install an open source application container engine and deploy the merged code version into an independent container based on the application container engine.

[0012] In one implementation, installing an open source application container engine and deploying the merged code version into an independent container based on the application container engine includes: Install the open source application container engine through a preset command line; Configure the key and add the generated public key to the version control tool; Install an open source automation server based on the version control tool; An open source Hypertext Transfer Protocol server and a reverse proxy server are installed, and the merged code version is deployed into an independent container based on the installed servers.

[0013] In a second aspect, the present invention provides a front-end collaborative development management and automated construction and deployment system, comprising: Version control tool module, used to select the corresponding version control tool according to the front-end collaborative development task; A format normalization processing module is used to perform unified normalization processing on the code format of the front-end collaborative development task based on the selected version control tool; A branch normalization processing module, used to perform branch normalization processing on the version iteration code of the development process of the front-end collaborative development task; The version deployment module is used to merge all code versions developed by developers according to user types and deploy the merged code versions.

[0014] In a third aspect, the present invention provides a terminal comprising: a processor and a memory, wherein the memory stores a front-end collaborative development management and automated construction and deployment program, and when the front-end collaborative development management and automated construction and deployment program is executed by the processor, it is used to implement the operation of the front-end collaborative development management and automated construction and deployment method as described in the first aspect.

[0015] In a fourth aspect, the present invention also provides a computer-readable storage medium, which stores a front-end collaborative development management and automated construction and deployment program. When the front-end collaborative development management and automated construction and deployment program is executed by a processor, it is used to implement the operation of the front-end collaborative development management and automated construction and deployment method as described in the first aspect.

[0016] The present invention adopts the above technical solution to achieve the following effects: The present invention selects the corresponding version control tool based on the front-end collaborative development task, and can standardize the code format of the front-end collaborative development task based on the selected version control tool. It also standardizes the branching of the version iteration code during the development process of the front-end collaborative development task. It can then merge all the code versions developed by developers based on user type and deploy the merged code versions. The present invention can effectively reduce code merging conflicts and improve the efficiency of build and deployment, thereby significantly improving development efficiency and product iteration speed. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the structures shown in these drawings without paying any creative work.

[0018] Figure 1 It is a flowchart of the front-end collaborative development management and automated construction and deployment method in the present invention.

[0019] Figure 2 It is the overall system flow chart of the present invention.

[0020] Figure 3 It is a functional principle diagram of a terminal in one implementation of the present invention.

[0021] The purpose, features and advantages of the present invention will be further described with reference to the accompanying drawings and in conjunction with the embodiments. DETAILED DESCRIPTION

[0022] In order to make the purpose, technical solutions and advantages of the present invention more clear and distinct, the present invention is further described in detail below with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention.

[0023] Exemplary Methods In today's internet industry, medium-to-large front-end projects often involve large teams of developers, frequently changing requirements, and the need for rapid iteration and continuous delivery. In these situations, incorrect management can lead to widespread code conflicts between versions, making manual builds and deployments time-consuming and labor-intensive, resulting in low development efficiency.

[0024] For front-end development project management, existing project management methods are developed for specific project types. Although this specific project management method can improve the management efficiency of a certain type of front-end development project, it cannot adapt to a variety of different front-end development projects, resulting in low compatibility. On the other hand, it adopts a general management method for management. This method cannot effectively reduce code merging conflicts, resulting in reduced development efficiency and product iteration speed.

[0025] In response to the above technical problems, an embodiment of the present invention provides a front-end collaborative development management and automated construction and deployment method, which includes: selecting a corresponding version control tool according to the front-end collaborative development task; standardizing the code format of the front-end collaborative development task based on the selected version control tool; standardizing the version iteration code of the development process of the front-end collaborative development task; merging all developed code versions of developers according to user type, and deploying the merged code version. The embodiment of the present invention can effectively reduce code merging conflicts, improve the efficiency of construction and deployment, and thus significantly improve development efficiency and product iteration speed.

[0026] like Figure 1 As shown, an embodiment of the present invention provides a front-end collaborative development management and automated construction and deployment method, including the following steps: Step S100: Select a corresponding version control tool according to the front-end collaborative development task.

[0027] In this embodiment, a reasonable collaborative management and automated construction and deployment method is provided, which can effectively reduce code merging conflicts, improve the efficiency of construction and deployment, and thus significantly improve development efficiency and product iteration speed.

[0028] In this embodiment, if Figure 2 As shown, the process of implementing the front-end collaborative development management and automated construction and deployment method mainly includes two parts: the development process part and the automated deployment part; wherein, in the development process part, tasks are first assigned based on demand analysis, and then based on the input text, branches are pulled from the main branch to local development, and after the corresponding code is submitted, a code version merge request is created and the code is reviewed, and then the required code can be merged; and in the automated deployment part, the software is first automatically built through Jenkins (an open source continuous integration and continuous delivery / deployment tool), and then after automatic code detection and automatic creation of the image, the front-end collaboratively developed software is automatically deployed.

[0029] Specifically, in one implementation of this embodiment, step S100 includes the following steps: Step S101 : selecting a cloud-based collaborative development platform that supports code hosting, continuous integration, continuous deployment, issue tracking, and code review as the version control tool according to the front-end collaborative development task.

[0030] In this embodiment, in the development process, after task allocation is performed based on demand analysis, the corresponding version control tool is selected based on the front-end collaborative development task. Specifically, the version control tool is selected as follows: First, Git (the core tool of a distributed version control system) is selected as the version control tool. To facilitate front-end collaborative development, this embodiment further selects GitLab, developed based on Git, as the cloud-based collaborative development platform. GitLab provides code hosting, continuous integration / continuous deployment (CI / CD), issue tracking, code review, and other features.

[0031] In this embodiment, in addition to selecting the above GitLab solution, you can also choose a version control tool based on the GitHub solution or a version control tool based on the PingCode solution; among them, GitHub is the world's largest open source community, supports Actions to achieve automated build / testing / deployment, and Copilot provides AI-assisted code review, and the Issue module has a complete problem tracking mechanism; PingCode covers the entire process from demand management to defect tracking, is deeply integrated with GitLab / GitHub, supports agile Kanban and code review workflows, and meets the requirements of information technology innovation.

[0032] like Figure 1 As shown, an embodiment of the present invention provides a front-end collaborative development management and automated construction and deployment method, including the following steps: Step S200 : performing unified and standardized processing on the code format of the front-end collaborative development task based on the selected version control tool.

[0033] In this embodiment, after selecting the GitLab tool according to the front-end collaborative development task, unified standardization processing is performed based on the GitLab tool using a unified development environment; this embodiment stipulates the development tool formatting rules for all developers in this unified development environment; through the unified development environment and defined development tool formatting rules, full-process code standardization management from local development to cloud collaboration can be achieved on the GitLab platform.

[0034] Specifically, in one implementation of this embodiment, step S200 includes the following steps: Step S201, setting development tool formatting rules for all developers; Step S202 : performing unified standardization processing on the code format of the front-end collaborative development task according to the formatting rules of the development tool to obtain a code with a unified format.

[0035] In this embodiment, in the process of unifying the development environment, development tool formatting rules are set for all developers, wherein the development tool formatting rules include: code indentation space number, code line break number, and code automation space rules.

[0036] As an example, a unified approach to code formatting can be to specify formatting rules for all developers' development tools, standardizing formatting rules (e.g., the number of spaces between code indentations, the number of words between lines, and automatic spacing in code). This prevents code conflicts caused by modifying someone else's code and changing the formatting of all code.

[0037] In the actual front-end collaborative development process, the GitLab-based front-end collaborative development code standardization implementation plan needs to integrate the engineering tool chain and version control process: 1. Formatting tool configuration: 1) Use Prettier for automatic formatting (supports JS / TS / CSS / HTML, etc.); 2) Define team rules (such as indentation 2 spaces, single quotes, etc.) through the .prettierrc file.

[0038] 2. Static checking tools: 1) ESLint detects JS / TS syntax errors and is used with the @typescript-eslint plugin; 2) Stylelint verifies CSS / Less / Sass style specifications.

[0039] In the version control process, mandatory checks are implemented through the pipeline to prevent code from being merged if it does not conform to the formatting rules. Specifically, a lint stage is defined in .gitlab-ci.yml to ensure that code that fails the check cannot be merged. In addition, all merge requests must pass code review and Squash Merge is enabled to keep the commit history clean.

[0040] To facilitate collaborative front-end development, you can use VSCode to configure a unified development environment and share editor behavior through VSCode's shared .vscode / settings.json file. Furthermore, you can set up front-end development guidelines in the GitLab Wiki and use the included code examples, tool configuration instructions, and solutions to common problems for operational guidance.

[0041] In this embodiment, by setting the development tool formatting rules for all developers, it is possible to prevent all code formats from changing due to modifying part of other people's code, thereby avoiding code conflicts.

[0042] like Figure 1 As shown, an embodiment of the present invention provides a front-end collaborative development management and automated construction and deployment method, including the following steps: Step S300 , performing branch normalization processing on the version iteration code of the development process of the front-end collaborative development task.

[0043] In this embodiment, after the code format of the front-end collaborative development task is uniformly standardized, the version iteration code of the development process of the front-end collaborative development task also needs to be branch standardized; the branch normalization means: in the process of iterating the code version, each version iteration pulls a new version branch based on the main branch.

[0044] Specifically, in one implementation of this embodiment, step S300 includes the following steps: Step S301, building a version iteration code branch architecture; Step S302, obtaining the main branch of the iterative code in the development process of the front-end collaborative development task; Step S303: When the code version corresponding to the main branch is updated, a new version branch is pulled based on the main branch, and the current code version is iterated in the pulled new version branch.

[0045] In this embodiment, GitLab's branch permission control + automated inspection ensures that the version iteration process complies with the standardized process.

[0046] Specifically, by building a version iteration code branch architecture and obtaining the main branch of the iterative code in the development process of the front-end collaborative development task, the version iteration code branch specification method is used to perform branch standardization on the version iteration code in the development process; among them, the version iteration code branch specification method is: each version iteration pulls a new version branch based on the main branch.

[0047] As an example, the version iteration code branch normalization process configured in GitLab is as follows: 1) Set branch protection rules: Only project maintainers are allowed to push to the master branch, and merging requires at least two approvals; for the dev branch, code review and CI must pass before merging.

[0048] 2) Implement branch strategy verification through .gitlab-ci.yml.

[0049] In this embodiment, branch normalization is performed on the version iteration code of the development process to ensure that the version iteration process complies with the standardized process and avoid version iteration confusion.

[0050] like Figure 1 As shown, an embodiment of the present invention provides a front-end collaborative development management and automated construction and deployment method, including the following steps: Step S400: Merge all code versions developed by developers according to user types, and deploy the merged code versions.

[0051] In this embodiment, after the version iteration code of the development process of the front-end collaborative development task is branched and normalized, the full life cycle management from code merging to secure deployment is realized through role authority separation and automated processes; when merging code versions, all code versions developed by developers are merged according to user type, and the merged code version is deployed.

[0052] Specifically, in one implementation of this embodiment, step S400 includes the following steps: Step S401: Based on the version merging operation tool, selectively copy specific code versions and submit them to the selected branch, merging all code versions developed by the current developer; Step S402: Install an open source application container engine, and deploy the merged code version into an independent container based on the application container engine.

[0053] In this embodiment, based on the version merging operation tool and utilizing the code merging specification method, specific code versions are selectively copied and submitted to the selected branch in sequence, and all code versions developed by the current developer are merged.

[0054] Among them, the standard method of code merging is: use git cherry-pick (version merge operation tool) to merge the code, only merging the code version developed by the current developer, and not performing large-scale version merging, thereby reducing the probability of code conflicts.

[0055] As an example, a complete solution for accurately merging developer code based on Git cherry-pick is: 1) Locate developer submission records: All developed code versions are filtered by author and then the commit hash list is extracted to arrange the target commits in chronological order to avoid missing dependencies.

[0056] 2) Execute selective merge strategy: For a single-branch merge operation, switch to the target branch and batch merge the specified commit directory.

[0057] For the cross-branch merge process, merge from the dev branch to the release branch and merge the latest 3 commits: ml-citation{ref="4" data="citationList"}.

[0058] 3) Conflict handling and verification: Conflict resolution is performed after manually resolving conflicts.

[0059] Change verification methods, check the integrity of merged content, and view file change statistics.

[0060] In this embodiment, after all code versions developed by developers are merged according to user types, an open source application container engine is installed, and the merged code versions are deployed into an independent container based on the application container engine.

[0061] As an example, in this embodiment, the merged code version is deployed into a separate container using Docker. The specific process is as follows: Deploy the server: Set up a Docker environment. Docker is an open source application container engine that allows developers to package applications and their dependencies into an independent container, enabling rapid deployment, isolated operation, and consistency across environments.

[0062] In one implementation of this embodiment, step S402 includes the following steps: Step S402a, installing the open source application container engine through a preset command line; Step S402b: configuring the key and adding the generated public key to the version control tool; Step S402c: installing an open source automation server based on the version control tool; Step S402d: Install an open source Hypertext Transfer Protocol server and a reverse proxy server, and deploy the merged code version into an independent container based on the installed servers.

[0063] In this embodiment, an open source application container engine is installed, and the merged code version is deployed into an independent container based on the application container engine. The specific solution is as follows: 1. Install Docker through the command line.

[0064] 2. Install Git, configure the key, and add the generated public key to gitLab.

[0065] 3. Install Jenkins. Jenkins is an open source automation server that helps development teams automate the building, testing, and deployment of software, thereby improving development efficiency, reducing human errors, and speeding up delivery.

[0066] 3.1. Connect to the Gitlab address library.

[0067] 3.2. Configure the node environment and select the node environment version.

[0068] 3.3. Configure build and deployment commands.

[0069] 4. Install Nginx, which is a high-performance open source HTTP server and reverse proxy server.

[0070] Nginx is ideal for serving static resources such as HTML, CSS, JavaScript, images, and fonts. It can quickly and efficiently process requests for static resources, reducing server response times. Nginx can act as a reverse proxy server, forwarding front-end requests to back-end services. This allows the front-end and back-end to be deployed independently, while Nginx provides unified request management. Nginx can also be configured as a load balancer, distributing requests to multiple back-end servers, thereby improving system availability and scalability. This is particularly useful for high-traffic front-end applications.

[0071] As an example, in an actual front-end collaborative development scenario, the following steps are included: S11, uses Git as the version control system; S12, uses GitLab or GitHub as a remote repository platform and supports CI / CD integration; S13, choose VS Code and HBuilder X as auxiliary tools; VS Code integrates the GitLens plug-in to enhance code history tracing capabilities; HBuilder X has built-in Git support to simplify basic operations; S14: Standardize the code based on code formatting rules and submit information using the Conventional Commits standard. S15, perform branch standardization through branch management strategy; S16 merges the code versions submitted by specific developers, submits them to the deployment pipeline through GitLab CI or Jenkins, and uses Webhook to trigger the container's seamless update.

[0072] This embodiment implements refined version control through GitHub and combines containerized deployment to ensure environmental consistency, effectively reducing code merging conflicts and improving build and deployment efficiency.

[0073] This embodiment achieves the following technical effects through the above technical solution: This embodiment, by selecting a corresponding version control tool, can standardize the code format of front-end collaborative development tasks based on the selected version control tool, and standardize the branching of version iteration code during the development process of front-end collaborative development tasks. This allows all code versions developed by developers to be merged based on user type and deployed. This embodiment can effectively reduce code merge conflicts and improve build and deployment efficiency, thereby significantly improving development efficiency and product iteration speed.

[0074] Exemplary devices Based on the above embodiments, the present invention further provides a front-end collaborative development management and automated construction and deployment system, including: Version control tool module, used to select the corresponding version control tool according to the front-end collaborative development task; A format normalization processing module is used to perform unified normalization processing on the code format of the front-end collaborative development task based on the selected version control tool; A branch normalization processing module, used to perform branch normalization processing on the version iteration code of the development process of the front-end collaborative development task; The version deployment module is used to merge all code versions developed by developers according to user types and deploy the merged code versions.

[0075] This embodiment achieves the following technical effects through the above technical solution: This embodiment, by selecting a corresponding version control tool, can standardize the code format of front-end collaborative development tasks based on the selected version control tool, and standardize the branching of version iteration code during the development process of front-end collaborative development tasks. This allows all code versions developed by developers to be merged based on user type and deployed. This embodiment can effectively reduce code merge conflicts and improve build and deployment efficiency, thereby significantly improving development efficiency and product iteration speed.

[0076] Based on the above embodiment, the present invention further provides a terminal, whose principle block diagram can be shown as follows: Figure 3 shown.

[0077] The terminal includes: a processor, memory, interface, display screen and communication module connected via a system bus; wherein the processor of the terminal is used to provide computing and control capabilities; the memory of the terminal includes a computer-readable storage medium and an internal memory; the computer-readable storage medium stores an operating system and a computer program; the internal memory provides an environment for the operation of the operating system and computer program in the computer-readable storage medium; the interface is used to connect to external devices; the display screen is used to display corresponding information; and the communication module is used to communicate with a cloud server or other devices.

[0078] When executed by a processor, the computer program is used to implement front-end collaborative development management and automate the operations of the construction and deployment method.

[0079] It will be understood by those skilled in the art that Figure 3 The principle block diagram shown in the figure is only a block diagram of a partial structure related to the solution of the present invention, and does not constitute a limitation on the terminal to which the solution of the present invention is applied. The specific terminal may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0080] In one embodiment, a terminal is provided, which includes: a processor and a memory, the memory storing a front-end collaborative development management and automated construction and deployment program, and the front-end collaborative development management and automated construction and deployment program is used to implement the operations of the above-mentioned front-end collaborative development management and automated construction and deployment method when executed by the processor.

[0081] In one embodiment, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores a front-end collaborative development management and automated construction and deployment program, which, when executed by a processor, is used to implement the operations of the above-mentioned front-end collaborative development management and automated construction and deployment method.

[0082] Those skilled in the art will appreciate that all or part of the processes in the above-described method embodiments can be implemented by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile storage medium. When executed, the computer program can include the processes in the above-described method embodiments. Any reference to memory, storage, database, or other media used in the various embodiments provided herein may include both non-volatile and volatile memory.

[0083] In summary, the present invention provides a front-end collaborative development management and automated build and deployment method, system, terminal, and storage medium, including: selecting a corresponding version control tool based on the front-end collaborative development task; performing unified standardization processing on the code format of the front-end collaborative development task based on the selected version control tool; performing branch standardization processing on the version iteration code of the development process of the front-end collaborative development task; merging all developed code versions of developers according to user type, and deploying the merged code version. The present invention can effectively reduce code merging conflicts, improve the efficiency of build and deployment, and thus significantly improve development efficiency and product iteration speed.

[0084] It should be understood that the application of the present invention is not limited to the above examples. For those skilled in the art, improvements or changes can be made based on the above description. All these improvements and changes should fall within the scope of protection of the claims attached to the present invention.

Claims

1. A front-end collaborative development management and automated construction and deployment method, characterized in that: include: Select the corresponding version control tool based on the front-end collaborative development task; Standardize the code format of the front-end collaborative development task based on the selected version control tool; Performing branch normalization processing on the version iteration code of the development process of the front-end collaborative development task; Merge all code versions developed by developers according to user type and deploy the merged code versions.

2. The front-end collaborative development management and automated construction and deployment method according to claim 1 is characterized in that: The selection of the corresponding version control tool according to the front-end collaborative development task includes: According to the front-end collaborative development task, a cloud-based collaborative development platform that supports code hosting, continuous integration, continuous deployment, issue tracking, and code review is selected as the version control tool.

3. The front-end collaborative development management and automated construction and deployment method according to claim 1 is characterized in that: The selected version control tool performs unified and standardized processing on the code format of the front-end collaborative development task, including: Set development tool formatting rules for all developers; According to the formatting rules of the development tool, the code format of the front-end collaborative development task is uniformly standardized to obtain a code with a uniform format.

4. The front-end collaborative development management and automated construction and deployment method according to claim 3 is characterized in that: The development tool formatting rules include: one or a combination of code indentation space number, code line break word number, and code automation space rules.

5. The front-end collaborative development management and automated construction and deployment method according to claim 1 is characterized in that: The branch normalization processing of the version iteration code of the development process of the front-end collaborative development task includes: Build version iteration code branch architecture; Obtaining the main branch of the iterative code in the development process of the front-end collaborative development task; When the code version corresponding to the main branch is updated, a new version branch is pulled based on the main branch, and the current code version is iterated in the pulled new version branch.

6. The front-end collaborative development management and automated construction and deployment method according to claim 1 is characterized in that: The merging of all code versions developed by developers according to user type and deploying the merged code versions includes: Based on the version merge operation tool, selectively copy specific code versions and submit them to the selected branch in turn, and merge all code versions developed by the current developer; Install an open source application container engine and deploy the merged code version into an independent container based on the application container engine.

7. The front-end collaborative development management and automated construction and deployment method according to claim 6 is characterized in that: The process of installing an open source application container engine and deploying the merged code version into an independent container based on the application container engine includes: Install the open source application container engine through a preset command line; Configure the key and add the generated public key to the version control tool; Install an open source automation server based on the version control tool; An open source Hypertext Transfer Protocol server and a reverse proxy server are installed, and the merged code version is deployed into an independent container based on the installed servers.

8. A front-end collaborative development management and automated construction and deployment system, characterized by: include: Version control tool module, used to select the corresponding version control tool according to the front-end collaborative development task; A format normalization processing module is used to perform unified normalization processing on the code format of the front-end collaborative development task based on the selected version control tool; A branch normalization processing module, used to perform branch normalization processing on the version iteration code of the development process of the front-end collaborative development task; The version deployment module is used to merge all code versions developed by developers according to user types and deploy the merged code versions.

9. A terminal, characterized in that: include: A processor and a memory, wherein the memory stores a front-end collaborative development management and automated construction and deployment program, and when the front-end collaborative development management and automated construction and deployment program is executed by the processor, it is used to implement the operation of the front-end collaborative development management and automated construction and deployment method as described in any one of claims 1-7.

10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a front-end collaborative development management and automated construction and deployment program, which, when executed by a processor, is used to implement the operation of the front-end collaborative development management and automated construction and deployment method as described in any one of claims 1-7.

Images