Mobile application construction method and system based on component version rolling management

Through the combination of CICD platform and Ansible scripts, the high communication cost and difficulty in automation of component version number management in mobile application development are solved, and the automated management and compilation and packaging of component version number are realized, and development efficiency and stability are improved.

CN119088442APending Publication Date: 2024-12-06CLOUDCHAIN GRP CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411153458.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-21
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

In mobile application development, component version number management is problematic of high manual communication costs, low efficiency, easy to miss or make mistakes when collaborating with multiple teams, and the existing technology cannot realize automated component version number management and compilation and packaging.

Method used

Get the default information of components and predefined component version number information through the CICD platform, regenerate configuration files using Ansible scripts, and manage and update component version numbers on the cloud platform to realize automated management and compilation and packaging of component version numbers.

Benefits of technology

It reduces the cost of manual communication and operation frequency, ensures the stability and security of component version management, improves the efficiency of component version management, and realizes the combination of automated management of component version numbers and packaging and compilation.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119088442A_ABST
    Figure CN119088442A_ABST
Patent Text Reader

Abstract

The invention provides a mobile application building method and system based on component version rolling management, and the method comprises the steps: obtaining default component information and component version number information through a CICD platform in an initialization stage of mobile application building; at each edition issuing time, the CICD platform obtains the unique identifier of the mobile application and associated data of the component edition number information based on the edition issuing time; for a configuration file generation task, the CICD platform obtains a current configuration file by using an Ansible script, regenerates a configuration file of the version issuing time, covers the configuration file and uploads the configuration file to the cloud platform; in each mobile application package output process, obtaining a configuration file of the version issuing time from the cloud platform to obtain an online application package of the version issuing time; and after the mobile application is online each time, the CICD platform updates the default component information based on the component version number information corresponding to the version issuing time. According to the method, the manual communication cost can be reduced, and the steps of rolling management of the component version number and compiling and packaging of the mobile application are combined.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of mobile application development, and in particular to a mobile application construction method and system based on component version rolling management. Background Art

[0002] In the Android system, gradle (an open source tool for automated project construction) is generally used to compile and package applications. The component description information is written in gradle.properties. As shown in the following figure, oa is the component name and the version number is 2.2.0.

[0003] In the iOS system, Xcode is generally used for compilation and packaging. The component description information is uninstalled in the Podfile. YLCommonUI is the component name, and the version number is represented in a format similar to "branch=>master". The arrow may point to a branch name or a gitlab tag version number.

[0004] Since mobile applications contain many components, they are actually developed in multiple groups. Different teams may have overlapping components, and each team is uncertain about which components to design before development. Therefore, it involves frequent configuration files and component version number management. Currently, mobile terminal componentization is a common problem. It is a headache for multiple teams to communicate and define component version information related to the release of this application.

[0005] In the prior art, the problem is mainly solved by having multiple people jointly maintain a configuration file, or by frequently communicating within or across teams to directly modify the configuration file content in the code and use it directly during packaging to solve the problem of keeping the version information of components related to application release consistent.

[0006] The problems of the existing technology include: (1) high cost and low efficiency of manual communication. (2) Manual modification of component version numbers can easily lead to omission or error of component version numbers. (3) Each time a mobile application is released and packaged, the component version number used is based on the code definition submitted by the developer, rather than automatically generated, which may lead to configuration errors.

[0007] The technical problems to be overcome by the present invention include:

[0008] (1) How can multiple development teams involved in component development unify component version numbers?

[0009] (2) How to avoid frequent modifications of communication configuration files within or across teams.

[0010] (3) When developing new components, how to quickly synchronize component version numbers.

[0011] (4) How to automatically modify the component version number of the configuration file when compiling and packaging a mobile application.

[0012] (5) How to automatically update the default component version number after the mobile application is released. Summary of the invention

[0013] In view of this, an embodiment of the present invention provides a method and system for building a mobile application based on component version rolling management to eliminate or improve one or more defects existing in the prior art.

[0014] One aspect of the present invention provides a method for building a mobile application based on component version rolling management, the method comprising the following steps: in the initialization stage of mobile application creation, the CICD platform obtains default component information of components contained in the mobile application predefined by the developer and predefined component version number information based on subsequent release time, the default component information includes the associated mobile application unique identifier and the current version number, the component version number information includes the component version number information involved in the modification at each release time and the default component version number information; at each release time, the CICD platform obtains the associated data of the mobile application unique identifier and the component version number information based on the release time; whenever the CICD platform receives a configuration file generation task created by the developer, the CICD platform uses the Ansible script to generate the configuration file from the built mobile application. The current configuration file is obtained from the mobile application, and the configuration file for this release time is regenerated according to the pre-defined component version number information based on the current release time and the default component information. The regenerated configuration file overwrites the previous configuration file, and the regenerated configuration file is uploaded to the cloud platform for managing configuration files, so that the configuration file for this release time can be obtained from the cloud platform during local development and mobile application packaging. In each mobile application packaging process, the configuration file for this release time is obtained from the cloud platform, and based on the obtained configuration file, the associated mobile application unique identifier and the associated data, pipeline compilation and packaging are performed to obtain the online application package for this release time; after each mobile application is launched, the CICD platform updates the default component information based on the component version number information corresponding to the current release time.

[0015] In some embodiments of the present invention, the default component information also includes basic component description information, and the basic component description information includes multiple ones of component name, component version number, component function description, author information, and support information; the method also includes: during the process of local development by developers, obtaining the configuration file of this release time from the cloud platform.

[0016] In some embodiments of the present invention, the step of the CICD platform using the Ansible script to obtain the current configuration file from the built mobile application includes: the CICD platform uses the Ansible script to clone the code of the built mobile application, and finds the current configuration file in the cloned code.

[0017] In some embodiments of the present invention, the step of regenerating the configuration file for this release time according to the predefined component version number information based on this release time and the default component information includes: on the basis of the acquired current configuration file, modifying the component version number information contained in the current configuration file according to the predefined component version number information based on this release time, and regenerating the configuration file for this release time according to the records of the default component information for components that are not involved in modification.

[0018] In some embodiments of the present invention, the cloud platform for managing configuration files includes any one of gitlab, GitHub, Bitbucket, Azure DevOps and Gitea platforms.

[0019] In some embodiments of the present invention, the step of pipeline compiling and packaging based on the acquired configuration file, the associated mobile application unique identifier and the associated data includes: in the process of mobile application packaging, triggering the compilation and packaging task and obtaining mobile application information, cloning the code through the mobile application information, replacing the original configuration file included in the mobile application code with the acquired configuration file through the associated data and the associated mobile application unique identifier, and compiling and packaging the replaced mobile application code.

[0020] In some embodiments of the present invention, the compilation and packaging tasks in the process of mobile application packaging are implemented by Xcode tools or gradle tools.

[0021] Another aspect of the present invention provides a mobile application construction system based on component version rolling management, the system comprising a processor, a memory, and a computer program / instructions stored in the memory, the processor being used to execute the computer program / instructions, and when the computer program / instructions are executed, the system implements the steps of the method described in any one of the above embodiments.

[0022] Another aspect of the present invention provides a computer-readable storage medium having a computer program / instruction stored thereon, which implements the steps of the method described in any one of the above embodiments when the computer program / instruction is executed by a processor.

[0023] Another aspect of the present invention provides a computer program product, comprising a computer program / instruction, which implements the steps of the method described in any one of the above embodiments when executed by a processor.

[0024] The mobile application construction method and system based on component version rolling management proposed in the present invention can reduce the manual communication cost in the mobile application construction process, reduce manual operations, ensure the stability and security of mobile application construction, realize the automation of component version management, and is not prone to errors and omissions. The efficiency of component version management is significantly higher than that of manual work. The method and system proposed in the present invention can realize efficient component version number rolling management and combine it with packaging compilation in the process of multiple people and multiple teams collaborating to build mobile applications.

[0025] Additional advantages, purposes, and features of the present invention will be described in part in the following description, and will become apparent to those skilled in the art after studying the following, or may be learned from the practice of the present invention. The purposes and other advantages of the present invention may be achieved and obtained by the structures specifically indicated in the specification and the accompanying drawings.

[0026] Those skilled in the art will appreciate that the objectives and advantages that can be achieved with the present invention are not limited to the above specific description, and the above and other objectives that can be achieved by the present invention will be more clearly understood from the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] The drawings described herein are used to provide a further understanding of the present invention, constitute a part of the present application, and do not constitute a limitation of the present invention. In the drawings:

[0028] Figure 1 The present invention is a flowchart of a method for constructing a mobile application based on component version rolling management in one embodiment of the present invention.

[0029] Figure 2 This is a flow chart of a method for building a mobile application based on component version rolling management in another embodiment of the present invention. DETAILED DESCRIPTION

[0030] In order to make the purpose, technical solution and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the embodiments and the accompanying drawings. Here, the illustrative embodiments of the present invention and their descriptions are used to explain the present invention, but are not intended to limit the present invention.

[0031] It should also be noted that, in order to avoid obscuring the present invention due to unnecessary details, only structures and / or processing steps closely related to the solutions according to the present invention are shown in the accompanying drawings, while other details that are not closely related to the present invention are omitted.

[0032] It should be emphasized that the term “include / comprises” when used herein refers to the presence of features, elements, steps or components, but does not exclude the presence or addition of one or more other features, elements, steps or components.

[0033] It should also be noted that, unless otherwise specified, the term “connection” herein may refer not only to a direct connection but also to an indirect connection with an intermediate.

[0034] Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. In the accompanying drawings, the same reference numerals represent the same or similar components, or the same or similar steps.

[0035] In order to overcome the problems existing in the mobile application construction method based on the existing component version management, the present invention proposes a mobile application construction method and system based on component version rolling management, which manages the version information of multiple components contained in the mobile application, thereby realizing a more automated mobile application construction. Among them, the mobile application (or can be called the main project) includes Android applications and IOS applications. The main projects of Android applications and IOS applications generally extract some common component codes into an independent project, that is, components. Android components are generally AAR packages stored in private service warehouses, and IOS components are generally stored in gitlab code warehouses in source code. The components of mobile applications can be more or less, up to dozens, and each component has a version number, such as the version number is 1.0.0. Each time the main project is packaged, the component version number will be upgraded, which is the same as the mobile application releases a new version and also upgrades the version. In software development, a component refers to an independent, reusable software unit with specific functions and interfaces. The component version refers to the version number of the component. During the component upgrade process, the component version number will be upgraded, and the version number is used to distinguish components of different versions.

[0036] In the process of building a mobile application based on the method proposed in the present invention, first, the developer predefines which components a mobile application has, what the current version number of each component is (the default version number), and then predefines the component version numbers of subsequent release times (in layman's terms, the component version numbers of all subsequent releases are defined in advance, and used directly according to the release time during compilation and packaging).

[0037] Next, obtain the component version number information and default component version number information involved in this release (the default component version number information does not include the version involved in the modification, the modified version number information + the default version number information = the full version number information), and then use the Ansible script to clone the mobile application code, find the configuration file and regenerate it, and finally upload the newly generated configuration file to gitlab.

[0038] Among them, Ansible is a Python-based automated operation and maintenance tool for configuration management, application deployment and cloud orchestration. Gitlab is an open source, web-based Git repository management software. The present invention is not limited to this, and using gitlab to store configuration files is only an example, and platforms such as GitHub, Bitbucket, Azure DevOps or Gitea can also be used.

[0039] During local development, developers can obtain the latest configuration files from platforms such as gitlab at any time for development and compile and test locally. When testing or compiling and packaging online, in addition to cloning the application code, you also need to obtain new configuration files, then overwrite the old files with the new files, and finally compile and package.

[0040] After the mobile application version is launched, the CICD platform updates the default component information based on the component version number information corresponding to the release time, that is, in the code merge phase, the component version number information involved in the release time is updated to the default component version number. CICD is the abbreviation of continuous integration (CI) and continuous deployment (CD), and sometimes it can also include the concept of continuous delivery (CD).

[0041] Figure 1 The flowchart of the method for building a mobile application based on component version rolling management in one embodiment of the present invention is as follows:

[0042] Step S110: During the initialization phase of mobile application creation, the CICD platform obtains the default component information of the components included in the mobile application predefined by the developer and the predefined component version number information based on the subsequent release time, wherein the default component information includes the associated mobile application unique identifier and the current version number, and the component version number information includes the component version number information modified at each release time and the default component version number information.

[0043] In the specific implementation process, for a specific release time, the component version number information involved in the modification refers to the component version number of the component version included in the mobile application that is modified at this release time, and the default version number refers to the component version number that does not involve the component version modification at this release time, that is, the original default version is recorded, and the default component version number can be read from the default component information, and the default component information will update the component version number after each mobile application version is launched. / / In another embodiment of the present invention, it can be data initialized for one year each time, which can be freely scheduled according to the release frequency, and the number of components based on the release time and the number of default components are completely consistent.

[0044] In some embodiments of the present invention, the default component information further includes basic component description information, and the basic component description information includes multiple of component name, component version number, component function description, author information, and support information.

[0045] Step S120: At each release time, the CICD platform obtains the associated data of the mobile application unique identifier and the component version number information based on the release time.

[0046] In the specific implementation process, the pre-defined component version number information is the full amount of data. In the process of mobile application version release, we should try to avoid releasing all components. Therefore, developers are required to associate the mobile application with the component version number information involved in this release time. This is equivalent to telling the CICD platform to associate the components I use. Developers do not need to communicate with other members. When releasing, they only need to release the modified component version number, and there is no need to release the full component version number.

[0047] Step S130: Whenever the CICD platform receives a configuration file generation task created by a developer, the CICD platform uses the Ansible script to obtain the current configuration file from the built mobile application, and regenerates the configuration file for this release time according to the pre-defined component version number information based on this release time and the default component information. The regenerated configuration file overwrites the previous configuration file, and uploads the regenerated configuration file to the cloud platform for managing configuration files, so that the configuration file for this release time can be obtained from the cloud platform during local development and mobile application packaging.

[0048] Step S140: During each mobile application release process, a configuration file for this release time is obtained from the cloud platform, and pipeline compilation and packaging is performed based on the obtained configuration file, the associated mobile application unique identifier, and the associated data to obtain an online application package for this release time.

[0049] Step S150: After each mobile application is launched, the CICD platform updates the default component information based on the component version number information corresponding to the current release time.

[0050] In the specific implementation process, the executor of this solution can be a local development platform or a CICD platform. The CICD platform can be a devops platform, etc.

[0051] In some embodiments of the present invention, the format of the publication time may be the publication date, or may be the specific publication time.

[0052] The mobile application construction method and system based on component version rolling management proposed in the present invention can reduce the manual communication cost in the mobile application construction process, reduce manual operations, ensure the stability and security of mobile application construction, realize the automation of component version management, and is not prone to errors and omissions. The efficiency of component version management is significantly higher than that of manual work. The method and system proposed in the present invention can realize efficient component version number rolling management and combine it with packaging compilation in the process of multiple people and multiple teams collaborating to build mobile applications.

[0053] In some embodiments of the present invention, the method proposed by the present invention further includes: obtaining a configuration file of the current release time from the cloud platform during the local development process of the developer.

[0054] By adopting the embodiment of the invention, developers can obtain the latest configuration file of the current release time from the cloud platform at any time.

[0055] In some embodiments of the present invention, the step in step S130 in which the CICD platform uses the Ansible script to obtain the current configuration file from the built mobile application includes: the CICD platform uses the Ansible script to clone the code of the built mobile application, and finds the current configuration file in the cloned code.

[0056] By adopting the embodiment of the invention, the configuration file can be found in the code of the mobile application through the Ansible script, so as to further automatically replace the configuration file.

[0057] In some embodiments of the present invention, the step of regenerating the configuration file for this release time according to the predefined component version number information based on this release time and the default component information in step S130 includes: on the basis of the acquired current configuration file, modifying the component version number information included in the current configuration file according to the predefined component version number information based on this release time, and regenerating the configuration file for this release time according to the records of the default component information for components that are not involved in modification.

[0058] By adopting the embodiment of the invention, the configuration file of the current release time can be automatically regenerated, thereby reducing the manual communication cost.

[0059] In some embodiments of the present invention, the cloud platform for managing configuration files includes any one of gitlab, GitHub, Bitbucket, Azure DevOps and Gitea platforms.

[0060] In some embodiments of the present invention, the step of pipeline compiling and packaging based on the acquired configuration file, the associated mobile application unique identifier and the associated data in step S140 includes: in the process of mobile application packaging, triggering the compilation and packaging task and obtaining mobile application information, cloning the code through the mobile application information, replacing the original configuration file included in the mobile application code with the acquired configuration file through the associated data and the associated mobile application unique identifier, and compiling and packaging the replaced mobile application code.

[0061] By adopting the embodiment of the invention, it is possible to implement pipeline translation and packaging of mobile application versions to be released.

[0062] Furthermore, in some embodiments of the present invention, the compilation and packaging tasks in the process of packaging the mobile application are implemented by using an Xcode tool or a gradle tool.

[0063] Figure 2 This is a flow chart of a method for building a mobile application based on component version rolling management in another embodiment of the present invention. Figure 2 The method shown can be specifically divided into the following 6 steps.

[0064] Step 1: It is necessary to design component management functions on the devops platform or other CICD platforms. The technical implementation of the management function can be consistent with the existing platform. The component management function must include three parts: The first part is the default component information management, which includes the basic description information of the component, the unique identifier of the associated mobile application, and the current version number. The second part is the component information management based on the release time, which includes the basic description information of the component, the release time, the unique identifier of the associated mobile application, and the version number. The third part is the configuration file generation.

[0065] Step 2: The mobile application service developer or person in charge maintains the component management data. When using this function for the first time, you need to initialize the complete default component information, and then predefine a period of component version number information based on the release time (we initialize one year's data each time, which can be freely scheduled according to the release frequency. The number of components based on the release time and the default number of components are exactly the same).

[0066] Step 3: Enter the development cycle of the current release time, because the component version number information based on the release time is full data, that is, it is not clear which of the full version number information will be used when it is predefined, so as to avoid all components needing to be released, developers need to associate the mobile application with the component version number information involved in this release time, that is, I associate what I use, without communicating with other members. The purpose of this step is to obtain the association between the mobile application associated by the developer and the component information involved in this release time.

[0067] Step 4: Developers generate configuration files through the component management function (we trigger generation by manual clicks, or by creating a project). Configuration file generation is a pipeline task combined with the existing platform. The task is triggered, and the task obtains mobile application information and default component information. Then the Ansible script clones the application code, finds the configuration file, and regenerates the configuration file using the component version number information, with the new one overwriting the old one. Finally, the new file is uploaded to gitlab. During local development, this new configuration file can be obtained to the local code without manual modification or further manual communication.

[0068] Step 5: Enter the test or online cycle of the current release time, and compile and package the mobile application. Compilation and packaging combined with the existing platform is a pipeline task, which triggers the task and obtains the mobile application information. When compiling and packaging, the code is cloned through the mobile application information, and then the current latest configuration file is obtained and replaced in the application code through the application unique identifier to perform compilation and packaging. This process is generally combined with the pipeline tasks of the existing platform. It only requires modifying the content of the pipeline task to add the step of obtaining the new file. This process only requires triggering the compilation and packaging task. Developers do not need to modify the configuration file content, nor do they need to submit the configuration file code in the mobile application. The automated mechanism will not miss the modification of the version information of a component.

[0069] Step 6: After the mobile application is released online, the version number update is triggered to update the component version number involved in this release time to the default component version number, that is, the component version number with a component version number update in this release time is synchronously updated in the default component information.

[0070] Step 7: When entering the development cycle of the next release time, continue to repeat steps 2 to 6 to implement rolling updates of component management and combine it with compilation and packaging. Among them, steps 1 to 6, the manual operations involved are only related to your own parts, and no manual communication or manual modification is required. The parts that do not involve manual operations are completed automatically by the program. This greatly simplifies the process of component management of mobile applications, reduces manual operations, avoids missing components, and improves efficiency.

[0071] In summary, the mobile application construction method and system based on component version rolling management proposed in the present invention can reduce the manual communication cost in the mobile application construction process, reduce manual operations, ensure the stability and security of mobile application construction, realize the automation of component version management, and is not prone to errors and omissions. The efficiency of component version management is significantly higher than that of manual work. The method and system proposed in the present invention can realize efficient component version number rolling management and combine it with packaging compilation in the process of multiple people and multiple teams collaborating to build mobile applications.

[0072] Specifically, the advantages of the method proposed by the present invention are:

[0073] (1) Reduce manual communication costs: Component management is used to clearly define the default component version number and the component version number required for each mobile application release. The development manager only needs to define it once and no longer needs to worry about how to define the version number. He only needs to worry about which components to develop.

[0074] (2) Reduce manual operations: Developers do not need to rewrite the content of configuration file components, and the rolling management of component version numbers is automatically performed, eliminating the need for developers to manually submit related codes.

[0075] (3) Automation: The rolling management of component version numbers is combined with the steps of compiling and packaging mobile applications to form a closed-loop mechanism. After the code is downloaded, a specific program obtains all component version information of the mobile application, including the default component version information and the version information required for this release, automatically regenerates the latest configuration file, and compiles and packages based on the latest configuration file.

[0076] Corresponding to the above method, the present invention also provides a mobile application construction system based on component version rolling management, the system includes a computer device, the computer device includes a processor and a memory, the memory stores computer instructions, the processor is used to execute the computer instructions stored in the memory, when the computer instructions are executed by the processor, the system implements the steps of the method described above.

[0077] The embodiment of the present invention also provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, the steps of the aforementioned edge computing server deployment method are implemented. The computer-readable storage medium can be a tangible storage medium, such as a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a floppy disk, a hard disk, a removable storage disk, a CD-ROM, or any other form of storage medium known in the technical field.

[0078] An embodiment of the present invention further provides a computer program product, including a computer program / instruction, which implements the steps of the method described in any one of the above embodiments when executed by a processor.

[0079] It should be understood by those skilled in the art that the exemplary components, systems and methods described in conjunction with the embodiments disclosed herein can be implemented in hardware, software or a combination of the two. Whether it is performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention. When implemented in hardware, it can be, for example, an electronic circuit, an application specific integrated circuit (ASIC), appropriate firmware, a plug-in, a function card, etc. When implemented in software, the elements of the present invention are programs or code segments used to perform the required tasks. The program or code segment can be stored in a machine-readable medium, or transmitted on a transmission medium or a communication link via a data signal carried in a carrier.

[0080] It should be clear that the present invention is not limited to the specific configuration and processing described above and shown in the figures. For the sake of simplicity, a detailed description of the known method is omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of the present invention is not limited to the specific steps described and shown, and those skilled in the art can make various changes, modifications and additions, or change the order between the steps after understanding the spirit of the present invention.

[0081] In the present invention, features described and / or illustrated for one embodiment may be used in the same or similar manner in one or more other embodiments, and / or combined with features of other embodiments or replace features of other embodiments.

[0082] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. For those skilled in the art, the embodiments of the present invention may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A method for building a mobile application based on component version rolling management, characterized in that: The method comprises the following steps: In the initialization phase of mobile application creation, the CICD platform obtains the default component information of the components contained in the mobile application predefined by the developer and the predefined component version number information based on the subsequent release time, wherein the default component information includes the associated mobile application unique identifier and the current version number, and the component version number information includes the component version number information involved in the modification of each release time and the default component version number information; At each release time, the CICD platform obtains the associated data of the mobile application unique identifier and the component version number information based on the release time; Whenever the CICD platform receives a configuration file generation task created by a developer, the CICD platform uses the Ansible script to obtain the current configuration file from the built mobile application, and regenerates the configuration file of the current release time according to the pre-defined component version number information based on the current release time and the default component information. The regenerated configuration file overwrites the previous configuration file, and uploads the regenerated configuration file to the cloud platform for managing configuration files, so that the configuration file of the current release time can be obtained from the cloud platform during local development and mobile application packaging. In each mobile application release process, a configuration file of this release time is obtained from the cloud platform, and pipeline compilation and packaging is performed based on the obtained configuration file, the associated mobile application unique identifier and the associated data to obtain an online application package of this release time; After each mobile application is launched, the CICD platform updates the default component information based on the component version number information corresponding to the current release time.

2. The method according to claim 1, characterized in that The default component information also includes basic component description information, which includes component name, component version number, component function description, author information, and support information; The method further includes: obtaining a configuration file of the current release time from the cloud platform during the local development process of the developer.

3. The method according to claim 1, characterized in that The steps of obtaining the current configuration file from the built mobile application by using the Ansible script on the CICD platform include: The CICD platform clones the code of the built mobile application using the Ansible script and finds the current configuration file in the cloned code.

4. The method according to claim 1, characterized in that The step of regenerating the configuration file of the current release time according to the predefined component version number information based on the current release time and the default component information includes: Based on the current configuration file obtained, the component version number information contained in the current configuration file is modified according to the predefined component version number information based on the current release time. For components that do not involve modification, the configuration file of the current release time is regenerated according to the record of the default component information.

5. The method according to claim 4, characterized in that The cloud platform for managing configuration files includes any one of gitlab, GitHub, Bitbucket, Azure DevOps and Gitea platforms.

6. The method according to claim 1, characterized in that The step of pipeline compiling and packaging based on the acquired configuration file, the associated mobile application unique identifier and the associated data includes: During the mobile application packaging process, the compilation and packaging task is triggered and the mobile application information is obtained. The code is cloned through the mobile application information. The obtained configuration file replaces the original configuration file contained in the mobile application code through the associated data and the associated mobile application unique identifier, and the replaced mobile application code is compiled and packaged.

7. The method according to claim 6, characterized in that The compilation and packaging tasks in the mobile application packaging process are implemented through Xcode tools or gradle tools.

8. A mobile application construction system based on component version rolling management, comprising a processor, a memory, and a computer program / instruction stored in the memory, characterized in that: The processor is used to execute the computer program / instructions, and when the computer program / instructions are executed, the system implements the steps of the method according to any one of claims 1 to 7.

9. A computer-readable storage medium having a computer program / instruction stored thereon, characterized in that: When the computer program / instructions are executed by a processor, the steps of the method as claimed in any one of claims 1 to 7 are implemented.

10. A computer program product comprising a computer program / instructions, characterized in that When the computer program / instructions are executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.