Application program updating method and related equipment
By receiving application update requests and grouping based on coupled relationships, determining the update plan, the application version update time and stability problems are solved, and efficient and stable automatic updates are achieved.
Patent Information
- Application Number
- CN202410931288.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-11
- Publication Date
- 2024-11-08
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
The application version update process takes a long time and requires more manual operations, which poses a potential risk of online service stability. Especially when multiple teams are promoting R&D in parallel, there are many problems in the distribution process.
A method of application update is proposed, by receiving update requests, grouping based on the coupling relationship between the update content and other application content, determining the application update plan, and executing the update plan in grouping units, including testing and rollback policies , use the operation and maintenance platform to perform updates in parallel, reduce labor costs and improve efficiency.
It realizes efficient and stable automation of applications, reduces labor costs, improves distribution efficiency, and avoids stability risks during the update process through grouping and parallel execution.
Smart Images

Figure CN118916052A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the field of computer technology, and in particular to an application updating method and related devices. Background Art
[0002] At present, the version update process of application programs (abbreviated as release) is not only usually time-consuming and requires a lot of manual operations, but also poses a great threat to the stability of online services when problems occur during release. Therefore, there is an urgent need for an application update method that can achieve efficient and stable automatic update of applications. Summary of the invention
[0003] In view of this, an embodiment of the present disclosure provides an application updating method and related devices, which can realize efficient and stable automatic updating of the application.
[0004] The application update method described in the embodiment of the present disclosure may include: receiving at least one application update request; wherein the application update request includes: at least one update content and a coupling relationship between the at least one update content and other application content; grouping the at least one application update request based on the coupling relationship between the update content contained in the at least one application update request and other application content to obtain at least one application update request group; for each application update request group, determining an application update plan corresponding to each application update request group based on the update content contained therein and the coupling relationship between the update content and other application content; and executing the application update plan corresponding to each application update request group respectively in units of the application update request group.
[0005] In some embodiments of the present disclosure, grouping the at least one application update request based on the coupling relationship between the update content contained in the at least one application update request and other application content includes: dividing the application update requests to which the update content with a coupling relationship in the update content contained in the at least one application update request belongs into the same application update request group to obtain the at least one application update request group.
[0006] In some embodiments of the present disclosure, dividing the application update requests to which the update content with a coupling relationship among the update content included in the at least one application update request belongs into the same application update request group includes: abstracting the at least one application update request into a node respectively; for each first node among the at least one node, in response to determining that there is a coupling relationship between the update content included in it and the update content included in other second nodes, establishing an edge from the second node to the first node to obtain a node dependency graph including at least one dependency subgraph; and based on the node dependency graph, dividing the nodes corresponding to the at least one dependency subgraph contained therein into a group respectively.
[0007] In some embodiments of the present disclosure, the application update request further includes: a test list corresponding to the at least one update content and a rollback strategy.
[0008] In some embodiments of the present disclosure, the above method may further include: for each application update request group, determining a test list and a rollback plan corresponding to each application update request group based on the test list and rollback strategy corresponding to the update content contained therein; and in response to determining that an execution result of an application update plan corresponding to an application update request group does not meet expectations based on the test list corresponding to each application update request group, executing the rollback plan corresponding to the application update request group.
[0009] In some embodiments of the present disclosure, after receiving at least one application update request, the method further includes: receiving a test result for the at least one application update request; for application update requests that pass the test, continuing to perform the step of grouping the at least one application update request based on the coupling relationship between the update content included in the at least one application update request and other application content; and for application update requests that do not pass the test, instructing the requester to resubmit the application update request within a specified first deadline.
[0010] In some embodiments of the present disclosure, before executing the application update plan corresponding to each application update request group separately, the method further includes: receiving a test result for the application update plan corresponding to the at least one application update request group; for the application update plan that passed the test, continuing to execute the steps of executing the application update plan corresponding to each application update request group separately in units of the application update request group; and for the application update plan that did not pass the test, instructing the application update request group administrator to resubmit the application update plan within a specified second deadline.
[0011] In some embodiments of the present disclosure, executing the application update plan corresponding to each application update request group separately in units of application update request groups includes: the operation and maintenance platform executing the application update plan corresponding to each application update request group in parallel in units of application update request groups.
[0012] In some embodiments of the present disclosure, the above method may further include: receiving application execution environment information; wherein, grouping the at least one application update request based on the coupling relationship between the update content contained in the at least one application update request and other application content includes: grouping the at least one application update request based on the coupling relationship between the update content contained in the at least one application update request and other application content and the application execution environment information; and for each application update request group, determining the application update plan corresponding to each application update request group based on the update content contained therein and the coupling relationship between the update content and other application content, includes: for each application update request group, determining the application update plan corresponding to each application update request group based on the update content contained therein, the coupling relationship between the update content and other application content and the application execution environment information.
[0013] Corresponding to the above-mentioned application updating method, the application updating platform described in the embodiment of the present disclosure may include:
[0014] A request receiving module, used to receive an application update request submitted by a demand proposer from a project management platform; wherein the application update request includes: at least one update content and a coupling relationship between the at least one update content and other application content;
[0015] A grouping module, configured to group the at least one application update request based on a coupling relationship between update content included in the at least one application update request and other application content, to obtain at least one application update request group;
[0016] a plan generation module, for determining, for each application update request group, an application update plan corresponding to each application update request group according to the update content contained in each application update request in the current group and the coupling relationship between each update content and other application content; and
[0017] The plan submission module is used to submit the application update plan corresponding to each application update request group to the operation and maintenance platform, and the operation and maintenance platform executes the application update plan corresponding to each application update request group respectively based on the application update request group.
[0018] In some embodiments of the present disclosure, the plan generation module is further used to determine, for each application update request group, a test list and a rollback plan corresponding to the application update request group according to the test list and rollback strategy corresponding to each update content in the current group; and the plan submission module is further used to submit the test list and rollback plan corresponding to each application update request group to the operation and maintenance platform.
[0019] Corresponding to the above-mentioned application update platform, an embodiment of the present disclosure further discloses an application update system, including: the above-mentioned application update platform, project management platform and operation and maintenance platform; wherein the project management platform is used to receive application update requests submitted by the demand-making party, and forward the received application update requests to the application update platform; and the operation and maintenance platform is used to execute the application update plan corresponding to each application update request group respectively in units of application update request groups.
[0020] In addition, an embodiment of the present disclosure further provides an electronic device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the above-mentioned application updating method when executing the program.
[0021] An embodiment of the present disclosure further provides a non-transitory computer-readable storage medium, wherein the non-transitory computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the above-mentioned application updating method.
[0022] An embodiment of the present disclosure further provides a computer program product, including computer program instructions, which, when executed on a computer, enable the computer to execute the above-mentioned application program updating method.
[0023] In the application updating method and related devices described in the embodiments of the present disclosure, the application updating or application rolling back operation is performed in units of each application updating request group, wherein a problem in any application updating request group does not affect other application updating request groups.
[0024] In addition, in the above-mentioned application update method, only one application needs to be submitted for the application update operation, and the application update platform can host the subsequent process. The party proposing the application update only needs to be responsible for clarifying the change content, coupling relationship, test list and rollback strategy of the part that it changes. The application update platform can automatically determine the application update request grouping, and separately determine the application update plan, test list and rollback plan for each application update request grouping, which greatly reduces labor costs and greatly improves the efficiency of application release.
[0025] Moreover, during the above-mentioned application update process, the business management platform and the application update platform are connected, which can cover all online change requirements. When the status is transferred, the form filling can be automatically triggered and log records can be generated for all operations. BRIEF DESCRIPTION OF THE DRAWINGS
[0026] In order to more clearly illustrate the technical solutions in the present disclosure or related technologies, the drawings required for use in the embodiments or related technical descriptions are briefly introduced below. Obviously, the drawings described below are only embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.
[0027] Figure 1 The implementation process of the application updating method described in some embodiments of the present disclosure is shown.
[0028] Figure 2 The implementation process of the method for grouping application update requests described in some embodiments of the present disclosure is shown.
[0029] Figure 3 The specific process of the application update process described in some embodiments of the present disclosure is shown.
[0030] Figure 4 An example of updating an application using the application updating method described in an embodiment of the present disclosure is shown.
[0031] Figure 5 The internal structure of the application update system described in some embodiments of the present disclosure is shown.
[0032] Figure 6 The internal structure of the application update platform described in some embodiments of the present disclosure is shown.
[0033] Figure 7 A more specific schematic diagram of the hardware structure of an electronic device described in some embodiments of the present disclosure is shown. DETAILED DESCRIPTION
[0034] In order to make the objectives, technical solutions and advantages of the present disclosure more clearly understood, the present disclosure is further described in detail below in combination with specific embodiments and with reference to the accompanying drawings.
[0035] It should be noted that, unless otherwise defined, the technical terms or scientific terms used in the embodiments of the present disclosure should be understood by people with ordinary skills in the field to which the present disclosure belongs. The "first", "second" and similar words used in the embodiments of the present disclosure do not indicate any order, quantity or importance, but are only used to distinguish different components. "Including" or "comprising" and similar words mean that the elements or objects appearing before the word cover the elements or objects listed after the word and their equivalents, without excluding other elements or objects. "Connect" or "connected" and similar words are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect. "Up", "down", "left", "right" and the like are only used to indicate relative positional relationships. When the absolute position of the described object changes, the relative positional relationship may also change accordingly.
[0036] It is understandable that before using the technical solutions of each embodiment of the present disclosure, the type, scope of use, usage scenarios, etc. of the personal information involved will be informed to the user in an appropriate manner, and the user's authorization will be obtained.
[0037] For example, in response to receiving an active request from a user, a prompt message is sent to the user to clearly remind the user that the operation requested to be performed will require obtaining and using the user's personal information. Thus, the user can independently choose whether to provide personal information to software or hardware such as an electronic device, application, server, or storage medium that performs the operation of the technical solution of the present disclosure according to the prompt message.
[0038] As an optional but non-limiting implementation, in response to receiving the user's active request, the prompt information may be sent to the user in the form of a pop-up window, in which the prompt information may be presented in text form. In addition, the pop-up window may also carry a selection control for the user to choose "agree" or "disagree" to provide personal information to the electronic device.
[0039] It is understandable that the above notification and the process of obtaining user authorization are merely illustrative and do not constitute a limitation on the implementation of the present disclosure. Other methods that meet relevant laws and regulations may also be applied to the implementation of the present disclosure.
[0040] As mentioned above, the release phase of the current application is not only usually time-consuming and requires a lot of manual operations, but also poses a great threat to the stability of online services when problems occur in the release. In particular, for recommendation platforms, the R&D process of recommendation platforms is usually carried out according to business needs. The participants of each business need can be regarded as an agile R&D team focusing on a fixed goal, and there are multiple teams advancing in parallel. The delivery goal of these teams is to go online, which may be involved in a routine release or an emergency release. When participating in a routine release, all teams need to form a virtual big team to integrate the work of each small team into a release plan. Such R&D characteristics also cause many problems in the release phase of the recommendation platform. Therefore, there is an urgent need for an application update method that can achieve efficient and stable automatic update of application versions.
[0041] In order to solve the above problems, an embodiment of the present disclosure provides an application updating method. It should be noted that the application updating method described in the embodiment of the present disclosure can be applied to a variety of application updating scenarios, and is particularly suitable for the release scenario of the recommendation platform.
[0042] Figure 1 The implementation process of the application updating method described in the embodiment of the present disclosure is shown. Figure 1 As shown, the application updating method described in the embodiment of the present disclosure includes the following steps:
[0043] At step 110, at least one application update request is received.
[0044] In some embodiments of the present disclosure, the application update request may include: at least one update content and a coupling relationship between the at least one update content and other application content. In some other embodiments of the present disclosure, the application update request may further include: a test list corresponding to the at least one update content and a rollback strategy.
[0045] In step 120, the at least one application update request is grouped based on the coupling relationship between the update content included in the at least one application update request and other application content to obtain at least one application update request group.
[0046] In step 130, for each application update request group, an application update plan corresponding to each application update request group is determined based on the update content contained therein and the coupling relationship between the update content and other application content.
[0047] In step 140, the application program update plan corresponding to each application program update request group is executed respectively in units of the application program update request group.
[0048] Each step of the above-mentioned application updating method will be described in detail below with reference to specific examples and drawings.
[0049] For the above step 110, the above update content defines the specific online actions corresponding to the application update request, which may specifically include: configuration update, application program interface (API) update, work order update, online service update, offline task update, backend service update and at least one of the front-end update.
[0050] In addition, as mentioned above, for R&D promoted according to business needs, each business need can be handled by an agile R&D team, while for the same application, there may be multiple teams working in parallel. Although the above multiple teams work independently, their work objects are not necessarily independent, but there may be a certain coupling relationship, or it can also be called a dependency relationship. For example, the work content of the first team is to update configuration 1, offline task 1, and backend service 1 based on business need A. Moreover, the execution of backend service 1 in the business chain of the application not only needs to rely on configuration 1 and offline task 1, but also needs to rely on the execution result of backend service 2. Then, in the above example, the coupling relationship between the above backend service 1 and other application content includes dependence on configuration 1, offline task 1, and backend service 2. In this case, if there is another second team whose work content is to update backend service 2 based on business need B, there is a certain coupling relationship between the work content of the above first team and the second team.
[0051] In some embodiments of the present disclosure, the coupling relationship between the at least one update content and other application content can be defined by a domain specific language (DSL). In this way, each update content can be abstracted as a node, and the coupling relationship between the nodes can be defined by the branch relationship between the nodes.
[0052] In addition, in an embodiment of the present disclosure, the above-mentioned test list includes at least one check item for testing whether the new version of the application can meet expectations after it is launched. Normally, when the new version of the application is tested based on the test list after it is launched and each check item in the test list passes, it can be considered that the new version of the application meets expectations after it is launched. If it is found that one or more check items in the test list have not passed after the new version of the application is tested based on the test list after it is launched, it can be considered that the new version of the application does not meet expectations after it is launched.
[0053] Further, in the embodiments of the present disclosure, the rollback strategy refers to the specific operation steps of performing a version rollback operation when it is determined that the new version of the application does not meet the expected conditions after it is launched. Generally, when the specific launch action is determined, the rollback strategy corresponding to the launch action can also be determined.
[0054] Therefore, when the party making the request submits an application update request, in addition to submitting at least one update content, they may further submit the coupling relationship between the at least one update content and other application content, the test list corresponding to the at least one update content, and the rollback strategy.
[0055] It should be noted that, in addition to the above content, the application update request also specifies the impact scope of each update content. The above impact scope specifically defines which specific links in the entire application will be affected after the current application update is executed.
[0056] With respect to the above step 120, as mentioned above, for R&D carried out according to business needs, each need may be handled by a separate team, while multiple teams may simultaneously carry out parallel work on the same application. Moreover, there may be a certain coupling relationship between the work objects of the above multiple teams. Therefore, when releasing an application, whether an application update request submitted by a team meets expectations may affect application update requests submitted by other teams. Therefore, considering that application update requests submitted based on different business needs may affect each other, in some embodiments of the present disclosure, the specific method of grouping the at least one application update request based on the coupling relationship between the update content contained in at least one application update request and other application content may include: dividing the application update requests to which the update content with a coupling relationship in the update content contained in at least one application update request belongs into the same application update request group, so as to obtain the at least one application update request group. Each application update request group is used as the minimum unit of application version update by the above grouping method. In this way, after the application is released, even if a certain application update request group does not meet expectations after the update, it will not affect the update of other application update request groups, and only the application update request group that does not meet expectations needs to be rolled back to eliminate the impact.
[0057] In an embodiment of the present disclosure, the application update request can be grouped based on a graph. Specifically, the above grouping method can refer to Figure 2 ,include:
[0058] In step 210, each of the at least one application program update requests is abstracted into a node.
[0059] In step 220, for each first node in the at least one node, the following operations are performed respectively: in response to determining that there is a coupling relationship between the update content contained in the first node and the update content contained in other second nodes, an edge from the second node to the first node is established.
[0060] After performing the above operations for each node respectively, a node dependency graph including at least one dependency subgraph can be obtained. Generally, the node dependency graph can be a directed acyclic graph (DAG).
[0061] In step 230, based on the node dependency graph, the nodes corresponding to the dependency subgraphs contained therein are grouped into one group, thereby obtaining the at least one application update request group, wherein each dependency subgraph may correspond to one application update request group.
[0062] It can be seen that after the dependency subgraphs as the minimum update units in the node dependency graph are sorted out, a release operation of an application can be changed to execute operations on multiple dependency subgraphs. And the rollback operation on a dependency subgraph will not affect other parts of the node dependency graph.
[0063] With respect to the above step 130, for each application update request group, an application update plan corresponding to each application update request group may be generated based on the dependency subgraph corresponding to the current application update request group in the above node dependency graph and the update content contained therein.
[0064] In some embodiments of the present disclosure, the above step 130 may further include: for each application update request group, based on the test list corresponding to the update content contained therein and the rollback strategy, respectively determine the test list and rollback plan corresponding to each application update request group. In this scenario, next, the above step 140 may further include: based on the test list corresponding to each application update request group, respectively determine whether the execution result of the application update plan corresponding to each application update request group meets expectations; in response to determining that the execution result of the application update plan corresponding to a certain application update request group does not meet expectations, execute the rollback plan corresponding to the above application update request group.
[0065] In order to further improve the stability of the application release process, on the basis of the above-mentioned application update method, the role of Quality Assurance (QA) can be further introduced in multiple links to test the submitted application update request and the generated application update plan, test list and rollback plan through the integrated testing platform, so as to eliminate the problems that may occur in the release process in advance and effectively prevent release accidents. Specifically, in the embodiments of the present disclosure, the above-mentioned QA can be an actual application tester or application manager, or a virtual role with application testing capabilities. The above-mentioned QA can check the submitted application update request and the generated application update plan, test list and rollback plan based on a series of established rules.
[0066] Specifically, in some embodiments of the present disclosure, after receiving at least one application update request, the application update method may further include: forwarding the at least one application update request to an integrated test platform for testing; receiving the test result for the at least one application update request; for the application update request that passes the test, continuing to perform the step of grouping the at least one application update request based on the coupling relationship between the update content contained in the at least one application update request and other application content as described in step 120; and for the application update request that does not pass the test, the party proposing the request may be instructed to resubmit the application update request within a specified first deadline. In an embodiment of the present disclosure, the above test may be performed by QA through an integrated test platform. The first deadline may be a set deadline for submitting an application update request.
[0067] In some other embodiments of the present disclosure, before executing the application update plan corresponding to each application update request group respectively, the application update method may further include: forwarding the application update plan corresponding to each application update request group to the integrated test platform for testing; receiving the test results of the application update plan corresponding to each application update request group; for the application update plan that passes the integrated test, continuing to execute the steps of executing the application update plan corresponding to each application update request group respectively in units of the application update request group; and for the application update plan that fails the integrated test, instructing the application update request group administrator to resubmit the application update plan within the specified second deadline. In the embodiment of the present disclosure, the centralized test may also be performed by QA through the integrated test platform. The second deadline is the set deadline for submitting the application update plan. It should be noted that, in addition to the application update plan corresponding to each application update request group, the test list and rollback plan corresponding to each application update request group submitted to QA for testing may also be included. When the test list and rollback plan corresponding to an application update request group do not meet expectations, the application update request group administrator may also be instructed to make adjustments within the specified second deadline.
[0068] The specific implementation process of the above application updating method will be described in detail below with reference to the accompanying drawings and specific examples.
[0069] For a more intuitive and understandable explanation, the following detailed description borrows the concept of Agile Release Train (ART) to compare the release operation of an application to the departure operation of a train.
[0070] Specifically, in the embodiments of the present disclosure, the release of an application is analogized to the process of a train from ticket sales to departure, and each of the above application update request groups is analogized to a carriage on the train. It can be understood that in the embodiments of the present disclosure, a carriage corresponds to the smallest unit of application update, and there is no dependency or coupling relationship between the carriages. In addition, the various time periods of the release of the application are mapped to the ticket sales period of the train (the time period allowing the demand provider to submit an application update request), the ticket sales deadline (the above-mentioned first deadline), the ticket inspection period (the time period for testing the application update request and the generated application update plan, test list and rollback plan, etc.), the ticket inspection deadline (the above-mentioned second deadline), and the departure time (the time point when the application goes online).
[0071] At the same time, in order to ensure the safe departure of the train, each train is also equipped with a train manager (also called application release manager), whose main responsibility is to be responsible for the overall release environment of the application, specifically responsible for organizing the departure, setting the above-mentioned time nodes, reviewing the rationality of the departure plan, etc. In addition, each carriage should also be equipped with a carriage manager (that is, the application update request group manager), whose main responsibility is to be responsible for the content related to the application update request group, specifically reviewing the application update plan, test list and rollback plan of the application update request group corresponding to its carriage. In addition, as mentioned above, in the release process of an application, the participation of the demand proposer and QA and other roles is also required. Among them, the demand proposer not only includes the proposer of the business demand, but also can include the research and development personnel who carry out technical development for the proposed demand, and they jointly complete the work of submitting the application update request. In addition, under normal circumstances, the types of application updates basically include: routine launch, emergency launch, etc. Among them, routine launch means that the application update is carried out according to the routine schedule, for example, a release is carried out every fixed period, etc. And emergency launch usually means an emergency release to solve certain problems of the application. In the embodiments of the present disclosure, the same implementation process can be used for routine and emergency online launches, while the update content of the application carried by the train is simplified. For example, for an emergency online launch, the train may only include one carriage, and the key time periods corresponding to the train, such as the ticket sales period and ticket inspection period, will be set to shorter time periods, so as to achieve the goal of emergency online launch.
[0072] Figure 3 A specific example of the application update process described in an embodiment of the present disclosure is shown. Figure 3 The application update process shown can be applied to both routine and emergency application launches. Figure 3 As shown, the application update process may include the following steps:
[0073] In step 310, the application update platform receives the information of the upcoming train registered by the train operator.
[0074] In the embodiments of the present disclosure, the above train information may include: the identification of the application to be released, the version of the application to be released, and the various time nodes involved in the application release process. The above various time points may include: the ticket sales period, the ticket sales deadline, the ticket inspection period, the ticket inspection deadline, and the departure time of the train. It can be understood that for routine online, the above various time nodes are the scheduled time nodes for routine online; and for emergency online, the above various time nodes are temporarily determined emergency time nodes.
[0075] Next, the application update platform may forward the above train information to the project management platform, and the project management platform may release the train information to the requesting party.
[0076] In step 320, during the ticketing period, the application update platform receives the application update request submitted by the demander through the project management platform.
[0077] As described above, in an embodiment of the present disclosure, the above-mentioned application update request may include: at least one update content, a coupling relationship between the above-mentioned at least one update content and other application content, a test list corresponding to the above-mentioned at least one update content, and a rollback strategy.
[0078] In step 330, during the ticket checking period, the application update platform receives the test results of the QA for each application update request to be boarded through the integrated test platform.
[0079] Specifically, for application update requests that are determined to meet expectations after testing, tickets will be issued, which means boarding will be allowed; for application update requests that are determined to not meet expectations after testing, the application update platform will instruct the requester to make modifications through the project management platform and modify them to meet expectations before the above-mentioned ticket sales deadline, otherwise boarding will not be allowed.
[0080] In step 340, after the ticketing deadline, the application update platform groups the application update requests that meet expectations to obtain at least one application update request group.
[0081] Specifically, as described above, the application update platform can group the application update requests to which the update contents with coupling relationship are attached in the update contents included in the application update requests into the same application update request group, thereby obtaining at least one application update request group. It can be considered that each application update request group corresponds to a carriage of the train. The above operation can also be understood as allocating a carriage to the application update request.
[0082] Further, the application update platform will also assign the train administrators of each train compartment. In actual application, the train administrator can also assign the train administrators of each train compartment through the application update platform.
[0083] In step 350, for each application update request group, the application update platform will generate an application update plan, a test list, and a rollback plan corresponding to each application update request group based on the update content contained in each application update request in the current group, the coupling relationship between each update content and other application content, the test list corresponding to each update content, and the rollback strategy.
[0084] In step 360, the application update platform receives the test results of the application update plan, test list and rollback plan corresponding to each car from QA through the integrated test platform.
[0085] Specifically, for application update request groups that are determined to meet expectations after testing, the boarding action will be immediately deemed to have been completed, and no other processing is required, and the train can just wait for departure; for application update request groups that are determined to not meet expectations after testing, the car manager of the corresponding car will be instructed to adjust the application update plan, test list, and rollback plan, and modify them to meet expectations before the above-mentioned ticket checking deadline, otherwise boarding will not be allowed.
[0086] In addition to testing the application update plan, test list, and rollback plan corresponding to each application update request group to determine whether the update result meets expectations, the above test will also include testing whether there are conflicts between the various application update request groups, such as different updates for the same update content, etc. Multiple application update request groups with conflicts can be merged before subsequent processing.
[0087] It should be noted that ticket purchase is still supported during the above-mentioned ticket inspection period, which means that the party making the request is allowed to submit a new application update request, but ticket purchase requires the consent of both the train manager and the manager of the affected carriage.
[0088] In step 370, after the ticket checking deadline, the project management platform will execute the departure operation: that is, submitting the expected application update request groups to the operation and maintenance platform, which will execute the application update plan corresponding to each application update request group based on the application update request group.
[0089] In an embodiment of the present disclosure, the operation and maintenance platform may execute the application update plan corresponding to each application update request group in parallel, taking the application update request group as a unit.
[0090] Furthermore, the operation and maintenance platform will also determine whether the execution results of the application update plan corresponding to each application update request group meet expectations based on the test list corresponding to each application update request group; in response to determining that the execution results of the application update plan corresponding to a certain application update request group do not meet expectations, execute the rollback plan corresponding to the above application update request group.
[0091] It should be noted that in Figure 3In the application update method shown, at each stage the application update platform will further return the status corresponding to each application update request, such as submission test, integration test, online launch, etc., to the project management platform to notify the party proposing the application update request of the execution progress, thereby improving the user experience when updating the application.
[0092] Figure 4 An example of using the application updating method described in the embodiment of the present disclosure to update an application is shown. Figure 4 The execution status of the ticket sales period, ticket inspection period and several stages after departure is shown.
[0093] Specifically, during the ticketing period, multiple demanders submit application update requests to the project management platform. Among them, the update content involved in request 1 includes: configuration 1, offline task 1, offline task 2, backend service 1, backend service 2 and backend service 3. Among them, the coupling relationship includes: backend service 1, backend service 2 and backend service 3 all depend on configuration 1, offline task 1, offline task 2 (wherein, the coupling relationship between configuration, offline task and backend service is not shown in the figure); and backend service 2 also depends on backend service 4 and backend service 5. The update content involved in request 2 includes: configuration 2, offline task 3 and backend service 1. The update content involved in request 3 includes: backend service 4. The update content involved in request 4 includes: backend service 6.
[0094] During the ticket inspection period, QA first tests the above four application update requests. The test results show that requests 1, 3, and 4 meet expectations and tickets can be issued; while request 2 does not meet expectations and boarding is rejected.
[0095] Next, the application update platform groups the expected requests 1, 3, and 4 according to the coupling relationship between the update contents contained in each request. Among them, since the backend service 2 in request 1 depends on the backend service 4 in request 3, request 1 and request 3 are assigned to the same car - car 1. Request 4 is assigned to a separate car - car 2.
[0096] Then, the application update platform generates the application update plan, test list, and rollback plan for car 1 according to the update content and coupling relationship contained in request 1 and request 3; and generates the application update plan, test list, and rollback plan for car 2 according to the update content and coupling relationship contained in request 4. Figure 4It can be seen that the application update plan corresponding to Carriage 1 includes: first execute the update of configuration 1, offline task 1, and offline task 2 in parallel; then execute the update of backend service 4; finally execute the update of backend service 1, backend service 2, and backend service 3 in parallel. The rollback plan corresponding to Carriage 1 includes: first execute the inverse operation of the update of configuration 1, offline task 1, and offline task 2 in parallel; then execute the inverse operation of the update of backend service 1, backend service 2, backend service 3, and backend service 4 in parallel (not shown in the figure). The application update plan corresponding to Carriage 2 includes: execute the update of backend service 6. The rollback plan corresponding to Carriage 2 includes: execute the inverse operation of the update of backend service 6 (not shown in the figure).
[0097] After the application update plan, test list and rollback plan corresponding to the above two carriages are tested and passed, you can wait for departure.
[0098] After departure, the application update platform can send the application update plan, test list and rollback plan corresponding to the above two cars to the operation and maintenance platform for execution. The operation and maintenance platform can execute the application update plan corresponding to the two cars in parallel, and test them based on the test lists corresponding to the two cars respectively. After testing, it can be determined that the application update plan corresponding to car 1 meets expectations after execution, while the application update plan corresponding to car 2 does not meet expectations after execution. It is necessary to further perform the reverse operation of the backend service 6 update according to the rollback plan corresponding to car 2. Then, the update process of this application can be ended.
[0099] It can be seen that in the above-mentioned application update method, each carriage can form a train for departure, but the update or rollback operation of the application is performed on a per-carriage basis. If a problem occurs in any carriage, the entire train will not be affected. In other words, in the above-mentioned application update method, the update or rollback operation of the application is performed on a per-application update request group basis. If a problem occurs in any application update request group, it will not affect other application update request groups.
[0100] In addition, in the above-mentioned application update method, only one application needs to be submitted for the application update operation, and the application update platform can host the subsequent process. The party proposing the application update only needs to be responsible for clarifying the change content, coupling relationship, test list and rollback strategy of the part that it changes. The application update platform can automatically determine the application update request grouping, and separately determine the application update plan, test list and rollback plan for each application update request grouping, which greatly reduces labor costs and greatly improves the efficiency of application release.
[0101] Moreover, during the above-mentioned application update process, the business management platform and the application update platform are connected, which can cover all online change requirements. When the status is transferred, the form filling can be automatically triggered and log records can be generated for all operations.
[0102] It can be understood that currently, applications can be executed in a variety of environments. Therefore, in the embodiment of the present disclosure, the above-mentioned application update method can also be applied to various different application execution environments. Specifically, the application update method described in the embodiment of the present disclosure can further include: receiving application execution environment information. The above-mentioned application execution environment information can be obtained from the operation and maintenance platform. In this case, the above-mentioned grouping of the at least one application update request based on the coupling relationship between the update content contained in the at least one application update request and other application content can include: grouping the at least one application update request based on the coupling relationship between the update content contained in the at least one application update request and other application content and the application execution environment information. That is, the application execution environment can be considered when grouping the application update request. In addition, further in the process of determining the application update plan corresponding to each application update request group based on the update content contained in each application update request group and the coupling relationship between the update content and other application content, the application update plan corresponding to each application update request group can also be determined based on the update content contained therein, the coupling relationship between the update content and other application content and the application execution environment information. In this way, by obtaining and considering the application execution environment information in the release link of the application, the application update method can be applied to various environments.
[0103] Corresponding to the above-mentioned application updating method, an embodiment of the present disclosure further provides an application updating system. Figure 5 The internal structure of the application update system is shown in Figure 1. Figure 5 As shown, the application updating system described in the embodiment of the present disclosure may include: an application updating platform 510 , a project management platform 520 , and an operation and maintenance platform 530 .
[0104] The project management platform 520 is used to receive an application update request submitted by a requester, and forward the received application update request to the application update platform 510 .
[0105] The above-mentioned application update platform 510 is used to receive application update requests submitted by the demand proposer from the project management platform 520; group the application update requests to obtain at least one application update request group; for each application update request group, determine the application update plan corresponding to each application update request group according to the update content contained in each application update request in the current group and the coupling relationship between each update content and other application content; and submit the application update plan corresponding to each application update request group to the operation and maintenance platform 530.
[0106] The operation and maintenance platform 530 is used to execute the application update plan corresponding to each application update request group based on the application update request group.
[0107] It should be noted that, in the embodiment of the present disclosure, the above-mentioned operation and maintenance platform 530 may include multiple ones, and each operation and maintenance platform 530 corresponds to the execution environment of an application. In the application, the above-mentioned operation and maintenance platform 530 may first report its own application execution environment information to the above-mentioned application update platform 510. In this way, the above-mentioned application update platform 510 will group the application update requests based on the application execution environment information reported by the operation and maintenance platform 530, and generate an update plan, test list and rollback plan corresponding to each application execution environment information for each application update request group based on the application execution environment information reported by the operation and maintenance platform 530, and finally send the corresponding update plan, test list and rollback plan of each application update request group to the corresponding operation and maintenance platform based on the application execution environment information reported by the operation and maintenance platform 530. In this way, the application update system described in the embodiment of the present disclosure will be applicable to application releases under a variety of application execution environments.
[0108] In some embodiments of the present disclosure, the application update system may further include: an integrated test platform 540, which is used to test the application update request and the application update plan corresponding to each application update request group. The application update platform 510 only performs corresponding subsequent operations on the application update request that has been tested and meets expectations and the application update plan corresponding to each application update request group.
[0109] In some embodiments of the present disclosure, the above-mentioned application update platform 510 can be further used to determine, for each application update request group, the test list and rollback plan corresponding to the above-mentioned application update request group according to the test list and rollback strategy corresponding to the update contents in the current group.
[0110] In this case, the operation and maintenance platform 530 may be further used to execute a rollback plan corresponding to an application update request group in response to determining that an application update plan corresponding to an application update request group does not execute as expected based on the test list corresponding to each application update request group.
[0111] In an embodiment of the present disclosure, the operation and maintenance platform 530 may execute the application update plan corresponding to each application update request group in parallel in units of application update request groups.
[0112] Figure 6 The internal structure of the application update platform described in the embodiment of the present disclosure is shown. Figure 6 As shown, the above application update platform may include:
[0113] The request receiving module 610 is used to receive at least one application update request submitted by the demand proposer from the project management platform 520;
[0114] A grouping module 620, configured to group the at least one application update request based on a coupling relationship between update content included in the at least one application update request and other application content, to obtain at least one application update request group;
[0115] A plan generating module 630 is used to determine, for each application update request group, the application update plan corresponding to each application update request group according to the update content contained in each application update request in the current group and the coupling relationship between each update content and other application content; and
[0116] The plan submission module 640 is used to submit the application update plan corresponding to each application update request group to the operation and maintenance platform 530.
[0117] In the embodiment of the present disclosure, the plan generation module 630 can be further used to determine the test list and rollback plan corresponding to each application update request group according to the test list and rollback strategy corresponding to each updated application content in the current group. In this case, the plan submission module 640 can be further used to submit the test list and rollback plan corresponding to each application update request group to the operation and maintenance platform 530.
[0118] Based on the same inventive concept, corresponding to any of the above-mentioned embodiments, the present disclosure also provides an electronic device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the application updating method described in any of the above embodiments is implemented.
[0119] Figure 7 A more specific hardware structure diagram of an electronic device provided in this embodiment is shown, and the device may include: a processor 2010, a memory 2020, an input / output interface 2030, a communication interface 2040, and a bus 2050. The processor 2010, the memory 2020, the input / output interface 2030, and the communication interface 2040 are connected to each other in communication within the device through the bus 2050.
[0120] The processor 2010 can be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this specification.
[0121] The memory 2020 can be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage device, dynamic storage device, etc. The memory 2020 can store an operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented by software or firmware, the relevant program codes are stored in the memory 2020 and are called and executed by the processor 2010.
[0122] The input / output interface 2030 is used to connect input / output devices to realize information input and output. The input / output devices can be configured in the device as components, or can be externally connected to the device to provide corresponding functions. The input devices can include microphones, various sensors, etc., and the output devices can include displays, speakers, vibrators, indicator lights, etc.
[0123] The communication interface 2040 is used to connect a communication module (not shown) to realize communication interaction between the device and other devices. The communication module can realize communication through a wired mode (such as USB, network cable, etc.) or a wireless mode (such as mobile network, WIFI, Bluetooth, etc.).
[0124] The bus 2050 includes a path that transmits information between the various components of the device (eg, the processor 2010, the memory 2020, the input / output interface 2030, and the communication interface 2040).
[0125] It should be noted that, although the above device only shows the processor 2010, the memory 2020, the input / output interface 2030, the communication interface 2040, and the bus 2050, in the specific implementation process, the device may also include other components necessary for normal operation. In addition, it can be understood by those skilled in the art that the above device may also only include the components necessary for implementing the embodiments of the present specification, and does not necessarily include all the components shown in the figure.
[0126] The electronic device of the above embodiment is used to implement the corresponding application updating method in any of the above embodiments, and has the beneficial effects of the corresponding method embodiment, which will not be described in detail here.
[0127] Based on the same inventive concept, corresponding to any of the above-mentioned embodiment methods, the present disclosure also provides a non-transitory computer-readable storage medium, wherein the non-transitory computer-readable storage medium stores computer instructions, and the computer instructions are used to enable the computer to execute the application update method described in any of the above embodiments.
[0128] The computer-readable medium of this embodiment includes permanent and non-permanent, removable and non-removable media, and information storage can be implemented by any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, read-only compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device.
[0129] The computer instructions stored in the storage medium of the above embodiments are used to enable the computer to execute the task processing method described in any of the above embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.
[0130] Those skilled in the art should understand that the discussion of any of the above embodiments is merely illustrative and is not intended to imply that the scope of the present disclosure (including the claims) is limited to these examples. Based on the concept of the present disclosure, the technical features in the above embodiments or different embodiments may be combined, the steps may be implemented in any order, and there are many other variations of the different aspects of the embodiments of the present disclosure as described above, which are not provided in detail for the sake of simplicity.
[0131] In addition, to simplify the description and discussion, and in order not to make the embodiments of the present disclosure difficult to understand, the known power / ground connections to the integrated circuit (IC) chips and other components may or may not be shown in the provided figures. In addition, the device can be shown in the form of a block diagram to avoid making the embodiments of the present disclosure difficult to understand, and this also takes into account the fact that the details of the implementation of these block diagram devices are highly dependent on the platform on which the embodiments of the present disclosure will be implemented (that is, these details should be fully within the scope of understanding of those skilled in the art). Where specific details (e.g., circuits) are set forth to describe exemplary embodiments of the present disclosure, it is apparent to those skilled in the art that the embodiments of the present disclosure can be implemented without these specific details or with changes in these specific details. Therefore, these descriptions should be considered illustrative rather than restrictive.
[0132] Although the present disclosure has been described in conjunction with specific embodiments of the present disclosure, many replacements, modifications and variations of these embodiments will be apparent to those skilled in the art from the foregoing description. For example, other memory architectures (e.g., dynamic RAM (DRAM)) may use the embodiments discussed.
[0133] The embodiments of the present disclosure are intended to cover all such substitutions, modifications and variations that fall within the broad scope of the appended claims. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the embodiments of the present disclosure should be included in the scope of protection of the present disclosure.
Claims
1. A method for updating an application, comprising: Receive at least one application update request; wherein the application update request includes: at least one update content and a coupling relationship between the at least one update content and other application content; Grouping the at least one application update request based on a coupling relationship between update content included in the at least one application update request and other application content to obtain at least one application update request group; For each application update request group, determining an application update plan corresponding to each application update request group based on the update content contained therein and the coupling relationship between the update content and other application content; and The application update plan corresponding to each application update request group is executed respectively in units of the application update request group.
2. The method according to claim 1, wherein: Grouping the at least one application update request based on the coupling relationship between the update content included in the at least one application update request and other application content includes: The application update requests to which the update contents having a coupling relationship are attached in the update contents included in the at least one application update request are divided into the same application update request group to obtain the at least one application update request group.
3. The method according to claim 2, wherein: The step of grouping the application update requests to which the update contents having a coupling relationship belong among the update contents included in the at least one application update request into the same application update request group comprises: abstracting the at least one application update request into a node respectively; For each first node among the at least one node, in response to determining that the update content contained in the first node has a coupling relationship with the update content contained in another second node, establishing an edge from the second node to the first node to obtain a node dependency graph including at least one dependency subgraph; and Based on the node dependency graph, nodes corresponding to at least one dependency subgraph contained therein are respectively divided into a group.
4. The method according to claim 1, wherein: The application update request further includes: a test list corresponding to the at least one update content and a rollback strategy.
5. The method according to claim 4, further comprising: For each application update request group, determine a test list and a rollback plan corresponding to each application update request group based on the test list and rollback strategy corresponding to the update content contained therein; as well as In response to determining, based on the test list corresponding to each application update request group, that an application update plan execution result corresponding to an application update request group does not meet expectations, a rollback solution corresponding to the application update request group is executed.
6. The method according to claim 1, wherein: After receiving at least one application update request, the method further comprises: receiving a test result for the at least one application update request; For the application update request that passes the test, continue to perform the step of grouping the at least one application update request based on the coupling relationship between the update content included in the at least one application update request and other application content; and For application update requests that fail the test, the requester is instructed to resubmit the application update request within a specified first period.
7. The method according to claim 1, wherein: Before respectively executing the application program update plan corresponding to each application program update request group, the method further comprises: receiving a test result of an application program update plan corresponding to the at least one application program update request group; For the application update plan that passes the test, continue to execute the step of executing the application update plan corresponding to each application update request group in units of application update request groups; and For application update plans that fail the test, the application update request group administrator is instructed to resubmit the application update plan within a specified second period.
8. The method according to claim 1, wherein: Taking the application update request group as a unit, executing the application update plan corresponding to each application update request group separately includes: the operation and maintenance platform takes the application update request group as a unit, and executes the application update plan corresponding to each application update request group in parallel.
9. The method according to claim 1, further comprising: Receive application execution environment information; wherein, Grouping the at least one application update request based on the coupling relationship between the update content included in the at least one application update request and other application content includes: grouping the at least one application update request based on the coupling relationship between the update content included in the at least one application update request and other application content and the application execution environment information; and For each application update request group, the application update plan corresponding to each application update request group is determined based on the update content contained therein and the coupling relationship between the update content and other application content, including: for each application update request group, the application update plan corresponding to each application update request group is determined based on the update content contained therein, the coupling relationship between the update content and other application content, and the application execution environment information.
10. An application updating platform, comprising: A request receiving module, used to receive an application update request submitted by a demand proposer from a project management platform; wherein the application update request includes: at least one update content and a coupling relationship between the at least one update content and other application content; A grouping module, configured to group the at least one application update request based on a coupling relationship between update content included in the at least one application update request and other application content, to obtain at least one application update request group; a plan generation module, for determining, for each application update request group, an application update plan corresponding to each application update request group according to the update content contained in each application update request in the current group and the coupling relationship between each update content and other application content; and The plan submission module is used to submit the application update plan corresponding to each application update request group to the operation and maintenance platform, and the operation and maintenance platform executes the application update plan corresponding to each application update request group respectively based on the application update request group.
11. The device according to claim 10, wherein: The plan generation module is further used to determine, for each application update request group, a test list and a rollback plan corresponding to the application update request group according to the test list and rollback strategy corresponding to each update content in the current group; and The plan submission module is further used to submit the test list and rollback plan corresponding to each application update request group to the operation and maintenance platform.
12. An application updating system, comprising: The application update platform, project management platform and operation and maintenance platform as claimed in claim 10 or 11; wherein: The project management platform is used to receive an application update request submitted by a demander, and forward the received application update request to the application update platform; and The operation and maintenance platform is used to execute the application update plan corresponding to each application update request group respectively based on the application update request group.
13. An electronic device, comprising: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the application program updating method according to any one of claims 1 to 9 is implemented.
14. A non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to enable a computer to execute the application updating method according to any one of claims 1 to 9.
15. A computer program product, comprising computer program instructions, which, when executed on a computer, enable the computer to execute the application program updating method according to any one of claims 1 to 9.
Citation Information
Patent Citations
Application system monitoring management method and device, equipment and storage medium
CN113051134A
Application program updating method and device, equipment and storage medium
CN114035827A
Method and device for updating software version, storage medium and electronic equipment
CN115167896A
Method and apparatus for updating application program on client, and electronic device
WO2019029457A1
