CN104978191A - Application deployment method and server - Google Patents

Abstract

The present disclosure relates to an application deployment method and a server. The method includes: receiving an application deployment instruction and obtaining an application to be deployed, the application to be deployed includes source code and a configuration file, and the configuration file contains the application to be deployed Deployment directory; Obtain the test case corresponding to the application to be deployed; Compile the application to be deployed, and send the compiled application to be deployed and the test case to each business server, so that each business server The compiled application to be deployed and the test case are stored in the deployment directory, and the test case is run to test the compiled application to be deployed. In the process of automatic deployment and testing, manual intervention is not required, problems of manual deployment and testing that are prone to errors are avoided, and the efficiency of application deployment and testing is improved while reliability of application deployment and testing is ensured.

Description

Application deployment method and server

technical field

The present disclosure relates to the technical field of communications, and in particular to an application deployment method and server.

Background technique

With the widespread application of distributed systems in different industries, in the field of information technology, in order to ensure the robustness and stability of system work, service providers generally deploy applications that provide certain services in distributed systems for the general public. user use. Wherein, a distributed system often includes multiple servers for deploying one or more applications.

Contents of the invention

In order to overcome the problems existing in related technologies, the present disclosure provides an application deployment method and a server to realize automatic deployment and testing of applications in a distributed system, so as to improve the efficiency and reliability of application deployment and testing.

According to a first aspect of an embodiment of the present disclosure, an application deployment method is provided, including:

receiving an application deployment instruction, and obtaining an application to be deployed, wherein the application to be deployed includes source code and a configuration file, and the configuration file includes a deployment directory of the application to be deployed;

Obtaining a test case corresponding to the application to be deployed; compiling the application to be deployed;

Send the compiled application to be deployed and the test case to each service server, so that each service server will store the compiled application to be deployed and the test case in the deployment directory, and run The test case tests the compiled application to be deployed.

Wherein, the application deployment instruction includes the application identification, version number and description file of the application to be deployed; the acquisition of the test case corresponding to the application to be deployed includes:

Determine whether there is a historical application corresponding to the application to be deployed, where the historical application is an application whose application identifier is the same as that of the application to be deployed and whose version number is lower than the version number of the application to be deployed;

If there is a historical application corresponding to the application to be deployed, obtaining a historical description file corresponding to the historical application, where the historical description file is a description file of the historical application;

Acquire a test case corresponding to the application to be deployed according to the history description file and the description file of the application to be deployed.

Specifically, the acquiring a test case corresponding to the application to be deployed according to the history description file and the description file of the application to be deployed includes:

By comparing the historical description file with the description file of the application to be deployed, determine whether there is a difference function module in the application to be deployed that has a module function different from that of each functional module of the historical application;

If the difference function module does not exist, obtaining the test case corresponding to the historical application as the test case corresponding to the application to be deployed;

If the difference function module exists, obtain the difference test case corresponding to the difference function module, and update the test case corresponding to the historical application according to the difference test case, and use the test case corresponding to the updated historical application as A test case corresponding to the application to be deployed.

Further, the method also includes:

Before compiling the application to be deployed, receiving a compiling instruction, the compiling instruction includes operator authentication information;

The operator is authenticated according to the authentication information, and if the authentication is passed, the step of compiling the application to be deployed is executed.

According to the second aspect of the embodiments of the present disclosure, another application deployment method is provided, including:

Receive the compiled application to be deployed and the test case corresponding to the application to be deployed sent by the management server; wherein the application to be deployed includes source code and configuration files, and the configuration file includes the application to be deployed Deployment directory.

The compiled application to be deployed and the test case are stored in the deployment directory.

Running the test case to test the compiled application to be deployed.

Wherein, the deployment directory includes a temporary directory and a formal directory; and storing the compiled application to be deployed and the test case into the deployment directory includes:

The compiled application to be deployed and the test case are stored in the temporary directory.

Said running said test case tests said compiled application to be deployed, including:

Running the test case in the temporary directory to test the compiled application to be deployed.

Further, the method also includes:

If the test case is run in the temporary directory and the compiled application to be deployed is tested and passed, then the compiled application to be deployed is stored in the official directory, and deleted and stored in the The compiled application to be deployed and the test case in the temporary directory.

Wherein, the test cases include unit test cases and basic environment test cases.

Specifically, the running of the test case tests the compiled application to be deployed, including:

Run the basic environment test case to test the basic operating environment of the application to be deployed.

If the basic environment test case passes, the unit test case is run to test each functional module of the application to be deployed.

According to a third aspect of the embodiments of the present disclosure, an application deployment management server is provided, including:

The first receiving module is configured to receive an application deployment instruction.

The first acquiring module is configured to acquire the application to be deployed, the application to be deployed includes source code and a configuration file, and the configuration file includes a deployment directory of the application to be deployed.

The second acquiring module is configured to acquire the test case corresponding to the application to be deployed.

The compiling module is configured to compile the application to be deployed.

The sending module is configured to send the compiled application to be deployed and the test case to each service server, so that each service server stores the compiled application to be deployed and the test case in the deployment directory, and run the test case to test the compiled application to be deployed.

Wherein, the application deployment instruction includes the application identification, version number and description file of the application to be deployed.

The second acquisition module includes:

The first determining submodule is configured to determine whether there is a historical application corresponding to the application to be deployed, and the historical application has the same application identifier as the application identifier of the application to be deployed and a version number lower than the application to be deployed The version number of the application.

The first obtaining submodule is configured to obtain a history description file corresponding to the history application when there is a history application corresponding to the application to be deployed, and the history description file is a description file of the history application.

The second acquiring submodule is configured to acquire the test case corresponding to the application to be deployed according to the history description file and the description file of the application to be deployed.

Specifically, the second acquisition submodule includes:

The determining submodule is configured to determine whether there is a difference function module in the application to be deployed that has a module function different from that of each function module of the historical application by comparing the history description file with the description file of the application to be deployed.

The first obtaining submodule is configured to obtain the test case corresponding to the historical application as the test case corresponding to the application to be deployed when the difference function module does not exist.

The second obtaining submodule is configured to obtain the difference test case corresponding to the difference function module when the difference function module exists, and update the test case corresponding to the historical application according to the difference test case, and update The test case corresponding to the later historical application is used as the test case corresponding to the application to be deployed.

Further, the management server also includes:

The second receiving module is configured to receive a compilation instruction before the compilation module compiles the application to be deployed, and the compilation instruction includes operator authentication information.

The authentication module is configured to authenticate the operator according to the authentication information; when the authentication is passed, the compiling module is triggered.

According to a fourth aspect of the embodiments of the present disclosure, an application deployment service server is provided, including:

The receiving module is configured to receive the compiled application to be deployed and the test case corresponding to the application to be deployed sent by the management server; wherein, the application to be deployed includes source code and configuration files, and the configuration files include The deployment directory of the application to be deployed.

The storage module is configured to store the compiled application to be deployed and the test case in the deployment directory.

The test module is configured to run the test case to test the compiled application to be deployed.

Wherein, the deployment directory includes a temporary directory and an official directory; the storage module includes:

The first storage submodule is configured to store the compiled application to be deployed and the test case in the temporary directory.

The test module is configured to run the test case in the temporary directory to test the compiled application to be deployed.

Further, the storage module also includes:

The second storage submodule is configured to store the compiled application to be deployed in the official directory when the test case passes the compiled application to be deployed by running the test case in the temporary directory Down.

The service server also includes:

The deletion module is configured to delete the compiled application to be deployed and the test case stored in the temporary directory.

Wherein, the test cases include unit test cases and basic environment test cases.

Wherein, the test module includes:

The first test submodule is configured to run the basic environment test case to test the basic operating environment of the application to be deployed.

The second test submodule is configured to run the unit test case to test each functional module of the application to be deployed when the basic environment test case passes the test.

According to a fifth aspect of the embodiments of the present disclosure, another application deployment management server is provided, including:

processor;

memory configured to store processor-executable instructions;

Wherein, the processor is configured as:

receiving an application deployment instruction, and obtaining an application to be deployed, wherein the application to be deployed includes source code and a configuration file, and the configuration file includes a deployment directory of the application to be deployed;

Obtaining a test case corresponding to the application to be deployed; compiling the application to be deployed;

Send the compiled application to be deployed and the test case to each service server, so that each service server will store the compiled application to be deployed and the test case in the deployment directory, and run The test case tests the compiled application to be deployed.

According to the sixth aspect of the embodiments of the present disclosure, another application deployment service server is provided, including:

processor;

memory configured to store processor-executable instructions;

Wherein, the processor is configured as:

Receive the compiled application to be deployed and the test case corresponding to the application to be deployed sent by the management server; wherein the application to be deployed includes source code and configuration files, and the configuration file includes the application to be deployed deployment directory;

storing the compiled application to be deployed and the test case in the deployment directory;

Running the test case to test the compiled application to be deployed.

The technical solutions provided by the embodiments of the present disclosure may include the following beneficial effects:

By setting the deployment directory where the application is deployed in each business server of the distributed system in the configuration file of the application, each business server automatically deploys the application in the deployment directory, ensuring the deployment path of the application in all business servers Consistent; and, by obtaining the test case corresponding to the application, and sending the test case to each business server, so that each business server stores the test case and the application together in the above-mentioned deployment directory, and each business server automatically starts Run the test case to test the application. In the process of automatic deployment and testing, manual intervention is not required, problems of manual deployment and testing that are prone to errors are avoided, and the efficiency of application deployment and testing is improved while reliability of application deployment and testing is ensured.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure.

Description of drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description serve to explain the principles of the disclosure.

Fig. 1 is a schematic diagram of an application scenario shown in an exemplary embodiment of the present disclosure;

Fig. 2 is a flow chart of Embodiment 1 of an application deployment method according to an exemplary embodiment;

Fig. 3 is a flow chart of Embodiment 2 of an application deployment method according to an exemplary embodiment;

Fig. 4 is a flow chart of Embodiment 3 of an application deployment method according to an exemplary embodiment;

Fig. 5 is a flow chart of Embodiment 4 of an application deployment method according to an exemplary embodiment;

Fig. 6 is a flow chart of Embodiment 5 of an application deployment method according to an exemplary embodiment;

Fig. 7 is a signaling interaction diagram of an application deployment method according to an exemplary embodiment;

Fig. 8 is a block diagram of Embodiment 1 of an application deployment management server according to an exemplary embodiment;

Fig. 9 is a block diagram of Embodiment 2 of an application deployment management server according to an exemplary embodiment;

Fig. 10 is a block diagram of Embodiment 3 of an application deployment management server according to an exemplary embodiment;

Fig. 11 is a block diagram of Embodiment 1 of an application deployment service server according to an exemplary embodiment;

Fig. 12 is a block diagram of Embodiment 2 of an application deployment service server according to an exemplary embodiment;

Fig. 13 is a block diagram of an application deployment management server according to an exemplary embodiment;

Fig. 14 is a block diagram of an application deployment service server according to an exemplary embodiment;

Fig. 15 is a block diagram of an application deployment management server according to an exemplary embodiment;

Fig. 16 is a block diagram of an application deployment service server according to an exemplary embodiment.

By means of the above-mentioned drawings, certain embodiments of the present disclosure have been shown and will be described in more detail hereinafter. These drawings and written description are not intended to limit the scope of the disclosed concept in any way, but to illustrate the disclosed concept for those skilled in the art by referring to specific embodiments.

Detailed ways

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numerals in different drawings refer to the same or similar elements unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatuses and methods consistent with aspects of the present disclosure as recited in the appended claims.

First, the applicable application scenarios of the embodiments of the present disclosure are introduced.

Fig. 1 is a schematic diagram of an application scenario shown in an exemplary embodiment of the present disclosure. As shown in Fig. 1 , the improved application deployment method in each embodiment of the present disclosure is applicable to a distributed application deployment scenario in a distributed system. The distributed system includes N service servers and one management server as shown in FIG. 1 , where N is an integer greater than 1. Wherein, the management server can be split into two independent servers functionally, namely a code server and a compilation server. The two servers can be set independently, or can be integrated together to form the above-mentioned management server. Since the specific implementation form of the management server has little influence on the application deployment method of the embodiment of the present disclosure, therefore, in the following embodiments, except for the special description in the embodiment shown in FIG. Specifically, it is divided into code server and compilation server.

The application deployment method of the present disclosure will be described in detail below in conjunction with various specific embodiments.

Fig. 2 is a flow chart of Embodiment 1 of an application deployment method according to an exemplary embodiment. As shown in Fig. 2 , the application deployment method involved in this embodiment may be executed by the management server shown in Fig. 1 . Specifically, the application deployment method includes the following steps:

In step S101, an application deployment instruction is received, and an application to be deployed is acquired. The application to be deployed includes a source code and a configuration file, and the configuration file includes a deployment directory of the application to be deployed.

In step S102, a test case corresponding to the application to be deployed is obtained.

In step S103, compile the application to be deployed.

In step S104, send the compiled application to be deployed and the test case to each service server, so that each service server will store the compiled application to be deployed and the test case into the deployment directory, and run the test case to test the compiled application to be deployed.

At present, various application service providers are always constantly introducing various network applications, such as WeChat, forums, Weibo, etc., which are currently used for people's instant messaging. Whenever the developer of the application completes the development of the relevant application, the application needs to be deployed in the service server in the above-mentioned distributed system, so as to provide it for access and use by a large number of users.

Specifically, the application developer can send the developed application to the management server in the distributed system.

In this embodiment, the working process of the management server is described in detail by taking the management server including the code server and the compiling server shown in FIG. 1 . However, it can be understood that the management server can also integrate the functions of the above two servers, and execute the working process in this embodiment as a unique whole.

Before introducing this embodiment in detail, first of all, it is worth noting that there is no strict timing relationship between the above step S102 and step S103, that is, the test case can be obtained first, and then the application to be deployed can be compiled; Compile the application to be deployed, and then obtain the test case; it is also possible to compile the application to be deployed while obtaining the test case. At this time, the two processes of the above-mentioned management server or the above-mentioned code server and compilation server perform different operations respectively. .

Specifically, in this embodiment, the code server may be configured to receive an application deployment instruction sent by an application developer, and the application deployment instruction includes a developed application to be deployed. Therefore, the code server receives and stores the application to be deployed sent by the application developer. After logging in to the compilation server, the operation and maintenance personnel can interact with the code server to obtain the application that needs to be deployed currently, that is, the application to be deployed.

In this embodiment, besides the source code of the application, the application to be deployed also includes the configuration file of the application.

Among other things, the application's configuration file contains application-specific settings. This file contains configuration settings that the common language runtime reads (such as assembly binding policies, remoting objects, and so on), as well as settings that applications can read.

In this embodiment, the configuration file includes the deployment directory of the application to be deployed in each service server, and the deployment directory can be preset.

As mentioned above, in order to ensure that the application can run normally after being deployed in each business server, so as to provide corresponding services for the majority of users, it is necessary to test the application in advance, such as the basic environment test of the business server and unit test for the application. etc.

Among them, unit testing (unit testing): refers to the inspection and verification of the smallest testable unit in the software. Regarding the meaning of a unit in unit testing, a unit in C language refers to a function, a unit in Java refers to a class, and a unit in graphical software refers to a window or a menu, etc. In general, a unit is the smallest functional module to be tested that is artificially specified. Wherein, during the development process of the application, it is likely to be developed based on some public components, some third-party components or some architectures. In order to enable the application to run normally, each business server that deploys the application needs to be able to support these public components, third-party components, and architecture, that is, each business server needs to provide the basic environment necessary for the application. Therefore, it is necessary to test whether each service server provides these basic environments.

In order to realize automatic testing of the application, in this embodiment, the management server, specifically the above-mentioned code server, needs to first obtain a test case corresponding to the application, wherein the test case includes a unit test case for unit testing, And basic environment test cases for testing the basic operating environment of each business server.

It is worth noting that the above-mentioned method of generating the test case is not the focus of protection in this disclosure, so the process of generating the test case will not be described too much. In practice, test cases are generally pre-written and designed by specialized application testers. Therefore, in this embodiment, assuming that the test case of the above-mentioned application to be deployed is designed and stored in a test case database, for example, the code server can query to obtain the test case corresponding to the application. For example, the code server searches the test case database for matching test cases by using the identification information of the application as an index. Correspondingly, it can be understood that, in addition to sending the application to be deployed to the code server, the application developer also carries identification information of the application, such as the name of the application.

Therefore, after the code server obtains the test case corresponding to the application to be deployed, the application to be deployed is stored in association with the test case.

In the actual application deployment process, it is necessary to compile the application to be deployed first, and then deploy it to each service server after the compilation is passed. Therefore, in the case that the management server is represented as an independent whole, the management server performs the compilation process of the application after receiving the compilation instruction of the operation and maintenance personnel for the application to be deployed. Here, compiling refers to a process of generating an object program from a source program (source code) written in a source language by using a compiler.

In the case where the management server is represented by the above-mentioned code server and compilation server, the compilation server needs to obtain the application to be deployed and the corresponding test case from the code server, and then compile the application. Specifically, after obtaining the test case corresponding to the application to be deployed, the code server can automatically trigger sending the application and the test case to the compilation server; or, the compilation server can periodically send a query request to the code server to query Whether there is an application to be deployed in the code server, and if so, the code server feeds back the corresponding application to be deployed and the corresponding test case to the compilation server.

If the application to be deployed is compiled successfully, the compilation server sends the compiled application and the corresponding test case to each business server, and each business server stores the received application and test case in the configuration file described in the application Therefore, each service server automatically deploys the application and the test case in the same directory, and starts and runs the test case to complete the test that the application can run normally. If the test passes, the deployment is complete; otherwise, an alarm is sent to the compilation server, so that the operation and maintenance personnel can detect and maintain the abnormal business server.

In this embodiment, by setting the deployment directory where the application is deployed in each business server of the distributed system in the configuration file of the application, each business server automatically deploys the application in the deployment directory, ensuring that the application is deployed in all The deployment path in the business server is consistent; and, after obtaining the test case corresponding to the application, the test case is also sent to each business server, so that each business server stores the test case and the application together in the deployment directory , each business server automatically starts running the test case to test the application. In the process of automatic deployment and testing, manual intervention is not required, problems of manual deployment and testing that are prone to errors are avoided, and the efficiency of application deployment and testing is improved while reliability of application deployment and testing is ensured.

Fig. 3 is a flow chart of Embodiment 2 of an application deployment method according to an exemplary embodiment. This embodiment provides another implementation manner for step 102 in the embodiment shown in Fig. 2 . As shown in Figure 3, the application deployment method provided in this embodiment may specifically include the following steps:

In step 201, an application deployment instruction is received, and an application to be deployed is acquired, and the application deployment instruction includes an application identifier, a version number, and a description file of the application to be deployed.

In step 202, it is determined whether there is a historical application corresponding to the application to be deployed, and the historical application has the same application identification as the application identification of the application to be deployed and the version number is lower than the version number of the application to be deployed application, if there is a historical application corresponding to the application to be deployed, step 203 is executed.

In step 203, a history description file corresponding to the history application is acquired, where the history description file is a description file of the history application.

In step 204, a test case corresponding to the application to be deployed is acquired according to the history description file and the description file of the application to be deployed.

In this embodiment, besides the application to be deployed, the application deployment instruction received by the management server may also include the application identification, version number and description file of the application.

Wherein, the application identifier and version number are used to uniquely represent the application, because the application will be upgraded and updated, and the same application will have different version numbers. Wherein, the description file of the application is a description of the functions provided by the application and each functional module included in the application.

In addition, the management server stores the application identification, version number, description file, and test case information of deployed applications that have been deployed, and these information can be stored in a database.

Therefore, when the management server receives the above-mentioned application deployment instruction, it queries from the above-mentioned database according to the application ID and version number of the current application to be deployed whether there is an The historical application of the version number of the application is the deployed application.

Wherein, it is worth noting that if multiple versions of an application are stored in the above database, during the above query process, especially the query obtains the corresponding historical application with a version number lower than the version number of the current application to be deployed.

If the management server query determines that there is no historical application corresponding to the application to be deployed, it can interact with the test case generation platform to obtain a test case corresponding to the application to be deployed; if the management server query determines that there is a historical application corresponding to the application to be deployed, Then it acquires the description file of the historical application, ie, the history description file, from the above database.

Furthermore, the management server compares the historical description file with the description file of the application to be deployed to determine whether the two description files are consistent, and obtains test cases corresponding to the application to be deployed in different ways according to the comparison result.

Specifically, if the application functions described in the two description files, the included function modules, and the functions or implementation methods of each function module are consistent, that is, if it is determined that there is no module function in the application to be deployed that is different from each of the historical application Different functional modules with different functional modules indicate that the test case corresponding to the historical application can be used as the test case corresponding to the application to be deployed. Otherwise, if there are different functional modules between the application to be deployed and the historical application, the test case corresponding to the application to be deployed is obtained by obtaining an incremental test case.

Specifically, the management server first obtains the test case of the historical application through the above database, and then obtains the difference test case corresponding to the difference function module, and then updates the test case corresponding to the historical application according to the difference test case, and updates the corresponding test case of the updated historical application. The test case serves as a test case corresponding to the application to be deployed.

Wherein, obtaining the difference test case corresponding to the difference function module may be obtained by, for example, interacting with the test case generation platform. By sending the above-mentioned difference function module to the test case generation platform, the test case designer can design and complete the difference test case corresponding to the difference function module test, and feed back to the management server through the test case generation platform.

Among them, update the test case corresponding to the historical application according to the difference test case, specifically including: if the difference function module is an additional function module relative to the history application, add the difference test case to the test case corresponding to the history application to complete the update ; If the difference function module is a change relative to an existing function module in the historical application, add the difference test case from the test case corresponding to the historical application, and at the same time use the test case corresponding to the historical application to test the same The test case of the function module corresponding to the difference function module is deleted, and the update is completed.

In this embodiment, the management server stores relevant information of each application that has been deployed, so that when the upgraded application is deployed subsequently, it is possible to use the test cases of the corresponding deployed applications to reduce the number of tests for each application by obtaining different test cases. An application needs to carry out the workload brought by the independent design of all test cases, which can further improve the efficiency of application deployment.

Fig. 4 is a flow chart of Embodiment 3 of an application deployment method according to an exemplary embodiment. On the basis of the above embodiment, as shown in Fig. 4 , in this embodiment, the Before deploying the application for compilation, the following steps are also included:

In step 301, a compiling instruction is received, and the compiling instruction includes authentication information of a compiling operator;

In step 302, the compilation operator is authenticated according to the authentication information, and it is determined whether the authentication is passed. If the authentication is passed, step 103 is executed, and if the authentication is not passed, the process ends.

Since the above-mentioned operation and maintenance personnel are compiling operators and operators who send compiled applications and test cases to each business server, and because the application is of great value to application providers, in order to avoid malicious operations by unauthorized personnel , the operation and maintenance personnel can be authenticated.

Specifically, the management server may pre-store authentication information of authorized personnel, such as login account number and password. Therefore, when the operation and maintenance personnel, that is, the current operator, logs in to the management server, if the login account and password entered by him are one of the authorized account and password, the operator is deemed to have passed the authentication.

It can be understood that the identity authentication method may also be, for example, a verification code, a fingerprint, etc., and is not specifically limited.

Above, the process of deploying the application in each service server of the distributed system is introduced from the perspective of the management server. The following describes the specific process of application deployment from the perspective of each service server in combination with several embodiments.

Fig. 5 is a flow chart of Embodiment 4 of an application deployment method according to an exemplary embodiment. As shown in Fig. 5, the application deployment method includes the following steps:

In step 401, the compiled application to be deployed and the test case corresponding to the application to be deployed are received from the management server; wherein, the application to be deployed includes source code and a configuration file, and the configuration file contains all Describe the deployment directory of the application to be deployed.

In step 402, the compiled application to be deployed and the test case are stored in the deployment directory.

In step 403, run the test case to test the compiled application to be deployed.

As described in the foregoing embodiments, after receiving the application deployment instruction, the management server obtains the test case corresponding to the application to be deployed, and after completing processing such as compiling the application to be deployed, sends the application to be deployed and the test case to For each service server, the configuration file of the application to be deployed includes a deployment directory of the application to be deployed.

Therefore, after each service server receives the above-mentioned compiled application to be deployed and test case sent by the management server, it stores the compiled application and test case to be deployed in the deployment directory, so that each service server has Deploy the application to be deployed and the test case in the same deployment directory to avoid errors that are prone to errors during manual deployment, such as storing the wrong directory, misoperation of the application or test case to be deployed, etc.

Furthermore, each business server starts and runs a test case from the deployment directory, and has completed testing whether the application to be deployed can run normally.

Wherein, in this embodiment, the test cases mainly include unit test cases and basic environment test cases. The execution order of these two test cases is that the basic environment test case is executed first, and the basic operating environment of the application to be deployed is tested. If the basic environment test passes, the unit test case is executed, and each of the described application to be deployed is tested. Function modules are tested; if the basic environment test case test fails, an alarm prompt is sent to the management server to remind the operation and maintenance personnel of what kind of test problems have occurred. Correspondingly, if the unit test passes when the unit test case is executed, it means that the application to be deployed can run normally in the business server, and the deployment is completed. If the unit test fails, an alarm prompt will be sent to the management server to remind the operation and maintenance What kind of unit testing problems do people have.

In this embodiment, after each service server receives the application to be deployed with the deployment target and its corresponding test case sent by the management server, it automatically stores the application to be deployed in the directory, and automatically runs the test. The use case tests the application. In the process of automatic deployment and testing, manual intervention is not required, problems of manual deployment and testing that are prone to errors are avoided, and the efficiency of application deployment and testing is improved while reliability of application deployment and testing is ensured.

Fig. 6 is a flow chart of Embodiment 5 of an application deployment method according to an exemplary embodiment. As shown in Fig. 6, the method specifically includes the following steps:

In step 501, the compiled application to be deployed and the test case corresponding to the application to be deployed are received from the management server; wherein, the application to be deployed includes source code and a configuration file, and the configuration file contains all The deployment directory of the application to be deployed is described, and the deployment directory includes a temporary directory and an official directory.

In step 502, the compiled application to be deployed and the test case are stored in the temporary directory.

In step 503, run the test case in the temporary directory to test the compiled application to be deployed.

In step 504, if running the test case in the temporary directory to pass the test of the compiled application to be deployed, then store the compiled application to be deployed in the official directory, and Deleting the compiled application to be deployed and the test case stored in the temporary directory.

In this embodiment, the temporary directory and the official directory are set based on the following considerations, wherein the official directory is a directory different from the temporary directory.

During the process of running test cases to test the application to be deployed, many temporary files, system fragments and other junk files will be generated. These junk files will not only occupy a certain storage space of the business server, but also cause subsequent applications to run The environment is not clean. Therefore, in order to ensure the efficiency and reliability of subsequent applications when they are officially used, the method of setting two directories is adopted in this embodiment.

Specifically, firstly, each business server stores applications and test cases to be deployed in a temporary directory, wherein the basis for selecting the temporary directory is to select a directory that will disappear after the operating system of the business server is permanent directory. Furthermore, the business server runs the test case in the temporary directory to complete the test of the application to be deployed. If the test passes, that is, if the basic environment test passes and the unit test also passes, the business server transfers the application to be deployed to the official directory. Then the business server can be restarted, and the activated application can be officially used. The official directory, as opposed to the temporary directory, is a permanent directory. In addition, the business server deletes the applications and test cases to be deployed stored in the temporary directory, thereby deleting most of the above-mentioned garbage files generated, so as to ensure that the operating environment is clean when the application is officially running.

The application deployment method provided by the present disclosure has been described above from the perspectives of the management server and the business server respectively. The following is a brief introduction of the main interaction process between the management server and the business server when the application is deployed in a distributed system in the present disclosure in conjunction with FIG. 7 . In this embodiment, the management server includes a code server and a compilation server as an example for illustration.

Fig. 7 is a signaling interaction diagram of an application deployment method according to an exemplary embodiment. As shown in Fig. 7, the interaction process includes:

In step 601, the code server receives an application deployment instruction, the application deployment instruction includes an application to be deployed, the application to be deployed includes a source code and a configuration file, and the configuration file includes a deployment directory of the application to be deployed.

In step 602, the code server obtains the test case corresponding to the application to be deployed.

In step 603, the compilation server obtains the application to be deployed and the test case from the code server.

In step 604, the compilation server receives a compilation instruction from the operator, and compiles the application to be deployed according to the compilation instruction.

In step 605, the compiling server sends the compiled application to be deployed and the test case to each service server respectively.

In step 606, each service server stores the compiled application to be deployed and the test case in the deployment directory, and runs the test case.

To sum up, the management server obtains the application to be deployed with the deployment directory and its corresponding test case, and then sends the application to be deployed and the test case to each business server, so that each business server automatically deploys the application in the Under the deployment directory, the deployment path of the application in all business servers is guaranteed to be consistent; moreover, by sending the test case corresponding to the application to each business server, each business server will store the test case in the above In the deployment directory, each business server automatically starts and runs the test case to test the application. In the process of automatic deployment and testing, manual intervention is not required, problems of manual deployment and testing that are prone to errors are avoided, and the efficiency of application deployment and testing is improved while reliability of application deployment and testing is ensured.

The implementation process of the application deployment method is described above, which can be realized by the management server and service server in the distributed system. The internal functions and structures of the management server and service server will be described below.

Fig. 8 is a block diagram of Embodiment 1 of an application deployment management server according to an exemplary embodiment. As shown in Fig. 8, the management server includes: a first receiving module 11, a first obtaining module 12, and a second obtaining module 13. Compiling module 14 and sending module 15.

The first receiving module 11 is configured to receive an application deployment instruction.

The first acquiring module 12 is configured to acquire the application to be deployed, the application to be deployed includes source code and a configuration file, and the configuration file includes a deployment directory of the application to be deployed.

The second obtaining module 13 is configured to obtain test cases corresponding to the application to be deployed.

The compiling module 14 is configured to compile the application to be deployed.

The sending module 15 is configured to send the compiled application to be deployed and the test case to each service server, so that each service server stores the compiled application to be deployed and the test case in the In the above deployment directory, and run the test case to test the compiled application to be deployed.

Fig. 9 is a block diagram of Embodiment 2 of an application deployment management server according to an exemplary embodiment. As shown in Fig. 9, on the basis of the embodiment shown in Fig. 8, the application deployment instruction further includes the The application ID, version number and description file of the application to be deployed. The second acquisition module 13 includes: a first determination submodule 131, a first acquisition submodule 132 and a second acquisition submodule 133, wherein the second acquisition submodule 133 includes: a determination submodule 1331, a first acquisition submodule 133 The submodule 1332 and the second acquisition submodule 1333.

The first determining submodule 131 is configured to determine whether there is a historical application corresponding to the application to be deployed, and the historical application has the same application ID as the application ID of the application to be deployed and a version number lower than the application ID of the application to be deployed Application version number of the application.

The first obtaining submodule 132 is configured to obtain a history description file corresponding to the history application when there is a history application corresponding to the application to be deployed, and the history description file is a description file of the history application.

The second acquiring submodule 133 is configured to acquire the test case corresponding to the application to be deployed according to the history description file and the description file of the application to be deployed.

Wherein, the determination submodule 1331 is configured to determine whether there is a difference in the function of the module in the application to be deployed by comparing the description file of the history description file with the description file of the application to be deployed. functional module.

The first obtaining submodule 1332 is configured to obtain the test case corresponding to the historical application as the test case corresponding to the application to be deployed when the difference function module does not exist.

The second obtaining submodule 1333 is configured to obtain the difference test case corresponding to the difference function module when the difference function module exists, and update the test case corresponding to the historical application according to the difference test case, and The test case corresponding to the updated historical application is used as the test case corresponding to the application to be deployed.

Fig. 10 is a block diagram of Embodiment 3 of an application deployment management server according to an exemplary embodiment. As shown in Fig. 10 , on the basis of the embodiment shown in Fig. 8 , the management server further includes: a second receiving module 21 and authentication module 22.

The second receiving module 21 is configured to receive a compilation instruction before the compilation module 14 compiles the application to be deployed, and the compilation instruction includes operator authentication information;

An authentication module 22 configured to authenticate the operator according to the authentication information;

When the authentication is passed, the compilation module 13 is triggered.

To sum up, the application deployment management server provided by the embodiment of the present disclosure can realize the acquisition, storage, compilation and distribution and deployment of the application to be deployed and its test cases to each business server, and realize the unified automatic scheduling of the application deployment process. There is no need to manually deploy and test applications in each service server one by one. Moreover, the management server can obtain differentiated test cases of applications to be deployed based on deployed applications stored in itself, thereby further improving application deployment efficiency.

FIG. 11 is a block diagram of Embodiment 1 of an application deployment service server according to an exemplary embodiment. As shown in FIG. 11 , the service server includes: a receiving module 31 , a storage module 32 and a testing module 33 .

The receiving module 31 is configured to receive the compiled application to be deployed and the test case corresponding to the application to be deployed sent by the management server; wherein, the application to be deployed includes source code and configuration files, and the configuration files include A deployment directory containing the application to be deployed.

The storage module 32 is configured to store the compiled application to be deployed and the test case in the deployment directory.

The testing module 33 is configured to run the test case to test the compiled application to be deployed.

Fig. 12 is a block diagram of Embodiment 2 of an application deployment service server according to an exemplary embodiment. As shown in Fig. 12, on the basis of the embodiment shown in Fig. 11, the deployment directory includes a temporary directory and an official directory , the storage module 32 includes: a first storage sub-module 321 and a second storage sub-module 322 .

The first storage submodule 321 is configured to store the compiled application to be deployed and the test case in the temporary directory.

The test module 33 is configured to run the test case in the temporary directory to test the compiled application to be deployed.

The second storage submodule 322 is configured to store the compiled application to be deployed in the official Under contents.

The service server also includes: a deletion module 34 .

The deletion module 34 is configured to delete the compiled application to be deployed and the test case stored in the temporary directory.

Wherein, the test cases include unit test cases and basic environment test cases.

The testing module 33 includes: a first testing submodule 331 and a second testing submodule 332 .

The first test submodule 331 is configured to run the basic environment test case to test the basic operating environment of the application to be deployed.

The second test submodule 332 is configured to run the unit test case to test each functional module of the application to be deployed when the basic environment test case passes the test.

To sum up, the application deployment service servers provided by the embodiments of the present disclosure can automatically store the application to be deployed in the corresponding deployment directory based on the unified distribution of the management server, and automatically run the test case to complete the automatic test of the application , improving the efficiency of application deployment. In addition, a temporary directory and an official directory are set up, and the application to be deployed and the test case are stored and tested in the temporary directory, and the application and the test case that pass the test are deleted from the temporary directory, and the application to be deployed is transferred to the official directory , to further ensure the cleanness of the running environment when the business server runs the application, and improve the running efficiency of the application.

Regarding the apparatus in the above embodiments, the specific manner in which each module and sub-module performs operations has been described in detail in the embodiments related to the method, and will not be described in detail here.

The above describes the internal functions and structure of the application deployment management server, as shown in Figure 13. In practice, the management server can be implemented as:

processor;

memory configured to store processor-executable instructions;

Wherein, the processor is configured as:

receiving an application deployment instruction, and obtaining an application to be deployed, wherein the application to be deployed includes source code and a configuration file, and the configuration file includes a deployment directory of the application to be deployed;

Obtaining a test case corresponding to the application to be deployed; compiling the application to be deployed;

Send the compiled application to be deployed and the test case to each service server, so that each service server will store the compiled application to be deployed and the test case in the deployment directory, and run The test case tests the compiled application to be deployed.

The above describes the internal functions and structure of the application deployment business server, as shown in Figure 14. In practice, the management server can be implemented as:

processor;

memory configured to store processor-executable instructions;

Wherein, the processor is configured as:

Receive the compiled application to be deployed and the test case corresponding to the application to be deployed sent by the management server; wherein the application to be deployed includes source code and configuration files, and the configuration file includes the application to be deployed deployment directory;

storing the compiled application to be deployed and the test case in the deployment directory;

Running the test case to test the compiled application to be deployed.

Fig. 15 is a block diagram of an application deployment management server 1500 according to an exemplary embodiment. Referring to FIG. 15, the management server 1500 includes a processing component 1522, which further includes a processor, and a memory resource represented by a memory 1532 for storing instructions executable by the processing component 1522, such as application programs. The application programs stored in memory 1532 may include one or more modules each corresponding to a set of instructions. In addition, the processing component 1522 is configured to execute instructions to perform the method described above:

receiving an application deployment instruction, and obtaining an application to be deployed, wherein the application to be deployed includes source code and a configuration file, and the configuration file includes a deployment directory of the application to be deployed;

Obtaining a test case corresponding to the application to be deployed; compiling the application to be deployed;

Send the compiled application to be deployed and the test case to each service server, so that each service server will store the compiled application to be deployed and the test case in the deployment directory, and run The test case tests the compiled application to be deployed.

Management server 1500 may also include a power component 1526 configured to perform power management of management server 1500, a wired or wireless network interface 1550 configured to connect management server 1500 to a network, and an input output (I/O) interface 1558 . The management server 1500 can operate based on an operating system stored in the memory 1532, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™ or the like.

Fig. 16 is a block diagram of an application deployment service server 1600 according to an exemplary embodiment. Referring to FIG. 16, the management server 1600 includes a processing component 1622, which further includes a processor, and a memory resource represented by a memory 1632 for storing instructions executable by the processing component 1622, such as application programs. The application programs stored in memory 1632 may include one or more modules each corresponding to a set of instructions. In addition, the processing component 1622 is configured to execute instructions to perform the above method:

Receive the compiled application to be deployed and the test case corresponding to the application to be deployed sent by the management server; wherein the application to be deployed includes source code and configuration files, and the configuration file includes the application to be deployed deployment directory;

storing the compiled application to be deployed and the test case in the deployment directory;

Running the test case to test the compiled application to be deployed.

Management server 1600 may also include a power supply component 1626 configured to perform power management of management server 1600, a wired or wireless network interface 1650 configured to connect management server 1600 to a network, and an input output (I/O) interface 1658 . The management server 1600 can operate based on an operating system stored in the memory 1632, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™ or the like.

Other embodiments of the present disclosure will be readily apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any modification, use or adaptation of the present disclosure, and these modifications, uses or adaptations follow the general principles of the present disclosure and include common knowledge or conventional technical means in the technical field not disclosed in the present disclosure . The specification and examples are to be considered exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

It should be understood that the present disclosure is not limited to the precise constructions which have been described above and shown in the drawings, and various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims (20)

1. An application deployment method, characterized in that the method comprises: receiving an application deployment instruction, and obtaining an application to be deployed, wherein the application to be deployed includes source code and a configuration file, and the configuration file includes a deployment directory of the application to be deployed; Obtaining a test case corresponding to the application to be deployed; compiling the application to be deployed; Send the compiled application to be deployed and the test case to each service server, so that each service server will store the compiled application to be deployed and the test case in the deployment directory, and run The test case tests the compiled application to be deployed. 2. The method according to claim 1, wherein the application deployment instruction includes the application identification, version number and description file of the application to be deployed; The acquisition of test cases corresponding to the application to be deployed includes: Determine whether there is a historical application corresponding to the application to be deployed, where the historical application is an application whose application identifier is the same as that of the application to be deployed and whose version number is lower than the version number of the application to be deployed; If there is a historical application corresponding to the application to be deployed, obtaining a historical description file corresponding to the historical application, where the historical description file is a description file of the historical application; Acquire a test case corresponding to the application to be deployed according to the history description file and the description file of the application to be deployed. 3. The method according to claim 2, wherein the obtaining the test case corresponding to the application to be deployed according to the history description file and the description file of the application to be deployed comprises: By comparing the historical description file with the description file of the application to be deployed, determine whether there is a difference function module in the application to be deployed that has a module function different from that of each functional module of the historical application; If the difference function module does not exist, obtaining the test case corresponding to the historical application as the test case corresponding to the application to be deployed; If there is the difference function module, then obtain the difference test case corresponding to the difference function module, and update the test case corresponding to the historical application according to the difference test case, and use the test case corresponding to the updated historical application as A test case corresponding to the application to be deployed. 4. The method according to claim 1, wherein the method further comprises: Before compiling the application to be deployed, receiving a compiling instruction, the compiling instruction includes operator authentication information; The operator is authenticated according to the authentication information, and if the authentication is passed, the step of compiling the application to be deployed is executed. 5. An application deployment method, characterized in that the method comprises: Receive the compiled application to be deployed and the test case corresponding to the application to be deployed sent by the management server; wherein the application to be deployed includes source code and configuration files, and the configuration file includes the application to be deployed deployment directory; storing the compiled application to be deployed and the test case in the deployment directory; Running the test case to test the compiled application to be deployed. 6. The method according to claim 5, wherein the deployment directory includes a temporary directory and an official directory; The described storing the compiled application to be deployed and the test cases in the deployment directory includes: Storing the compiled application to be deployed and the test case into the temporary directory; Said running said test case tests said compiled application to be deployed, including: Running the test case in the temporary directory to test the compiled application to be deployed. 7. The method according to claim 6, further comprising: If the test case is run in the temporary directory and the compiled application to be deployed is tested and passed, then the compiled application to be deployed is stored in the official directory, and deleted and stored in the The compiled application to be deployed and the test case in the temporary directory. 8. The method according to any one of claims 5 to 7, wherein the test cases include unit test cases and basic environment test cases. 9. The method according to claim 8, wherein the running the test case to test the compiled application to be deployed comprises: Running the basic environment test case to test the basic operating environment of the application to be deployed; If the basic environment test case passes, the unit test case is run to test each functional module of the application to be deployed. 10. An application deployment management server, characterized in that the management server includes: The first receiving module is configured to receive an application deployment instruction; The first acquisition module is configured to acquire the application to be deployed, the application to be deployed includes source code and a configuration file, and the configuration file includes a deployment directory of the application to be deployed; The second acquiring module is configured to acquire the test case corresponding to the application to be deployed; A compiling module configured to compile the application to be deployed; The sending module is configured to send the compiled application to be deployed and the test case to each service server, so that each service server stores the compiled application to be deployed and the test case in the deployment directory, and run the test case to test the compiled application to be deployed. 11. The management server according to claim 10, wherein the application deployment instruction includes the application identification, version number and description file of the application to be deployed; The second acquisition module includes: The first determining submodule is configured to determine whether there is a historical application corresponding to the application to be deployed, and the historical application has the same application identifier as the application identifier of the application to be deployed and a version number lower than the application to be deployed The version number of the application; The first obtaining submodule is configured to obtain a history description file corresponding to the history application when there is a history application corresponding to the application to be deployed, and the history description file is a description file of the history application; The second acquiring submodule is configured to acquire the test case corresponding to the application to be deployed according to the history description file and the description file of the application to be deployed. 12. The management server according to claim 11, wherein the second acquiring submodule comprises: The determining submodule is configured to determine whether there is a difference function module in the application to be deployed that has a module function different from that of each function module of the historical application by comparing the history description file with the description file of the application to be deployed; The first obtaining submodule is configured to obtain the test case corresponding to the historical application as the test case corresponding to the application to be deployed when the difference function module does not exist; The second obtaining submodule is configured to obtain the difference test case corresponding to the difference function module when the difference function module exists, and update the test case corresponding to the historical application according to the difference test case, and update The test case corresponding to the later historical application is used as the test case corresponding to the application to be deployed. 13. The management server according to claim 10, further comprising: The second receiving module is configured to receive a compilation instruction before the compilation module compiles the application to be deployed, and the compilation instruction includes operator authentication information; The authentication module is configured to authenticate the operator according to the authentication information; when the authentication is passed, the compiling module is triggered. 14. An application deployment service server, characterized in that the service server includes: The receiving module is configured to receive the compiled application to be deployed and the test case corresponding to the application to be deployed sent by the management server; wherein, the application to be deployed includes source code and configuration files, and the configuration files include The deployment directory of the application to be deployed; A storage module configured to store the compiled application to be deployed and the test case in the deployment directory; The test module is configured to run the test case to test the compiled application to be deployed. 15. The service server according to claim 14, wherein the deployment directory includes a temporary directory and an official directory; The storage module includes: The first storage submodule is configured to store the compiled application to be deployed and the test case in the temporary directory; The test module is configured to run the test case in the temporary directory to test the compiled application to be deployed. 16. The service server according to claim 15, wherein the storage module further comprises: The second storage submodule is configured to store the compiled application to be deployed in the official directory when the test case passes the compiled application to be deployed by running the test case in the temporary directory Down; The service server also includes: The deletion module is configured to delete the compiled application to be deployed and the test case stored in the temporary directory. 17. The service server according to any one of claims 14 to 16, wherein the test cases include unit test cases and basic environment test cases. 18. The service server according to claim 17, wherein the test module comprises: The first test submodule is configured to run the basic environment test case to test the basic operating environment of the application to be deployed; The second test submodule is configured to run the unit test case to test each functional module of the application to be deployed when the basic environment test case passes the test. 19. An application deployment management server, comprising: processor; memory configured to store processor-executable instructions; Wherein, the processor is configured as: receiving an application deployment instruction, and obtaining an application to be deployed, wherein the application to be deployed includes source code and a configuration file, and the configuration file includes a deployment directory of the application to be deployed; Obtaining a test case corresponding to the application to be deployed; compiling the application to be deployed; Send the compiled application to be deployed and the test case to each service server, so that each service server will store the compiled application to be deployed and the test case in the deployment directory, and run The test case tests the compiled application to be deployed. 20. An application deployment service server, characterized in that it comprises: processor; memory configured to store processor-executable instructions; Wherein, the processor is configured as: Receive the compiled application to be deployed and the test case corresponding to the application to be deployed sent by the management server; wherein the application to be deployed includes source code and configuration files, and the configuration file includes the application to be deployed deployment directory; storing the compiled application to be deployed and the test case in the deployment directory; Running the test case to test the compiled application to be deployed.