A version management system for application distribution platform
By designing a version management system in the application distribution platform, the application crash and version conflict caused by dependency changes are solved, and automated testing and rollback functions are implemented, improving the user experience.
Patent Information
- Application Number
- CN202410896379.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-05
- Publication Date
- 2024-11-05
- Estimated Expiration
- 2044-07-05
AI Technical Summary
The existing application distribution platform cannot effectively detect dependency changes, causing application crashes or inconsistencies, and different versions of software may have functional conflicts and cannot return to the previous old version, resulting in a bad user experience.
A version management system for application distribution platform was designed. By obtaining business requirements and formulating version management strategies, determining version management modules, and automated testing and code review based on continuous integration and continuous delivery channels, software packages and the latest version number are generated to realize the application. Program version management and rollback functions.
Discover code flaws and potential security risks through automated testing and code review, avoid application crashes, and automatically roll back to older versions when problems occur, improving user experience.
Smart Images

Figure CN118444970B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of software engineering and system architecture, and in particular to a version management system of an application distribution platform. Background Art
[0002] With the rapid development of mobile Internet, application developers and users have higher and higher demands for application software. In order to better meet these demands, application distribution platforms came into being.
[0003] However, existing application distribution platforms cannot detect dependencies. When dependencies change, the application may crash or become inconsistent. At the same time, different versions of software may have functional conflicts and cannot return to the previous old version, which may lead to a poor user experience.
[0004] Therefore, the present invention provides a version management system for an application distribution platform. Summary of the invention
[0005] The present invention provides a version management system for an application distribution platform, which is used to solve the defects in the prior art that when dependencies change, the application may crash or be inconsistent, different versions of software may have functional conflicts, and it is impossible to return to the previous old version, which may cause a poor user experience.
[0006] In one aspect, the present invention provides a version management system for an application distribution platform, comprising:
[0007] The first acquisition module: obtains the business requirements and goals of the application distribution platform version management, and formulates corresponding version management strategies and specifications;
[0008] First, determine the module: determine the relevant version management module according to the version management strategy and specifications;
[0009] A second determination module: determining the software package and the latest version number of each application based on the continuous integration and continuous delivery channels according to the version management module;
[0010] Test and review module: performs automated testing and code review on each application based on the software package and the latest version number;
[0011] Storage module: Determine multiple data of each new version of the application based on the review results, and store the multiple data in documents to achieve version management of the application distribution platform.
[0012] According to a version management system of an application distribution platform provided by the present invention, a first acquisition module includes:
[0013] First acquisition unit: obtain relevant data on user feedback, competitive product analysis and market research;
[0014] A first determining unit: determining the function and performance index of the application distribution platform version management according to the relevant data;
[0015] A second determining unit: determining the business requirements and objectives of the application distribution platform version management based on the functions and performance indicators;
[0016] The third determination unit: determines the development language, framework and technology stack adopted by the platform according to the business requirements and goals;
[0017] The first formulation unit: formulate corresponding version management strategies and specifications based on the development language, framework and technology stack.
[0018] According to a version management system of an application distribution platform provided by the present invention, a first determination module includes:
[0019] The second acquisition unit: defines each stage in the application life cycle according to the version management strategy and specifications, and obtains different version management tasks and goals in each stage;
[0020] A fourth determining unit: determining a version control point for each stage according to different version management tasks and objectives in each stage;
[0021] A fifth determining unit: obtaining a development process of the application program, and determining a version control tool based on the version control point;
[0022] The sixth determining unit determines a related version management module according to the application life cycle, the version control point in each stage and the version control tool.
[0023] According to a version management system of an application distribution platform provided by the present invention, the second determination module includes:
[0024] Management unit: managing the application build process using continuous integration and continuous delivery tools according to the version management module;
[0025] Check unit: During the build process, use specific build tools to check the dependencies between the code and each application;
[0026] Generating unit: generating a dependency tree of code and application based on the dependency relationship;
[0027] A seventh determining unit: determining a software package and a latest version number of the application program according to the dependency tree.
[0028] According to a version management system of an application distribution platform provided by the present invention, after determining the software package of each application based on the continuous integration and continuous delivery channel, the version management system further includes:
[0029] Create a unit: Create a separate branch for each application and obtain all the code for that application and the related build and test scripts;
[0030] Differentiate units: Store each branch in a version control system and use tags, milestones, or other markers to distinguish different versions;
[0031] Update unit: When a new version is to be released, all code and build / test scripts of the corresponding branch will be updated;
[0032] Monitoring unit: During the development process, the continuous integration system will monitor the activities of each branch. When a new version is obtained, the continuous integration system will automatically trigger the build, test, and deployment process. If an abnormality is found, the continuous integration system will automatically roll back to the previous version.
[0033] Execution unit: During the continuous delivery process, when a new version is obtained, the continuous delivery system will perform building, testing, and deployment on all branches. If any abnormality is found, the continuous delivery system will automatically roll back to the previous version.
[0034] According to the present invention, a version management system of an application distribution platform, a test review module, includes:
[0035] Writing unit: determine all functions and edge cases of the application based on the software package and the latest version number, and write test scripts;
[0036] The second formulation unit: formulate corresponding code review rules according to the coding standards;
[0037] Test review unit: performs automated testing and code review on each application based on the test scripts and code review rules and based on automated tools.
[0038] According to a version management system of an application distribution platform provided by the present invention, a storage module includes:
[0039] The eighth determination unit: determines different running states of each new version of the application according to the review results;
[0040] A ninth determining unit: determining multiple data of each new version of the application according to the different running states;
[0041] Storage unit: Use data analysis tools to organize and classify multiple data, and store documents through API interfaces to achieve version management of the application distribution platform.
[0042] According to a version management system of an application distribution platform provided by the present invention, after performing automated testing and code review on each application based on the software package and the latest version number, the version management system further includes:
[0043] The first creation module: creates a preset boot environment for the software package, and uploads the preset boot environment to a target host where the application distribution platform is located;
[0044] A second creation module: creating a script file for the preset boot environment according to the software package;
[0045] Association module: associates the created script file with the application of the target host;
[0046] The second acquisition module: after the association is completed, the preset boot environment is installed on the target host, and the test configuration files related to the software package are obtained from the preset file library;
[0047] Generating module: generating an installation test task of a software package based on the test configuration file;
[0048] The third determination module: determines the number of cyclic tests and cyclic test lines of the installation test task according to the operating system type, CPU and memory parameters of the target host;
[0049] Import module: obtains the test address of the installation test task and imports the software package into the preset boot environment according to the test address;
[0050] Execution module: executes the installation test of the target number of software packages using the test circuit according to the installation test task in the preset boot environment;
[0051] A judgment module: obtaining execution information during each installation test process, and judging whether the software package can be updated on the target host in the preset boot environment according to the execution information; if so, confirming that the software package can be installed normally on the target host; otherwise, confirming that the software package cannot be installed normally on the target host;
[0052] Detection module: When it is confirmed that the software package cannot be installed normally on the target host, detect whether the installation line of the target host is abnormal. If so, repair the installation line through the repair tool;
[0053] Test module: After the repair is completed, re-run the installation test. When the test passes, it is confirmed that the software package can be installed normally on the target host;
[0054] Update module: Use the software package to update the application of the target host in the preset boot environment, detect the update progress in real time, and determine whether the software package is damaged based on the update progress. If so, issue a reminder instruction.
[0055] Compared with the prior art, the present invention has the following beneficial effects:
[0056] By formulating corresponding management policies and specifications based on the business needs and goals of the application distribution platform, the software package and the latest version number of each application are determined, and automated testing and code review are performed to discover defects, problems or potential security risks in the code, and provide corresponding repair suggestions to avoid low-level errors that cause application crashes. At the same time, through continuous integration and continuous delivery channels, the application can be traced back to the old version when problems occur, improving the user experience. BRIEF DESCRIPTION OF THE DRAWINGS
[0057] In order to more clearly illustrate the technical solutions in the present invention or 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 some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0058] Figure 1 It is a structural diagram of a version management system of an application distribution platform provided by an embodiment of the present invention;
[0059] Figure 2 It is a structural diagram of the second determination module provided in an embodiment of the present invention. DETAILED DESCRIPTION
[0060] In order to make the purpose, technical solution and advantages of the present invention clearer, the technical solution of the present invention will be clearly and completely described below in conjunction with the drawings of the present invention. Obviously, the described embodiments are 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.
[0061] Embodiment 1:
[0062] An embodiment of the present invention provides a version management system for an application distribution platform, such as Figure 1 As shown, the system mainly includes the following modules:
[0063] The first acquisition module: obtains the business requirements and goals of the application distribution platform version management, and formulates corresponding version management strategies and specifications;
[0064] First, determine the module: determine the relevant version management module according to the version management strategy and specifications;
[0065] A second determination module: determining the software package and the latest version number of each application based on the continuous integration and continuous delivery channels according to the version management module;
[0066] Test and review module: performs automated testing and code review on each application based on the software package and the latest version number;
[0067] Storage module: Determine multiple data of each new version of the application based on the review results, and store the multiple data in documents to achieve version management of the application distribution platform.
[0068] In this embodiment, the application distribution platform is a tool that facilitates users to find, download and install applications, and provides an interface that allows users to search, browse and filter applications, as well as obtain and manage applications from multiple sources (such as application stores, developer websites, etc.).
[0069] In this embodiment, the business requirements include: user experience, ease of use, rich application selection, and security and reliability.
[0070] In this embodiment, the version management strategy is a set of methods and rules that guide the application development, testing, release and management process, which is usually used to control the quality, security and consistency of software products, including:
[0071] Version numbering strategy: Determine the numbering rules for different versions of the application, such as using timestamps, version numbers, revision numbers, etc.
[0072] Code management strategy: Defines the rules for how source code, dependencies, build files, and test scripts are stored and managed, such as version control systems, branching, and merging strategies.
[0073] Release planning strategy: Determine the rules for when to release each new version, such as weekly, monthly, quarterly, etc., and develop a detailed release plan for each version.
[0074] Defect management and rollback strategy: Defines how to track and manage defects and errors, and the rules for how to handle and rollback errors, such as defect tracking system, rollback strategy, etc.
[0075] In this embodiment, the version management module is an important part of the software development process, used to record and track changes that occur during the development, testing and release of different versions of the software, including the addition, deletion, modification of code, and changes to documents and other metadata.
[0076] In this embodiment, continuous integration is a software development practice that refers to the process of frequently integrating code into a shared repository and automatically building, testing, and deploying the code, including three steps: checking source code, building software packages, and executing automated tests.
[0077] In this embodiment, continuous delivery refers to a method of frequently delivering software packages to users in a software development process.
[0078] In this embodiment, the software package of the application refers to an instance of the software package, which includes a set of codes for specific functions or tasks executed by the application program.
[0079] In this embodiment, the latest version number of the application refers to the latest version number of the application, which is usually a unique digital identifier that indicates the latest functions of the application, which vulnerabilities and errors have been fixed, and may provide new features or improvements.
[0080] In this embodiment, automated testing is a method of automatically executing test cases using a computer program with the goal of detecting errors or defects in a software system. In automated testing, test scripts are written and stored in a reusable library and then run in multiple environments to check whether the software works as expected in each version.
[0081] In this embodiment, code review refers to the process of checking and reviewing source code during the software development process to ensure that the code complies with programming standards, design specifications, and coding specifications.
[0082] In this embodiment, multiple data depend on the type and function of the application, such as: Newly added data: some functions or features are added to the application, such as adding
[0083] A new interface, adjustments to certain setting options, etc. These newly added data may include relevant configuration information, user feedback, log records, and other information.
[0084] Modified data: Some functions or features have been modified in the application, such as changing the layout of a certain interface, optimizing certain performance indicators, etc. The modified data may include code comparison before and after the modification, change records, user feedback and other information.
[0085] Deleted data: Certain functions or features are deleted in the application, such as removing an infrequently used function button or deleting a history record. The deleted data may include configuration information before deletion and log records after deletion.
[0086] The beneficial effects of the above technical solution are: by formulating corresponding management policies and specifications based on the business needs and goals of the application distribution platform, the software package and the latest version number of each application are determined, and automated testing and code review are performed to discover defects, problems or potential security risks in the code, and provide corresponding repair suggestions to avoid low-level errors that cause application crashes. At the same time, through continuous integration and continuous delivery channels, the application can be traced back to the old version when problems occur, thereby improving the user experience.
[0087] Embodiment 2:
[0088] Based on Example 1, the first acquisition module of the embodiment of the present invention includes:
[0089] The first acquisition unit: by obtaining relevant data on user feedback, competitive product analysis and market research;
[0090] A first determining unit: determining the function and performance index of the application distribution platform version management according to the relevant data;
[0091] A second determining unit: determining the business requirements and objectives of the application distribution platform version management based on the functions and performance indicators;
[0092] The third determination unit: determines the development language, framework and technology stack adopted by the platform according to the business requirements and goals;
[0093] The first formulation unit: formulate corresponding version management strategies and specifications based on the development language, framework and technology stack.
[0094] In this embodiment, the version management function of the application distribution platform is mainly used to publish, maintain and manage application software on platforms of different versions, such as:
[0095] Version release: According to the demand plan, a unique version number is generated for each application version and packaged into the application package. At the same time, the new version package needs to be uploaded to the corresponding application store for review and release.
[0096] Version update: Based on the existing version, fix or add new features to meet user needs. These updates can be divided into functional updates, performance optimizations, etc. After the version is updated, it also needs to be packaged and published to the app store.
[0097] Version control: Version control is performed through code repositories such as Git and SVN, and detailed information of each version is recorded, including version number, submission time, update content, etc. This helps the team track the change history of each version and facilitates subsequent version backtracking and problem troubleshooting.
[0098] In this embodiment, the performance indicators of the application distribution platform version management include: release cycle, version iteration frequency, and error rate.
[0099] In this embodiment, the development language used by the platform is, for example, Java, C++, and Objective-C.
[0100] In this embodiment, the framework adopted by the platform is, for example: a front-end framework, a back-end framework, and a database framework.
[0101] In this embodiment, the technology stack of the application distribution platform generally includes multiple parts such as the front-end, the back-end and the server-end.
[0102] The beneficial effects of the above technical solution are: by applying the business needs and goals of version management of the application distribution platform, the development language, framework and technology stack adopted by the platform are determined, so as to formulate corresponding version management strategies and specifications. Standardized documents and clear management strategies can make it easier to understand and take over tasks, thereby improving development efficiency and reducing maintenance costs.
[0103] Embodiment 3:
[0104] Based on Example 2, the first determination module in this embodiment of the present invention includes:
[0105] The second acquisition unit: defines each stage in the application life cycle according to the version management strategy and specifications, and obtains different version management tasks and goals in each stage;
[0106] A fourth determining unit: determining a version control point for each stage according to different version management tasks and objectives in each stage;
[0107] A fifth determining unit: obtaining a development process of the application program, and determining a version control tool based on the version control point;
[0108] The sixth determining unit determines a related version management module according to the application life cycle, the version control point in each stage and the version control tool.
[0109] Before determining the version control point of each stage according to the different version management tasks and objectives in each stage, it is also used to identify the execution steps in each task flow of the version management task;
[0110] Perform the following verification operations for all execution steps in any identified task flow:
[0111] When two adjacent execution steps include the same action, the suspicious step in the two adjacent execution steps is determined according to the following filtering algorithm, and the suspicious step is marked, and the marked suspicious step is output for manual verification;
[0112] Obtaining manual verification results, and constructing a flowchart corresponding to any of the task processes according to the manual verification results;
[0113] ;
[0114] in, It indicates the probability of an action occurring in the next execution step, i.e., the nth execution step, when the action occurs in the n-1th execution step; Used to indicate the action that occurs in the nth execution step; Used to represent the i-th action; Represents the adjective sequence that appears in the nth execution step; It is used to indicate the action that occurs in the n+1th execution step; N indicates the total number of steps in all execution steps in any task flow; represents the probability of adjective sequence u appearing in the n+1th execution step when the i-th action in the n-th execution step is executed, It is expressed as the probability of the adjective sequence u appearing when the i-th action in the n-th execution step is executed.
[0115] Steps where the probability of an action occurring is greater than or equal to a preset probability are retained, and the execution steps of the task flow are determined according to the retained steps to obtain the corresponding flow chart.
[0116] In this embodiment, the life cycle of an application refers to the entire process from conception, design, development to release and maintenance of the application.
[0117] In this embodiment, different version management tasks may be performed at different stages of the application life cycle, such as:
[0118] During the requirements analysis and planning phase, some lightweight version management tasks will be performed, such as recording user feedback and requirements changes, and updating documents and plans.
[0119] Design and development phase: More complex version management tasks are performed, such as tracking and managing source code versions, integration testing, and building systems.
[0120] Testing Phase: Release testing and acceptance testing are performed to ensure that the application meets the expected standards and specifications.
[0121] The beneficial effect of the above technical solution is: by obtaining the version management tasks and goals of each stage of the application, determining the version control points of each stage, and thus determining the version control tool, the relevant version management modules are obtained, which can simplify version control and facilitate collaboration between users.
[0122] Embodiment 4:
[0123] Based on Example 3, the second determination module of the embodiment of the present invention is as follows: Figure 2 As shown, including:
[0124] Management unit: managing the application build process using continuous integration and continuous delivery tools according to the version management module;
[0125] Check unit: During the build process, use specific build tools to check the dependencies between the code and each application;
[0126] Generating unit: generating a dependency tree of code and application based on the dependency relationship;
[0127] A seventh determining unit: determining a software package and a latest version number of the application program according to the dependency tree.
[0128] In this embodiment, the process of building the application generally includes: selecting tools and frameworks to be used, writing application code, integrating application code, and compiling application code.
[0129] In this embodiment, common construction tools include: Git, SVN, and Eclipse.
[0130] In this embodiment, the dependency between the code and each application refers to the association between code libraries. When the application is running, different code libraries will call each other to provide specific functions. For example, an image processing application may call an image processing algorithm. If this algorithm exists in another code library, the application can call it. In this case, the application relies on the algorithm in this code library to implement image processing.
[0131] In this embodiment, the dependency tree is a graphical representation method for displaying the dependency relationship between code bases. Each node represents a code base and is connected by edges to represent the dependency relationship between them. Each layer of the dependency tree represents a hierarchy. The top layer is the most common dependency relationship between all code bases. As the number of layers increases, the dependency relationship becomes more and more specific and special. The bottom layer is a code base specific to a single application.
[0132] The beneficial effect of the above technical solution is: by using a specific build tool to check the dependencies between the code and each application during the application building process and generating a dependency tree, the dependencies between the code and the application can be intuitively determined. Furthermore, the software package and the latest version number of the application can be determined, which facilitates the platform to carry out release management and improves the reliability and speed of the application distribution platform.
[0133] Embodiment 5:
[0134] Based on Example 4, after determining the software package of each application based on the continuous integration and continuous delivery channel, the embodiment of the present invention further includes:
[0135] Create a unit: Create a separate branch for each application and obtain all the code for that application and the related build and test scripts;
[0136] Differentiate units: Store each branch in a version control system and use tags, milestones, or other markers to distinguish different versions;
[0137] Update unit: When a new version is to be released, all code and build / test scripts of the corresponding branch will be updated;
[0138] Monitoring unit: During the development process, the continuous integration system will monitor the activities of each branch. When a new version is obtained, the continuous integration system will automatically trigger the build, test, and deployment process. If an abnormality is found, the continuous integration system will automatically roll back to the previous version.
[0139] Execution unit: During the continuous delivery process, when a new version is obtained, the continuous delivery system will perform building, testing, and deployment on all branches. If any abnormality is found, the continuous delivery system will automatically roll back to the previous version.
[0140] In this embodiment, independent branches of the application refer to dividing the code base of the application into multiple separate parts so that different tasks can be performed simultaneously during the development process and can be changed and deployed independently.
[0141] In this embodiment, the related construction is a construction method, which means that some additional steps will be automatically triggered during the construction process. For example, when writing an application in C++, the related construction may include checking whether the variable type is correct, or checking whether there is enough memory, or checking whether there are enough resources available, etc.
[0142] In this embodiment, the version control system is a tool in software engineering for tracking and managing the code and change history of a software project, such as Git, SVN, and Perforce.
[0143] In this embodiment, milestones refer to certain important moments in the project life cycle.
[0144] The beneficial effects of the above technical solution are: different versions of each application are distinguished by labels, milestones or other markers. When a new version is obtained, the continuous integration system will monitor the activities of each branch, and the continuous delivery system will perform building, testing and deployment on all branches. It can detect abnormal situations in time and automatically roll back to the previous version, which can ensure the stability of the platform and improve the user experience.
[0145] Embodiment 6:
[0146] Based on Example 5, the test review module of this embodiment of the present invention includes:
[0147] Writing unit: determine all functions and edge cases of the application based on the software package and the latest version number, and write test scripts;
[0148] The second formulation unit: formulate corresponding code review rules according to the coding standards;
[0149] Test review unit: performs automated testing and code review on each application based on the test scripts and code review rules and based on automated tools.
[0150] In this embodiment, the boundary conditions of the application refer to the external limitations of the application, such as user needs, hardware requirements, and network limitations. For example, if the application needs to connect to a specific database, then the database must support all data formats and query languages used by the application. If the application needs to run on a specific operating system, then the system must support all application files and formats.
[0151] In this embodiment, the test script is a set of scripts for automated testing of an application program, using a specific programming language and running in a specific test framework, which can simulate different test scenarios and verify the behavior of the application program.
[0152] In this embodiment, the coding standard is a set of rules, guidelines or conventions for guiding programmers to follow when writing code, such as: naming conventions, comment styles, data structures and algorithms.
[0153] In this embodiment, automated testing is an automated testing process that can be used to check different parts of software systems and evaluate these systems.
[0154] In this embodiment, code review refers to the process of checking a section of program code to determine whether the code meets the requirements of programming specifications, readability, security and performance.
[0155] The beneficial effects of the above technical solution are: writing test scripts through all the functions and boundary conditions of the application, formulating code review rules according to coding standards, and performing automated testing and code review based on automated tools, which can be run quickly multiple times, saving a lot of time and labor costs, while ensuring code quality, reducing the possibility of errors, and improving the reliability of software products.
[0156] Embodiment 7:
[0157] Based on Embodiment 6, the storage module of the embodiment of the present invention includes:
[0158] The eighth determination unit: determines different running states of each new version of the application according to the review results;
[0159] A ninth determining unit: determining multiple data of each new version of the application according to the different running states;
[0160] Storage unit: Use data analysis tools to organize and classify multiple data, and store documents through API interfaces to achieve version management of the application distribution platform.
[0161] In this embodiment, the code review results are conclusions and suggestions obtained after reviewing the source code. During the code review process, the code syntax, format, naming conventions, module division, etc. are checked to see if they comply with coding standards.
[0162] In this embodiment, different running states of the new version of the application refer to the impacts and performances that may occur during the release and use of the new version of the application, such as: unstable state, compatibility state, promotion state, and problem identification state.
[0163] In this embodiment, the API interface is a mechanism for implementing communication between applications. The API defines a set of specifications that describe how an application interacts with other applications or services to implement specific functions, such as storage and sharing.
[0164] The beneficial effect of the above technical solution is: determining multiple data of the new version through the different running states of each new version of the application, and classifying and organizing the data for document storage, so that different personnel can easily connect to different applications and services without changing the data, thereby improving the scalability and maintainability of the platform.
[0165] Embodiment 8:
[0166] Based on Example 7, after performing automated testing and code review on each application based on the software package and the latest version number, the embodiment of the present invention further includes:
[0167] The first creation module: creates a preset boot environment for the software package, and uploads the preset boot environment to a target host where the application distribution platform is located;
[0168] A second creation module: creating a script file for the preset boot environment according to the software package;
[0169] Association module: associates the created script file with the application of the target host;
[0170] The second acquisition module: after the association is completed, the preset boot environment is installed on the target host, and the test configuration files related to the software package are obtained from the preset file library;
[0171] Generating module: generating an installation test task of a software package based on the test configuration file;
[0172] The third determination module: determines the number of cyclic tests and cyclic test lines of the installation test task according to the operating system type, CPU and memory parameters of the target host;
[0173] Import module: obtains the test address of the installation test task and imports the software package into the preset boot environment according to the test address;
[0174] Execution module: executes the installation test of the target number of software packages using the test circuit according to the installation test task in the preset boot environment;
[0175] A judgment module: obtaining execution information during each installation test process, and judging whether the software package can be updated on the target host in the preset boot environment according to the execution information; if so, confirming that the software package can be installed normally on the target host; otherwise, confirming that the software package cannot be installed normally on the target host;
[0176] Detection module: When it is confirmed that the software package cannot be installed normally on the target host, detect whether the installation line of the target host is abnormal. If so, repair the installation line through the repair tool;
[0177] Test module: After the repair is completed, re-run the installation test. When the test passes, it is confirmed that the software package can be installed normally on the target host;
[0178] Update module: Use the software package to update the application of the target host in the preset boot environment, detect the update progress in real time, and determine whether the software package is damaged based on the update progress. If so, issue a reminder instruction.
[0179] In this embodiment, the preset boot environment of the software package refers to a boot interface provided when the software is installed or started, which provides the user with some options and settings so that the user can better use and configure the software.
[0180] In this embodiment, the target host where the application distribution platform is located refers to a server or cloud host on which the application distribution platform is run and deployed.
[0181] In this embodiment, the script file is a text file containing a series of instructions or commands, which can be used to control the execution process of a computer program. Common script file suffixes include .bat (Windows operating system) and .sh (Linux and macOS operating systems).
[0182] In this embodiment, the preset file library is a design pattern that can be used to store a group of commonly used or repeatedly used files.
[0183] In this embodiment, the test configuration file associated with the software package is a file used to describe the test configuration information of the software package. The file usually contains information about the software package to be tested, such as the name, version, dependencies, and test objectives of the software package. The test configuration file can also define how to run the test, such as the test framework used and the source of the test data.
[0184] In this embodiment, the software package installation test task is a set of test tasks performed to verify whether the software package is correctly installed in the expected manner and can work normally. This type of test mainly focuses on the installation process of the software package, including installation methods, steps, dependencies, etc.
[0185] In this embodiment, the operating system type of the target host generally refers to the specific operating system that we want to deploy application software on the target host, such as: Windows operating system, Linux operating system, macOS operating system.
[0186] In this embodiment, the operating parameters of the target host refer to some key indicators that need to be considered when allocating memory resources to target devices such as servers or computers, such as: memory size, memory type, and memory frequency.
[0187] In this embodiment, the loop test circuit is a test method mainly used to check whether each part of the product works as expected and whether there are any errors or failures.
[0188] In this embodiment, in the application distribution platform, the test address of the installation test task usually refers to the specific location of the task on the platform, that is, a URL address. This address is usually a relative path to the platform's main page and can be found by accessing the platform's management background or using the platform's internal tools.
[0189] In this embodiment, during the installation test work, the execution information includes operation logs related to the test steps and use cases.
[0190] In this embodiment, the installation route of the target host refers to the steps and methods for installing the operating system on a given target host.
[0191] In this embodiment, the repair tool refers to software used to repair various devices such as computer systems, mobile devices or networks when they fail, such as Master Lu and Driver Genius.
[0192] The beneficial effect of the above technical solution is: by performing the installation test of the software package of the target host in the target boot environment, it can be effectively evaluated whether the target host can complete the complete installation of the installation package in the target boot environment, thereby ensuring the installation stability and success probability of the target host for the application. Furthermore, by repairing the installation line of the target host, it can be further ensured that the target host successfully installs the application installation package, further improving the stability.
[0193] Through the description of the above implementation methods, those skilled in the art can clearly understand that each implementation method can be implemented by means of software plus a necessary general hardware platform, and of course, can also be implemented by hardware. Based on this understanding, the above technical solution is essentially or the part that contributes to the prior art can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, a disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment or some parts of the embodiments.
[0194] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention.
Claims
1. A version management system for an application distribution platform, characterized in that: include: The first acquisition module: obtains the business requirements and goals of the application distribution platform version management, and formulates corresponding version management strategies and specifications; First, determine the module: determine the relevant version management module according to the version management strategy and specifications; A second determination module: determining the software package and the latest version number of each application based on the continuous integration and continuous delivery channels according to the version management module; Test and review module: performs automated testing and code review on each application based on the software package and the latest version number; Storage module: determines multiple data of each new version of the application according to the review results, and stores the multiple data in documents to achieve version management of the application distribution platform; Among them, after performing automated testing and code review on each application based on the software package and the latest version number, it also includes: The first creation module: creates a preset boot environment for the software package, and uploads the preset boot environment to a target host where the application distribution platform is located; A second creation module: creating a script file for the preset boot environment according to the software package; Association module: associates the created script file with the application of the target host; The second acquisition module: after the association is completed, the preset boot environment is installed on the target host, and the test configuration files related to the software package are obtained from the preset file library; Generating module: generating an installation test task of a software package based on the test configuration file; The third determination module: determines the number of cyclic tests and cyclic test lines of the installation test task according to the operating system type, CPU and memory parameters of the target host; Import module: obtains the test address of the installation test task and imports the software package into the preset boot environment according to the test address; Execution module: executes the installation test of the target number of software packages using the test circuit according to the installation test task in the preset boot environment; A judgment module: obtaining execution information during each installation test process, and judging whether the software package can be updated on the target host in the preset boot environment according to the execution information; if so, confirming that the software package can be installed normally on the target host; otherwise, confirming that the software package cannot be installed normally on the target host; Detection module: When it is confirmed that the software package cannot be installed normally on the target host, detect whether the installation line of the target host is abnormal. If so, repair the installation line through the repair tool; Test module: After the repair is completed, re-run the installation test. When the test passes, it is confirmed that the software package can be installed normally on the target host; Update module: Use the software package to update the application of the target host in the preset boot environment, detect the update progress in real time, and determine whether the software package is damaged based on the update progress. If so, issue a reminder instruction.
2. The version management system of the application distribution platform according to claim 1, characterized in that: The first acquisition module includes: First acquisition unit: obtain relevant data on user feedback, competitive product analysis and market research; A first determining unit: determining the function and performance index of the application distribution platform version management according to the relevant data; A second determining unit: determining the business requirements and objectives of the application distribution platform version management based on the functions and performance indicators; The third determination unit: determines the development language, framework and technology stack adopted by the platform according to the business requirements and goals; The first formulation unit: formulate corresponding version management strategies and specifications based on the development language, framework and technology stack.
3. The version management system of the application distribution platform according to claim 1, characterized in that: The first determination module includes: The second acquisition unit: defines each stage in the application life cycle according to the version management strategy and specifications, and obtains different version management tasks and goals in each stage; A fourth determining unit: determining a version control point for each stage according to different version management tasks and objectives in each stage; A fifth determining unit: obtaining a development process of the application program, and determining a version control tool based on the version control point; The sixth determining unit determines a related version management module according to the application life cycle, the version control point in each stage and the version control tool.
4. The version management system of the application distribution platform according to claim 1, characterized in that: The second determination module includes: Management unit: managing the application build process using continuous integration and continuous delivery tools according to the version management module; Check unit: During the build process, use specific build tools to check the dependencies between the code and each application; Generating unit: generating a dependency tree of code and application based on the dependency relationship; A seventh determining unit: determining a software package and a latest version number of the application program according to the dependency tree.
5. The version management system of the application distribution platform according to claim 1, characterized in that: After determining the software package for each application based on the continuous integration and continuous delivery pipeline, it also includes: Create a unit: Create a separate branch for each application and obtain all the code for that application and the related build and test scripts; Differentiate units: Store each branch in a version control system and use tags, milestones, or other markers to distinguish different versions; Update unit: When a new version is to be released, all code and build / test scripts of the corresponding branch will be updated; Monitoring unit: During the development process, the continuous integration system will monitor the activities of each branch. When a new version is obtained, the continuous integration system will automatically trigger the build, test, and deployment process. If an abnormality is found, the continuous integration system will automatically roll back to the previous version. Execution unit: During the continuous delivery process, when a new version is obtained, the continuous delivery system will perform building, testing, and deployment on all branches. If any abnormality is found, the continuous delivery system will automatically roll back to the previous version.
6. The version management system of the application distribution platform according to claim 1, characterized in that: Test review module, including: Writing unit: determine all functions and edge cases of the application based on the software package and the latest version number, and write test scripts; The second formulation unit: formulate corresponding code review rules according to the coding standards; Test review unit: performs automated testing and code review on each application based on the test scripts and code review rules and based on automated tools.
7. The version management system of the application distribution platform according to claim 1, characterized in that: Storage module, including: The eighth determination unit: determines different running states of each new version of the application according to the review results; A ninth determining unit: determining multiple data of each new version of the application according to the different running states; Storage unit: Use data analysis tools to organize and classify multiple data, and store documents through API interfaces to achieve version management of the application distribution platform.
