Mobile terminal automatic deployment process based on devops

Through the devops-based mobile automatic deployment process, the problem that the App deployment process and project management in the existing technology are not related, and automated component dependency configuration and deployment are realized, error rate and communication costs are reduced, and deployment efficiency is improved. and security.

CN118963783APending Publication Date: 2024-11-15ZHONGQI LIANXIN (BEIJING) TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411007865.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-25
Publication Date
2024-11-15

AI Technical Summary

Technical Problem

The existing mobile app deployment process is based on the engineering dimension and cannot be effectively associated with the project management process, resulting in high technical requirements, high error rate, high communication cost, and multi-department maintenance results in high configuration file error rate. Developers need to manually modify component dependencies. Relationships, safety risks.

Method used

Adopt the mobile terminal automatic deployment process based on devops. Through the event triggering mechanism, binary packages and installation packages are automatically generated based on component dependencies, reducing communication costs, and the platform automatically generates configuration files to ensure the correct component order and achieve full automated deployment.

Benefits of technology

It reduces the communication and configuration file management costs of developers, reduces the probability of errors, ensures the correct component dependencies, realizes an automated App deployment process, and improves deployment efficiency and security.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118963783A_ABST
    Figure CN118963783A_ABST
Patent Text Reader

Abstract

The invention discloses a mobile terminal automatic deployment process based on devops, which comprises the following steps that: A, 10 minutes after an event is sent, if a submitted code warehouse has components, the warehouse acquires the components of a binary package required to be generated according to the dependency relationship of the components, then acquires the version number of the binary package of the components according to a submitted branch configuration center, and stores the version number of the binary package of the components in the submitted code warehouse; the platform automatically generates binary packages of versions corresponding to the components in sequence; and B, if the warehouse submitting the codes does not have components, the warehouse obtains a configuration file corresponding to the online window from a configuration file management center. On the basis of project dimension design, mutual noninterference between development and between project groups can be achieved, communication cost is reduced, configuration file management is not needed for development, and configuration file exchange is not needed for different departments. The binary file of the dependent component and the installation package of each environment of the app can be automatically generated according to the dependency relationship configuration between the components.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of App deployment, and in particular to a devops-based mobile terminal automatic deployment process. Background Art

[0002] At present, the existing mobile App deployment process is basically based on the engineering dimension of package deployment. For example, it is deployed based on a certain App in a certain environment. It cannot be effectively combined with the online project and the online window, and it is necessary to develop configuration files for maintaining the dependencies of components. There are problems such as high technical requirements for technical personnel, high error rate, and high communication costs between developers. Moreover, as the number of developers increases, more and more businesses are involved, and multiple departments jointly maintain an App, the communication and management costs are getting higher and higher. The shortcomings of the existing solutions are: 1. Basically, the automatic deployment process is based on Jenkins and monitoring code submission records, and automatically pushes the given package platform 1. The automatic package deployment achieved by this method cannot be associated with the project management process and is only a package deployment tool; 2. When deploying the mobile App, the developer needs to manually modify the component dependencies in the configuration file (component dependency file). Manual configuration will increase the error rate; 3. Multiple groups jointly maintaining a configuration file will increase communication costs and increase the error rate; 4. Package deployment is not related to the project. The correctness of the package depends on the correctness of the configuration. The developers of Group A can modify the component configuration of Group B, which is very unsafe; 5. If there are multiple components in the project, there may be order requirements for the components to generate binary packages such as ar packages or frameworks, which will increase the requirements for development. Summary of the invention

[0003] The purpose of the present invention is to provide a devops-based mobile terminal automatic deployment process to solve the problems raised in the above background technology.

[0004] To achieve the above purpose, the present invention provides the following technical solution: a mobile terminal automatic deployment process based on devops, the process is as follows:

[0005] A. 10 minutes after the event is sent, if the submitted code repository has components, the repository obtains the components of the binary package that needs to be generated according to the component dependencies, and then obtains the version number of the component binary package from the configuration center according to the submitted branch, and the platform automatically generates binary packages of the corresponding versions of the components in turn;

[0006] B. If the repository where the code is submitted does not have a component, the repository goes to the configuration file management center to obtain the configuration file for the corresponding online window;

[0007] C. Automatically generate the installation package for the corresponding environment.

[0008] Preferably, the event threshold can be set. For example, the code of components 1 and 2 is submitted to the r_0524 branch. After the code is submitted, the submission information will be pushed to the packaging center. The packaging center executes the process 10 minutes after the last submission. The repositories 1 and 2 where the code is submitted are both components. According to the submission branch of components 1 and 2 is r_0524, the online window is 0524, the version number of the online window of component 1 0524 is m, and the version number of component 2 is n. Binary packages with version numbers m and n of components 1 and 2 are generated in sequence.

[0009] Preferably, after the binary package is generated, the App installation package is generated. The configuration center is used to obtain the 0524-platform type configuration file to generate the App installation package. Due to the dependencies between components, if the order in which the components are released in binary packages is incorrect, the package may fail to be released. For example, if component 2 depends on component 1, if the binary package of component 2 is released first, the package may fail to be released because the dependent component 1 has not yet updated its component package.

[0010] Preferably, the order of generating component binary packages is as follows: according to the components that need to be packaged, the dependencies between the components are obtained, and the components are graded according to the dependencies, such as: the components that need to be packaged are A, B, C, and D, A depends on B and D, B depends on C and D, and the initial levels of A, B, C, and D are all 1. Recursively traverse the dependency tree, A depends on B and D, the levels of B and D become 2, B depends on C and D, the levels of C and D are 3, and there is no dependency under C and D, then the A component is terminated. Because the levels of the B, C, and D components are all lower than the levels of the B, C, and D components after traversal, recursive traversal is not performed, and the final component levels are A: 1, B: 2, C: 3, and D: 3. Then the order of packaging is to first package C and D, then B after C and D are packaged, and finally A. The packages are packaged in reverse order of levels. If the levels are the same, they are packaged together.

[0011] Preferably, for example, the online window of 0524 has project A input components 1, 2, 3, and project B input projects 3, 4. 1. After the entry of project A and project B is completed, the entry information 0524-A-1, 2, 3 and 0524-B-3, 4 will be pushed to the configuration center; 2. The configuration center obtains the version number m according to 0524-A, and obtains the version number n according to 0524-B; 3. Generate configuration files A: m, B: n; 4. Name the configuration file 0524-platform type and store it in the configuration center.

[0012] Preferably, if the code of the specified branch is submitted, gitlab will push the code submission information to the automatic deployment service. The automatic deployment service will generate binary files such as ar or framework of the specified version according to the submitted components and branches. In order to solve the problem that a project may involve multiple components, automatic deployment cannot be performed after submitting one component, and automatic deployment must be performed after all components are submitted, an event-triggered threshold is designed. For example, a project involves components A and B, and the threshold is set to 10 minutes. Automatic deployment is performed 10 minutes after component A submits the code. If the code of component B is submitted 2 minutes later, it becomes executed 10 minutes after component B is submitted. By analogy, automatic deployment will be performed 10 minutes after the last submission. At this time, components A and B and the App that needs to be generated need to be deployed.

[0013] Compared with the prior art, the present invention has the following beneficial effects:

[0014] The present invention is designed based on the project dimension, and can achieve non-interference between developers and between project groups, thereby reducing communication costs. Developers do not need to manage configuration files, and different departments do not need to communicate on how to modify configuration files. Binary files of dependent components and installation packages of various app environments can be automatically generated according to the dependency relationship between components, and the entire package delivery process is fully automated. Developers do not need to modify configuration files, and the platform automatically modifies configuration files according to projects entered by developers, thereby reducing the probability of errors. After the project entry is completed, the platform automatically generates or modifies the configuration file of the project's online window and saves it to the configuration center. At the same time, a threshold for triggering automatic package delivery after submission is set to prevent the problem that after component A is submitted, component B, which A depends on, has not been submitted, resulting in the triggering of the binary generation task. In addition, as long as there is code submission in the same online window, the package delivery task will be executed after a certain event. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 It is a service call relationship diagram of the present invention;

[0016] Figure 2 Generate a configuration file flow chart for the present invention;

[0017] Figure 3 This is a flow chart of the automatic deployment service of the present invention. DETAILED DESCRIPTION

[0018] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0019] See also Figure 1-Figure 3 , the mobile terminal automatic deployment process based on devops is as follows:

[0020] A. 10 minutes after the event is sent, if the submitted code repository has components, the repository obtains the components of the binary package that needs to be generated according to the component dependencies, and then obtains the version number of the component binary package from the configuration center according to the submitted branch, and the platform automatically generates binary packages of the corresponding versions of the components in turn;

[0021] B. If the repository where the code is submitted does not have a component, the repository goes to the configuration file management center to obtain the configuration file for the corresponding online window;

[0022] C. Automatically generate the installation package for the corresponding environment.

[0023] The event threshold can be set. For example, the code of components 1 and 2 is submitted to the r_0524 branch. After the code is submitted, the submission information will be pushed to the packaging center. The packaging center will execute the process 10 minutes after the last submission (the threshold is set to 10 minutes). The repositories 1 and 2 where the code is submitted are both components. According to the submission branch of components 1 and 2, which is r_0524 and the online window is 0524, the version number of the 0524 online window of component 1 is m, and the version number of component 2 is n. Binary packages with version numbers m and n of components 1 and 2 are generated in sequence.

[0024] After the binary package is generated, start generating the App installation package. Go to the configuration center to obtain the 0524-platform type configuration file and generate the App installation package. Due to the dependencies between components, if the order of binary packages of components is incorrect, the package generation may fail. For example, if component 2 depends on component 1, if the binary package of component 2 is generated first, the package generation may fail because the dependent component 1 has not updated the component package.

[0025] The order of generating component binary packages is as follows: according to the components that need to be packaged, the dependencies between the components are obtained, and the components are graded according to the dependencies. For example, the components that need to be packaged are A, B, C, and D. A depends on B and D, and B depends on C and D. The initial levels of A, B, C, and D are all 1. Recursively traverse the dependency tree. A depends on B and D, and the levels of B and D become 2. B depends on C and D, and the levels of C and D are 3. If there is no dependency under C and D, the A component is terminated. Because the levels of B, C, and D components are all lower than the levels of B, C, and D after traversal, recursive traversal is not performed. The final component levels are A: 1, B: 2, C: 3, and D: 3. Then the package is released in the order of C and D first, and then B after C and D are released, and finally A. The packages are released in reverse order of level. If the levels are the same, they are released together.

[0026] For example, the online window of 0524 has project A entering components 1, 2, and 3, and project B entering projects 3 and 4. 1. After project A and project B are entered, the entry information 0524-A-1, 2, 3 and 0524-B-3, 4 will be pushed to the configuration center; 2. The configuration center obtains version number m based on 0524-A and version number n based on 0524-B; 3. Generate configuration files A: m, B: n; 4. Name the configuration file 0524-Platform Type and store it in the configuration center.

[0027] If the code of the specified branch is submitted, gitlab will push the code submission information to the automatic deployment service. The automatic deployment service will generate binary files such as ar or framework of the specified version according to the submitted components and branches. In order to solve the problem that a project may involve multiple components, automatic deployment cannot be performed after submitting one component, and automatic deployment must be performed after all components are submitted, an event-triggered threshold is designed. For example, a project involves components A and B, and the threshold is set to 10 minutes. Automatic deployment is performed 10 minutes after component A submits the code. If the code of component B is submitted 2 minutes later, it becomes executed 10 minutes after component B is submitted. By analogy, automatic deployment will be performed 10 minutes after the last submission. At this time, components A and B and the App that needs to be generated need to be deployed.

[0028] Although embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes, modifications, substitutions and variations may be made to the embodiments without departing from the principles and spirit of the present invention, and that the scope of the present invention is defined by the appended claims and their equivalents.

Claims

1. The automatic deployment process of mobile terminals based on devops is characterized by: The process is as follows: A. 10 minutes after the event is sent, if the submitted code repository has components, the repository obtains the components of the binary package that needs to be generated according to the component dependencies, and then obtains the version number of the component binary package from the configuration center according to the submitted branch, and the platform automatically generates binary packages of the corresponding versions of the components in turn; B. If the repository where the code is submitted does not have a component, the repository goes to the configuration file management center to obtain the configuration file for the corresponding online window; C. Automatically generate the installation package for the corresponding environment.

2. The mobile terminal automatic deployment process based on devops according to claim 1 is characterized in that: The event threshold can be set. For example, the code of components 1 and 2 is submitted to the r_0524 branch. After the code is submitted, the submission information will be pushed to the packaging center. The packaging center executes the process 10 minutes after the last submission. The repositories 1 and 2 where the code is submitted are both components. According to the submission branch of components 1 and 2, which is r_0524 and the online window is 0524, the version number of the online window of component 1 0524 is m, and the version number of component 2 is n. Binary packages with version numbers m and n of components 1 and 2 are generated in sequence.

3. The devops-based mobile terminal automatic deployment process according to claim 2 is characterized in that: After the binary package is generated, start generating the App installation package. Go to the configuration center to obtain the 0524-platform type configuration file and generate the App installation package. Due to the dependencies between components, if the order of binary packages of components is incorrect, the package generation may fail. For example, if component 2 depends on component 1, if the binary package of component 2 is generated first, the package generation may fail because the dependent component 1 has not updated the component package.

4. The mobile terminal automatic deployment process based on devops according to claim 3 is characterized in that: The order of generating component binary packages is as follows: according to the components that need to be packaged, the dependencies between the components are obtained, and the components are graded according to the dependencies. For example, the components that need to be packaged are A, B, C, and D. A depends on B and D, and B depends on C and D. The initial levels of A, B, C, and D are all 1. Recursively traverse the dependency tree. A depends on B and D, and the levels of B and D become 2. B depends on C and D, and the levels of C and D are 3. If there is no dependency under C and D, the A component is terminated. Because the levels of B, C, and D components are all lower than the levels of B, C, and D after traversal, recursive traversal is not performed. The final component levels are A: 1, B: 2, C: 3, and D:

3. Then the package is released in the order of C and D first, and then B after C and D are released, and finally A. The packages are released in reverse order of level. If the levels are the same, they are released together.

5. The mobile terminal automatic deployment process based on devops according to claim 3 is characterized in that: For example, the online window of 0524 has project A entering components 1, 2, and 3, and project B entering components 3 and 4.

1. After project A and project B are entered, the entry information 0524-A-1, 2, 3 and 0524-B-3, 4 will be pushed to the configuration center; 2. The configuration center obtains version number m based on 0524-A and version number n based on 0524-B; 3. Generate configuration files A:m, B:n; 4. Store the configuration file 0524-Platform Type Naming in the configuration center.

6. The mobile terminal automatic deployment process based on devops according to claim 5 is characterized in that: If the code of the specified branch is submitted, gitlab will push the code submission information to the automatic deployment service. The automatic deployment service will generate binary files such as ar or framework of the specified version according to the submitted components and branches. In order to solve the problem that a project may involve multiple components, automatic deployment cannot be performed after submitting one component, and automatic deployment must be performed after all components are submitted, an event-triggered threshold is designed. For example, a project involves components A and B, and the threshold is set to 10 minutes. Automatic deployment is performed 10 minutes after component A submits the code. If the code of component B is submitted 2 minutes later, it becomes executed 10 minutes after component B is submitted. By analogy, automatic deployment will be performed 10 minutes after the last submission. At this time, components A and B and the App that needs to be generated need to be deployed.