An application updating method and device

Abstract

The application discloses an application updating method and device, and relates to the field of system release management of Fintech (Fintech). The method comprises the following steps: selecting a server as a first server from at least one server associated with a first front-end system; updating an application of a first version deployed in the first server into an application of a second version; testing an optimized function of the application of the second version relative to the application of the first version; establishing a second front-end system according to the first front-end system and the application of the second version; associating the second front-end system with the first server; testing a newly-added function of the application of the second version relative to the application of the first version; and if it is determined that the test is passed, determining that the application updating is successful. The method improves the verification efficiency of application updating and improves the stability of system use.

Description

Technical Field

[0001] This invention relates to the field of system release management in financial technology (Fintech), and more particularly to an application update method and apparatus. Background Technology

[0002] With the development of computer technology, more and more technologies (big data, distributed systems, blockchain, artificial intelligence, etc.) are being applied in the financial field, and the traditional financial industry is gradually transforming into Fintech. Currently, in the Fintech field, as business demands increase and standards become more stringent, the frequency and importance of adding and optimizing various system features are also rising. The canary release method used in existing system updates refers to a release method that allows for a smooth transition during software version releases. Assuming the current software version is A and the new software version is B, when a software development company releases an upgrade version of a certain software, the server controls a portion of users to start using version B; another portion of users continue to use version A. If no problems occur while using version B, all users are gradually migrated to version B.

[0003] Generally, the new version of application B differs from the old version of application A in two main ways: adjustments and optimizations, and new features. With current canary release methods, while the new version of application B is deployed on the backend server, the frontend system is always deployed with the old version of application A. Therefore, when some users are using the new version of application B, they can only test the adjustments and optimizations on the backend server, without testing the new features. This results in incomplete testing of the new version. Consequently, if version issues arise after the new version of application B is fully released on the frontend system, it will not only affect all personnel using the frontend system, but also require a thorough testing and inspection of all backend servers and the frontend system to troubleshoot the problem, leading to long operation times and low maintenance efficiency.

[0004] Therefore, the fact that the backend server has not tested the new features of the new version of the application during the application update of existing technologies is an urgent problem that needs to be solved. Summary of the Invention

[0005] This application provides an application update method and apparatus, which solves the problem in the prior art that the backend server does not test the new features added to the new version of the application during application updates.

[0006] This application provides an application update method, specifically including:

[0007] Select one server from at least one server associated with the first front-end system as the first server; update the first version of the application deployed on the first server to the second version of the application, wherein the second version of the application is the application updated from the first version of the application;

[0008] The optimized functions of the second version of the application deployed on the first server are tested relative to the first version of the application. If the test is passed, the connection between the first front-end system and the first server is disconnected.

[0009] A second front-end system is established based on the first front-end system and the second version of the application; the second front-end system is associated with the first server;

[0010] The new features added to the second version of the application deployed on the first server compared to the first version of the application are tested. If the test is passed, the application update is considered successful.

[0011] One possible implementation, after determining that the application update was successful, further includes:

[0012] Select one server from at least one server associated with the first front-end system that deploys the first version of the application, update the first version of the application to the second version of the application and test it; until all the first version of the application deployed on the at least one server associated with the first front-end system are updated to the second version of the application, and the application update is confirmed to be successful;

[0013] Update the first front-end system according to the second version of the application.

[0014] One possible implementation involves testing the new features added to the second version of the application deployed on the first server, relative to the first version of the application, including:

[0015] The second front-end system receives instructions corresponding to the newly added function;

[0016] Based on the execution result of the instruction, determine the test pass status of the newly added function in the second version of the application.

[0017] One possible implementation, after testing the new features added to the second version of the application deployed on the first server compared to the first version, further includes:

[0018] If the test fails, roll back the second version of the application deployed on the first server to the first version of the application; disconnect the association between the second front-end system and the first server; and re-establish the association between the first front-end system and the first server.

[0019] This application provides an application update device, specifically including:

[0020] The acquisition unit is used to select one server as the first server from at least one server associated with the first front-end system;

[0021] The processing unit is configured to update the first version of the application deployed on the first server to a second version of the application, wherein the second version of the application is the updated version of the first version of the application; to perform optimization function testing on the second version of the application deployed on the first server; and if the test is passed, to disconnect the first front-end system from the first server.

[0022] The processing unit is further configured to establish a second front-end system based on the first front-end system and the second version of the application; associate the second front-end system with the first server; test the newly added functions of the second version of the application deployed on the first server; and if the test is passed, determine that the application update is successful.

[0023] One possible implementation is that the processing unit is specifically used for:

[0024] Select one server from at least one server associated with the first front-end system that deploys the first version of the application, update the first version of the application to the second version of the application and test it; until all the first version of the application deployed on the at least one server associated with the first front-end system are updated to the second version of the application, and the application update is confirmed to be successful;

[0025] Update the first front-end system according to the second version of the application.

[0026] One possible implementation is that the processing unit is specifically used for:

[0027] Receive instructions corresponding to the newly added functions;

[0028] Based on the execution result of the instruction, determine the test pass status of the newly added function in the second version of the application.

[0029] One possible implementation is that the processing unit is specifically used for:

[0030] If the test fails, roll back the second version of the application deployed on the first server to the first version of the application; disconnect the association between the second front-end system and the first server; and re-establish the association between the first front-end system and the first server.

[0031] This application provides a storage medium including a program or instructions that, when executed, cause a computer to perform the method in any of the possible designs described above.

[0032] This application provides a chip connected to a memory for reading and executing software programs stored in the memory to implement any of the methods in the above-described possible designs.

[0033] The application update method and apparatus provided by this invention have the following advantages: each time a new version of the application is deployed on a backend server, the frontend system associated with the backend server is tested under both old and new application deployments. This ensures that the testing of the backend server during the application update process includes the new features of the new application, guaranteeing the completeness of the testing of the new application. It also avoids the impact on all system users due to problems with the new application after the update is completed, thereby improving the verification efficiency of the application update and enhancing the stability of the system. Attached Figure Description

[0034] Figure 1 This is a flowchart illustrating an application update method in an embodiment of this application;

[0035] Figure 2 This is a schematic diagram of an example of an application update method in this application embodiment;

[0036] Figure 3 This is a schematic diagram illustrating the work of an operator applying an update method according to an embodiment of this application;

[0037] Figure 4 This is a schematic diagram of the structure of an application update device according to an embodiment of this application. Detailed Implementation

[0038] To better understand the above technical solutions, the following will describe the above technical solutions in detail with reference to the accompanying drawings and specific implementation methods. It should be understood that the embodiments of this application and the specific features in the embodiments are detailed descriptions of the technical solutions of this application, rather than limitations on the technical solutions of this application. In the absence of conflict, the embodiments of this application and the technical features in the embodiments can be combined with each other.

[0039] With the development of computer technology, more and more technologies (big data, distributed systems, blockchain, artificial intelligence, etc.) are being applied in the financial field, and the traditional financial industry is gradually transforming into financial technology (Fintech). Figure 1 The figure shows a flowchart of an application update method in an embodiment of this application. The specific steps are described below.

[0040] Step 101: Select one server from at least one server associated with the first front-end system as the first server; update the first version of the application deployed on the first server to the second version of the application, wherein the second version of the application is the updated application of the first version of the application;

[0041] Specifically, the first server is any one of the at least one servers associated with the first front-end system. The first server is selected to deploy the new version of the application, and the original first version of the application is updated to the second version of the application. The first front-end system still deploys the first version of the application.

[0042] Step 102: Test the optimized functions of the second version of the application deployed on the first server relative to the first version of the application. If the test is passed, disconnect the first front-end system from the first server.

[0043] Specifically, the adjustment and optimization functions of the second version application are tested on the first server in conjunction with the first front-end system. The test content includes: (1) checking whether there are any abnormalities in the log records of the first server; (2) verifying whether the results of the adjustment and optimization of the second version application match the results of the first version application. When there are no abnormalities in the log records of the first server and the results of the second version application match the results of the first version application, the test is deemed to have passed, indicating that the first server in the backend can be compatible with the first front-end system that deploys the first version application after deploying the second version application. The association between the first front-end system and the first server is then disconnected.

[0044] More specifically, if the test fails, it indicates that there is a problem with the deployed second version of the application. The second version of the application deployed on the first server is rolled back to the first version of the application, and the problem in the second version is detected and fixed before the second version of the application is retested.

[0045] Step 103: Establish a second front-end system based on the first front-end system and the second version of the application; associate the second front-end system with the first server;

[0046] Specifically, the web page files of the first front-end system contain the first front-end web page directory. The first front-end web page directory is determined in advance based on the first front-end system so that when a group of operators are called to verify and test the new version of the application during the application update process, a second front-end system can be established based on the first front-end web page directory of the first front-end system and the second version of the application without affecting the original first front-end system. The verification and testing of the new version of the application can then be carried out by using the second front-end system.

[0047] Step 104: Test the new features added to the second version of the application deployed on the first server compared to the first version of the application. If the test is passed, the application update is confirmed to be successful.

[0048] Specifically, at least one operator is called upon to use the second front-end system, and the newly added features in the second version of the application are tested based on the results of the operator's execution of the second front-end system.

[0049] More specifically, a certain percentage of the total number of operators is pre-set as the number of operators using the second front-end system to test the new features of the second version of the application. When operators log into the first front-end system, the system calls upon a corresponding number of operators to use the second front-end system based on the set number of operators. The calling method includes two options: automatic calling based on a certain percentage of operators, and manual assignment of specific operators by system administrators based on a set percentage of operators for verification. One method can be selected based on the actual situation. For example, the system automatically calls upon 5% of the operators to use the second front-end system to test the new features of the second version of the application.

[0050] More specifically, after confirming that the optimization function test of the second version of the application deployed on the first server has passed, the status of the first server is set to grayscale; the status of the first server is checked at regular intervals, for example, every 5 minutes. When the status of the first server is checked to be grayscale, 5% of the operators are called to use the second front-end system.

[0051] Specifically, when testing new features, the testing includes: (1) checking whether there are any abnormalities in the log records of the first server; (2) verifying whether the result of executing the new features of the second version of the application matches the preset result; and (3) checking whether there are any abnormalities in the display status of the second front-end system. Once the test is confirmed to be passed, the second version of the application is confirmed to have been successfully updated.

[0052] For example, in the first scenario: check the logs of the first server. If an anomaly is recorded in the logs, verify that there is a problem with the new features added to the second version of the application.

[0053] The second scenario: Pre-set the input information and output results for the new function of the second version of the application, then input and execute the set input information through the second front-end system, and check whether the execution result is consistent with the preset output result. If they are consistent, it is verified that the new function of the second version of the application is fine; if they are inconsistent, it is verified that the new function of the second version of the application has a problem.

[0054] The third scenario: Check the webpage display status of the second front-end system to see if it is empty or if there are formatting errors, garbled characters, etc. If any of these conditions are present, then the newly added function of the second version of the application has a problem; if none of these conditions are present, then the newly added function of the second version of the application has no problem.

[0055] More specifically, after confirming that the application update is successful, disconnect the association between the second front-end system and the first server; and establish the association between the first front-end system and the first server, wherein the application deployed on the first server is the second version of the application.

[0056] More specifically, when it is determined that the test of the new feature has failed, the status of the first server is changed from gray-scale to gray-scale verification failed, the second version of the application deployed on the first server is rolled back to the first version of the application; the association between the second front-end system and the first server is disconnected; the association between the first front-end system and the first server is re-established, and a certain proportion of the operators of the second front-end system used to test and deploy the second version of the application are recalled to continue using the first front-end system, so that the problems of the second version of the application can be detected and fixed before the second version of the application is re-released.

[0057] Step 105: Select a server from at least one server that is associated with the first front-end system and deploys the first version of the application, update the first version of the application to the second version of the application and test it; until all the first version of the application deployed on the at least one server associated with the first front-end system is updated to the second version of the application, and the application update is confirmed to be successful; update the first front-end system according to the second version of the application.

[0058] Specifically, once all backend servers have deployed the second version of the application and passed testing of the adjusted, optimized, and newly added features of the second version, the first frontend system is updated based on the second version. A certain percentage of the personnel who tested the new features of the second version are then recalled to continue using the first frontend system. In other words, after all backend servers have completed the application update, the first frontend system deploying the first version is used for a full release of the second version of the application, and a certain percentage of the personnel used to test the second frontend system are recalled.

[0059] This method enables a smooth transition between old and new application versions, ensuring that both the backend server and the frontend system are tested and verified during the application update process. The verification includes the new features added in the new version, preventing any issues with the new version from affecting all staff using the frontend system after the update is complete. This significantly reduces the impact of the new application release on system stability and improves the verification efficiency of the application update.

[0060] During the execution of steps 101-105 above, there are two ways to create storage space for the establishment of the second front-end system and the verification test of the first server and the second front-end system.

[0061] In the first approach, all backend servers are located under the production domain. A new first domain is created, which points to the first frontend webpage directory and the first server, and is used to independently deploy the second version of the application. An independent Nginx service can also be deployed on the first domain to achieve load balancing of storage space during use.

[0062] More specifically, when the first server is pointed to by the newly created first domain name, the second version of the application is deployed on the first server, and the adjustment and optimization functions of the second version of the application are tested in conjunction with the first front-end system. The test content includes: (1) checking whether there are any abnormalities in the log records of the first server; (2) verifying whether the results of the adjustment and optimization of the second version of the application match the results of the first version of the application; if the test is confirmed to be passed, the association between the first front-end system and the first server is disconnected. The second front-end system is established based on the first front-end webpage directory pointed to by the first domain name and the second version of the application; the second front-end system is associated with the first server; the status of the first server is set to grayscale; the status of the first server is checked at regular intervals. When the status of the first server is detected to be grayscale, a certain proportion of operators are called to use the second front-end system to test the new functions of the second version of the application. When the test of the new functions is passed, the newly created first domain name is removed from the first server where the second version of the application has been deployed, and the original domain name is pointed to the first server again; and then any one of the back-end servers where the second version of the application has not been deployed, such as the second server, is selected, and the newly created first domain name is pointed to the storage address of the second server. At the same time, the original domain name is removed from the second server, and the second version of the application is deployed on the second server. Then, the status of the first server was changed from gray-scale to gray-scale verification passed. This process continued until all servers deploying the second version of the application were redirected from the original domain name, and then the first front-end system was updated according to the second version of the application.

[0063] The second approach involves creating a new space under the original production domain of the backend server to store the first frontend webpage directory and to distinguish the space of the first server it points to from the spaces of other servers.

[0064] More specifically, when the first server is moved from its original storage space to a newly created space, the second version of the application is deployed on the first server. The adjusted and optimized functions of the second version of the application are tested in conjunction with the first front-end system. If the test is successful, the association between the first front-end system and the first server is disconnected. A second front-end system is established based on the first front-end webpage directory and the second version of the application stored in the newly created space. The second front-end system is then associated with the first server. The status of the first server is set to grayscale. The status of the first server is checked periodically. When the status of the first server is detected as grayscale, a certain proportion of operators are called upon to use the second front-end system to test the newly added functions of the second version of the application. When the test of the newly added functions is successful, the first server with the second version of the application deployed is moved back from the newly created space to its original storage space. Then, any one of the backend servers without the second version of the application deployed, such as the second server, is selected, moved from its original storage space to the newly created space, and the second version of the application is deployed on the second server. The status of the first server is then changed from grayscale to grayscale verification successful. This process continues until all servers with the second version of the application deployed are moved back to their original storage spaces, and then the first front-end system is updated according to the second version of the application.

[0065] Figure 2 The figure shows a schematic flowchart of an application update method in an embodiment of this application. The specific steps are as follows.

[0066] Step 201: Release begins;

[0067] Step 202: Deploy the second version of the application on any of the backend servers;

[0068] Step 203: Test and adjust the optimization function. If the test passes, proceed to step 204; if the test fails, proceed to step 205.

[0069] Step 204: Determine the second front-end system;

[0070] Specifically, the web page files of the first front-end system contain a first front-end web page directory. The first front-end web page directory is determined in advance based on the first front-end system. The second front-end system is built based on the first front-end web page directory of the first front-end system and the second version of the application. The new version of the application is verified and tested by using the second front-end system.

[0071] Step 205: Revert to the first version of the application;

[0072] Step 206: Set the status of this server to grayscale;

[0073] Specifically, after the server's adjustment and optimization functions have been tested and approved, the server's status is set to grayscale.

[0074] Step 207: Invite a small percentage of operators to use the second front-end system;

[0075] Specifically, we began testing and verifying the new features in the second version of the application, asking a small number of staff to use the second front-end system, and testing and verifying it together with the first server that deployed the second version of the application.

[0076] Step 208: Verify the new feature. If the test passes, proceed to step 210; if the test fails, proceed to step 209.

[0077] Step 209: Set the server status to "Verification Failed" and revert to the first version of the application, recalling a small percentage of the operators;

[0078] Step 210: Set the status of this server to "verification passed" and continue to deploy the second version of the application on the next server;

[0079] Step 211: Check if all backend server statuses are verified successfully; if all are verified successfully, proceed to step 212; if not all are verified successfully, proceed to step 203.

[0080] Step 212: Update the first front-end system with the second version of the application;

[0081] Specifically, after all backend servers have completed the application update, the first frontend system that deployed the first version of the application will be fully released as the second version of the application, that is, the first frontend system will be updated with the second version of the application.

[0082] Step 213: Reassign a small proportion of the workforce;

[0083] Specifically, a certain percentage of the staff who were used to test and deploy the second version of the application were reassigned to the second front-end system, ensuring that all staff used the first front-end system for deploying the second version of the application.

[0084] Step 214: Posting complete.

[0085] Figure 3 The figure shows a schematic diagram of an operator performing an application update method according to an embodiment of this application. The specific process is described below.

[0086] Backend server 301 includes first server 303, second server 304 up to Nth server 305, deploying the production version. The corresponding first frontend system deploys production frontend version 309. Before the application is updated, all customer service personnel in customer service operator 302 use the first frontend system deployed with production frontend version 309. Simultaneously, the storage address of the backend server corresponding to the first frontend system is pointed to by the production domain name 308. When the application is updated, the first server 303 in backend server 301 is selected to deploy the new version, i.e., the grayscale version in the diagram. A new grayscale domain name 306 is created, independent of the original production domain name 308, to point to a certain storage space. A second frontend system is established in this storage space based on the first frontend system and the grayscale frontend version 307. Customer service personnel in customer service operator 302 are called as verifiers 310 according to a pre-set ratio to test and verify the usage of the first server 303 and the second frontend system after deploying the grayscale version. Once verification is successful, the verifiers 310 continue to test the second frontend system corresponding to the next server deployed with the grayscale version of the application.

[0087] Figure 4 This is a schematic diagram of an application update device according to an embodiment of the present application, including an acquisition unit 401 and a processing unit 402, which are described in detail below.

[0088] The acquisition unit 401 is used to select one server as the first server from at least one server associated with the first front-end system;

[0089] Processing unit 402 is used to update the first version of the application deployed on the first server to a second version of the application, wherein the second version of the application is the updated version of the first version of the application; to perform optimization function testing on the second version of the application deployed on the first server; and if the test is passed, to disconnect the first front-end system from the first server.

[0090] The processing unit 402 is further configured to establish a second front-end system based on the first front-end system and the second version of the application; associate the second front-end system with the first server; test the newly added functions of the second version of the application deployed on the first server; and if the test is passed, determine that the application update is successful.

[0091] In one possible implementation, the processing unit 402 is specifically used for:

[0092] Select one server from at least one server associated with the first front-end system that deploys the first version of the application, update the first version of the application to the second version of the application and test it; until all the first version of the application deployed on the at least one server associated with the first front-end system are updated to the second version of the application, and the application update is confirmed to be successful;

[0093] Update the first front-end system according to the second version of the application.

[0094] In one possible implementation, the processing unit 402 is specifically used for:

[0095] At least one operator is instructed to use the second front-end system, and the newly added features in the second version of the application are tested based on the results of the operator's execution of the second front-end system.

[0096] In one possible implementation, the processing unit 402 is specifically used for:

[0097] If the test fails, roll back the second version of the application deployed on the first server to the first version of the application; disconnect the association between the second front-end system and the first server; and re-establish the association between the first front-end system and the first server.

[0098] Finally, it should be noted that those skilled in the art will understand that the embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, optical storage, etc.) containing computer-usable program code.

[0099] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0100] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0101] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. An application update method, characterized in that, include: Select one server from at least one server associated with the first front-end system as the first server; The first version of the application deployed on the first server is updated to the second version of the application, while the first front-end system still deploys the first version of the application, and the second version of the application is the application updated from the first version of the application. The optimized functions of the second version of the application deployed on the first server are tested relative to the first version of the application. If the test is passed, the connection between the first front-end system and the first server is disconnected. A second front-end system is established based on the first front-end system and the second version of the application; Associate the second front-end system with the first server; The newly added functions of the second version of the application deployed on the first server are tested relative to the first version of the application. If the test is passed, the application update is considered successful. The testing of the newly added functions relative to the first version of the application includes checking whether there are any abnormalities in the log records of the first server, verifying whether the result of executing the newly added functions of the second version of the application matches the preset result, and checking whether there are any abnormalities in the display status of the second front-end system.

2. The method as described in claim 1, characterized in that, After confirming that the application update was successful, the process also includes: Select one server from at least one server associated with the first front-end system that deploys the first version of the application, update the first version of the application to the second version of the application and test it; until all the first version of the application deployed on the at least one server associated with the first front-end system are updated to the second version of the application, and the application update is confirmed to be successful; Update the first front-end system according to the second version of the application.

3. The method as described in claim 1, characterized in that, Testing the new features added to the second version of the application deployed on the first server, relative to the first version of the application, including: The second front-end system receives instructions corresponding to the newly added function; Based on the execution result of the instruction, determine the test pass status of the newly added function in the second version of the application.

4. The method according to any one of claims 1-3, characterized in that, After testing the new features added to the second version of the application deployed on the first server compared to the first version, the process also includes: If the test fails, roll back the second version of the application deployed on the first server to the first version of the application; disconnect the association between the second front-end system and the first server; and re-establish the association between the first front-end system and the first server.

5. An application update device, characterized in that, include: The acquisition unit is used to select one server as the first server from at least one server associated with the first front-end system; The processing unit is configured to update the first version of the application deployed on the first server to the second version of the application, while the first front-end system still deploys the first version of the application, and the second version of the application is the updated version of the first version of the application; to perform optimization function testing on the second version of the application deployed on the first server, and if the test is found to be passed, to disconnect the association between the first front-end system and the first server; The processing unit is further configured to establish a second front-end system based on the first front-end system and the second version of the application; The second front-end system is associated with the first server; the second version of the application deployed on the first server is tested for new functions, and if the test is passed, the application is confirmed to have been updated successfully; wherein, when the processing unit tests the second version of the application deployed on the first server for new functions, it is specifically used to check whether there are any abnormalities in the log records of the first server, verify whether the result of executing the new functions of the second version of the application matches the preset result, and check whether there are any abnormalities in the display status of the second front-end system.

6. The apparatus as claimed in claim 5, characterized in that, The processing unit is specifically used for: Select one server from at least one server associated with the first front-end system that deploys the first version of the application, update the first version of the application to the second version of the application and test it; until all the first version of the application deployed on the at least one server associated with the first front-end system are updated to the second version of the application, and the application update is confirmed to be successful; Update the first front-end system according to the second version of the application.

7. The apparatus as claimed in claim 5, characterized in that, The processing unit is specifically used for: Receive instructions corresponding to the newly added functions; Based on the execution result of the instruction, determine the test pass status of the newly added function in the second version of the application.

8. The apparatus according to any one of claims 5-7, characterized in that, The processing unit is specifically used for: If the test fails, roll back the second version of the application deployed on the first server to the first version of the application; and disconnect the association between the second front-end system and the first server. Establish the association between the first front-end system and the first server.

9. A storage medium, characterized in that, Includes a program or instruction, which, when executed, performs the method as described in any one of claims 1 to 4.

10. A chip, characterized in that, Includes a program or instruction, which, when executed, performs the method as described in any one of claims 1 to 4.

Images