CN115495096A - Application deployment method, device, equipment, storage medium and product - Google Patents

Abstract

The application provides an application deployment method, device, equipment, storage medium and product, and is applied to the technical field of software development. The method comprises the following steps: acquiring a pre-configured current dependency definition file after receiving an application deployment instruction; the current dependency definition file includes: standardization related information of a service on which the current version application depends; configuring the dependent service according to the current dependency definition file and the corresponding configuration strategy, and acquiring the calling parameter of the configured dependent service; the calling parameters are parameters required by calling service; and after the integrated code obtained by the application construction is obtained, deploying the application according to the calling parameter and the integrated code. The step of configuring the dependent service can be executed only by acquiring the current dependency definition file including the standardized relevant information of the dependent service, the dependent service is not required to be configured manually by technicians, the repeated work of manual operation can be avoided, and the deployment efficiency of the application is improved.

Description

Application deployment method, device, equipment, storage medium and product

Technical Field

The present application relates to the field of software development technologies, and in particular, to an application deployment method, apparatus, device, storage medium, and product.

Background

From the development of the application source code to the online application, application deployment is required. The application deployment process often relies on some basic services, such as configuration center services.

When the basic services are deployed, relatively professional developers are needed to configure and maintain the basic services, so that the developers are difficult to independently complete the deployment process of the application. Moreover, each deployment of the application may require a developer to perform repetitive work of configuring basic services, which results in low efficiency of deploying the application; and developers need to be familiar with the configuration and maintenance process of basic services, and the deployment efficiency of the application is further influenced.

Disclosure of Invention

The application deployment method, device, equipment, storage medium and product are provided to solve the problems that in the prior art, developers are required to be familiar with the configuration and maintenance process of basic services, and the deployment of applications at each time may require the developers to repeatedly configure the basic services, so that the deployment efficiency is low.

In a first aspect, the present application provides an application deployment method, including: acquiring a pre-configured current dependency definition file after receiving an application deployment instruction; the current dependency definition file comprises: standardization related information of a service on which the current version of application development depends;

configuring the dependent service according to the current dependency definition file and the corresponding configuration strategy, and acquiring a calling parameter of the configured dependent service; the calling parameter is a parameter required by calling service;

and after the integrated code obtained by the application construction is obtained, deploying the application according to the calling parameter and the integrated code.

In a second aspect, the present application provides an application deployment apparatus, comprising:

the acquisition module is used for acquiring a pre-configured current dependency definition file after receiving an application deployment instruction; the current dependency definition file comprises: standardization related information of a service on which the current version of application development depends;

the configuration module is used for configuring the dependent service according to the current dependency definition file and the corresponding configuration strategy and acquiring the calling parameter of the configured dependent service; the calling parameter is a parameter required by calling service;

and the deployment module is used for deploying the application according to the calling parameter and the integrated code after the integrated code obtained by the application construction is obtained.

In a third aspect, the present application provides an electronic device, comprising: a processor, and a memory communicatively coupled to the processor;

the memory stores computer-executable instructions;

the processor executes computer-executable instructions stored in the memory to implement the application deployment method of any of the above aspects.

In a fourth aspect, the present application provides a computer-readable storage medium, in which computer-executable instructions are stored, and when executed by a processor, the computer-executable instructions are used to implement the application deployment method according to any one of the above aspects.

In a fifth aspect, the present application provides a computer program product comprising computer executable instructions that, when executed by a processor, implement the application deployment method of any of the above aspects.

According to the application deployment method, the application deployment device, the application deployment equipment, the storage medium and the product, the pre-configured current dependency definition file is obtained after the application deployment instruction is received; the current dependency definition file comprises: standardization related information of a service on which the current version of application development depends; configuring the dependent service according to the current dependence definition file and the corresponding configuration strategy, and acquiring the calling parameter of the configured dependent service; the calling parameters are parameters required by calling service; and after the integrated code obtained by the application construction is obtained, deploying the application according to the calling parameter and the integrated code. The step of configuring the dependent service can be executed only by acquiring the current dependency definition file including the standardized relevant information of the dependent service, the dependent service is not required to be configured manually by technicians, the deployment efficiency of the application can be improved, the repeated work of manual operation can be avoided, and the deployment efficiency of the application is further improved.

Drawings

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

Fig. 1 is a schematic view of an application scenario provided in an embodiment of the present application;

fig. 2 is a flowchart of an application deployment method according to an embodiment of the present application;

FIG. 3 is a flowchart of a method for configuring a dependent service according to an embodiment of the present application;

fig. 4 is a schematic structural diagram of an application deployment apparatus according to a fourth embodiment of the present application;

fig. 5 is a schematic structural diagram of an electronic device according to a fifth embodiment of the present application.

Specific embodiments of the present application have been shown by way of example in the drawings and will be described in more detail below. These drawings and written description are not intended to limit the scope of the inventive concepts in any manner, but rather to illustrate the inventive concepts to those skilled in the art by reference to specific embodiments.

Detailed Description

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, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

The terms "first", "second", etc. are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. In the description of the following examples, "plurality" means two or more unless specifically limited otherwise.

First, the prior art related to the present invention will be explained and analyzed in detail.

Before the application is deployed, a deployment package or a mirror needs to be constructed, a server and a base environment need to be prepared, and base services such as a database, a cache and the like which are depended by the application need to be deployed. When the basic services are deployed, relatively professional developers are needed to configure and maintain the basic services, so that the developers are difficult to independently complete application deployment, or the developers need to learn how to configure and maintain the basic services on which the applications depend in advance before the application deployment. And before deploying a new version of the application, the developer may be required to perform repetitive work of configuring the base service again, resulting in inefficient deployment of the application.

The inventor finds out in research that by performing standard definition on related information and the like of the service dependent on the application, the service dependent on the application can be regarded as metadata, and the service dependent on the application can be configured according to a corresponding configuration policy through a configuration mode. Therefore, the application deployment method is provided, and the pre-configured current dependency definition file is obtained; the current dependency definition file includes: standardization related information of a service on which the current version application depends; configuring a dependent service according to the current dependence definition file and a corresponding configuration strategy, and acquiring a calling parameter of the configured dependent service; the calling parameters are parameters required by calling service; and after the integrated code obtained by the application construction is obtained, deploying the application according to the calling parameter and the integrated code.

Fig. 1 is a schematic view of an application scenario provided in an embodiment of the present application, and as shown in fig. 1, includes a code repository 1 and an application deployment apparatus 2. The application deployment device 2 can obtain the dependency definition file from the code repository 1, and the dependency definition file includes the standardization related information of the dependent service, so that the application deployment device 2 configures the dependent service a, the dependent service B, and the dependent service C according to the current dependency definition file and the corresponding configuration policy, and obtains the calling parameter of the configured dependent service; after the application deployment device 2 configures the dependent service, instantiation of the application service can be performed according to the calling parameter of the service and the application can be deployed.

In the technical scheme of the application, the collection, storage, use, processing, transmission, provision, disclosure and other processing of the related information such as financial data or user data and the like all accord with the regulations of related laws and regulations and do not violate the good custom of the public order.

The following describes the technical solutions of the present application and how to solve the above technical problems with specific embodiments. These several specific embodiments may be combined with each other below, and details of the same or similar concepts or processes may not be repeated in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.

Example one

Fig. 2 is a flowchart of an application deployment method provided in an embodiment of the present application, and the embodiment of the present application provides an application deployment method for solving a problem in the prior art that a developer needs to be familiar with a configuration and maintenance process of a basic service, and the developer may need to perform repetitive work of configuring the basic service for deployment of an application each time, which results in low efficiency of deploying the application. The method in this embodiment is applied to an application deployment apparatus, and the application deployment apparatus may be located in an electronic device. Among them, the electronic device may be a digital computer or a cloud server representing various forms. Such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers.

As shown in fig. 2, the method comprises the following specific steps:

step S101, obtaining a pre-configured current dependency definition file after receiving an application deployment instruction.

Wherein, the current dependency definition file comprises: the current version applies the standardized relevant information of the dependent service. The application-dependent service may be a cloud service, a cloud function, or a technical component, etc., which provides a public function, where the public function may be a function of configuration management, parameter management, log management, etc. Illustratively, application-dependent services may include: databases, buffers, message queues, etc.

The embodiment of the present application does not limit the manner of triggering the application deployment instruction, and for example, the application deployment instruction may be automatically triggered after the user submits the current dependency definition file and the source code corresponding to the current version application, the application deployment trigger button may also be provided to trigger the application deployment instruction through the user clicking the application deployment trigger button, and the application deployment instruction may also be triggered through any other form.

It should be understood that the current dependency definition file includes information about services on which the standardized current version of the application depends, and thus the services on which the application depends can be configured as metadata.

In the embodiment of the present application, the pre-configured current dependency definition file may be written directly by a developer according to the standard definition of the service on which the application depends, or may be generated according to the input of the user.

And S102, configuring the dependent service according to the current dependency definition file and the corresponding configuration strategy, and acquiring the calling parameter of the configured dependent service.

The calling parameters are parameters required by calling the service. Illustratively, the invocation parameters may include one or more of IP address, port, username, password, etc. parameters corresponding to the service. If the dependent service is a message queue, the invocation parameter may also include a queue name.

In the embodiment of the application, after the configuration of the dependent service is completed, the calling parameter of the dependent service can be acquired, so that the application is deployed according to the calling parameter of the dependent service.

And S103, after the integrated code obtained through the application construction is obtained, deploying the application according to the calling parameter and the integrated code.

In the embodiment of the present application, the integrated code may be a deployment package or a mirror image code obtained by compiling an application source code through an application building. After the calling parameters and the integrated codes are obtained, deployment of the application can be carried out. For example, deployment of applications may be performed using a deployment CD pipeline based on call parameters and integration code.

According to the application deployment method, a pre-configured current dependency definition file is obtained after an application deployment instruction is received; the current dependency definition file includes: standardization related information of a service on which the current version application depends; configuring the dependent service according to the current dependency definition file and the corresponding configuration strategy, and acquiring the calling parameter of the configured dependent service; the calling parameters are parameters required by calling service; and after the integrated code obtained by the application construction is obtained, deploying the application according to the calling parameter and the integrated code. The step of configuring the dependent service can be executed only by acquiring the current dependency definition file including the standardized relevant information of the dependent service, the dependent service is not required to be configured manually by technicians, the deployment efficiency of the application can be improved, the repeated work of manual operation can be avoided, and the deployment efficiency of the application is further improved.

Example two

On the basis of the first embodiment, before the pre-configured dependency definition file is obtained in step S101, the input of the user needs to be standardized to generate the dependency definition file, where the standardization related information in the dependency definition file includes: the method for generating a dependency definition file by normalizing user input includes:

step S201, obtaining a service identifier of a dependent service and a corresponding demand parameter value, which are input by a user.

In the embodiment of the present application, the service identifier of the service input by the user and the corresponding required parameter value may be chinese, english, a code, or the like, which is not specifically limited in the embodiment of the present application. After the service identification of the dependent service input by the user and the corresponding demand parameter value are obtained, the service identification and the corresponding demand parameter value are standardized to determine the dependent service and configure the dependent service according to the standardized demand parameter value.

In the embodiment of the application, the mode of inputting the service identifier and the corresponding requirement parameter value by the user is not limited. Illustratively, a dependent service input box and a requirement parameter input box can be provided to obtain a service identifier of a dependent service input by a user and a corresponding requirement parameter value; a graphical interface may also be provided to obtain user-entered service identifications of dependent services and corresponding demand parameter values.

Optionally, a method of obtaining an identification of a dependent service input by a user includes: and acquiring the service identifier of the service which is determined by the user in the application arrangement interface through the dragging operation and depends on the application.

Specifically, a plurality of services with corresponding configuration policies can be provided in the application orchestration interface, and a user can drag an application-dependent service from the provided plurality of services to a specified area of the application orchestration interface to complete determination of the application-dependent service, so that the application deployment device determines a service identifier of the application-dependent service through the service in the specified area.

According to the method provided by the embodiment of the application, the service identifier of the application-dependent service determined in the application arrangement interface by the user through the dragging operation is obtained, so that the user can enable the application arrangement device to obtain the service identifier of the application-dependent service through a simple dragging operation, the difficulty in configuring and maintaining the application-dependent service can be reduced, and the requirements on technical personnel are reduced.

Step S202, the service identification and the corresponding demand parameter value are standardized.

In the embodiment of the application, after the service identifier and the corresponding demand parameter value are subjected to standardization processing, the service identifier and the demand parameter value in a unified format can be obtained.

The embodiment of the present application does not limit the way of performing the standardized processing on the service identifier and the corresponding demand parameter value. For example, the service identifier and the corresponding demand parameter value may be standardized by using a natural language processing technique, or the standardized service identifier and the standardized demand parameter value corresponding to the service identifier and the demand parameter value input by the user may be determined by using a comparison table of the standardized service identifier and the non-standardized demand parameter value, or the service identifier and the corresponding demand parameter value may be standardized by using any other method.

Step S203, writing the service identifier after the standardization processing and the corresponding requirement parameter value into the current dependence definition file, and storing the current dependence definition file and the application version information in a code warehouse in an associated manner.

In this embodiment of the present application, the application version information corresponding to the current dependency definition file may be automatically generated or may be input by a user, and the application version information may also be managed by a version control tool.

It should be understood that the application version information may instead be dependent on the number of iterations of the definition file and the application version.

On the basis of the above steps, the way of acquiring the pre-configured current dependency definition file in step S101 is as follows: and acquiring a current dependency definition file corresponding to the current version application from the code warehouse.

In the embodiment of the application, the code repository stores the dependency definition files corresponding to a plurality of application versions.

Specifically, the current dependency definition file having an association relationship with the current application version information may be acquired from the code repository according to the current application version information.

The method provided by the embodiment of the application acquires the service identification of the dependent service input by the user and the corresponding demand parameter value; carrying out standardization processing on the service identification and the corresponding demand parameter value; and writing the service identifier after the standardization processing and the corresponding demand parameter value into the current dependence definition file, and storing the current dependence definition file and the application version information in a code warehouse in an associated manner. The dependence definition file can be automatically generated through standardized processing of user input, the user does not need to learn the standard definition of the service identification of each dependence service and the corresponding requirement parameter value, the user does not need to manually write the dependence definition file, and the application deployment efficiency can be improved.

EXAMPLE III

On the basis of any of the above embodiments, the present embodiment relates to a refinement of an implementation manner in which step S102 configures dependent services according to a current dependency definition file and a corresponding configuration policy, and obtains invocation parameters of the configured dependent services, and specifically includes the following steps:

step S301, acquiring the service identifier standardized in the current dependency definition file.

In the embodiment of the present application, the current dependency definition file includes a standardized service identifier of a service on which the current version of application depends, and the service that needs to be configured may be determined according to the standardized service identifier.

Optionally, a manner of obtaining the service identifier standardized in the current dependency definition file is as follows: acquiring a service identifier list from a current dependency definition file; and acquiring standardized service identifiers outside the configuration center in the service identifier list in sequence to execute the step of configuring the dependent services in sequence.

In the embodiment of the application, the configuration center is used for storing the calling parameters of the rest of the dependent services. The configuration center does not need to be configured by adopting the steps from S302 to S306.

Fig. 3 is a flowchart of a method for configuring a dependent service according to an embodiment of the present application, and as shown in fig. 3, the method includes: step 1, obtaining a service identification list. And 2, sequentially acquiring the service identifiers in the service identifier list. And 3, judging whether the service identification corresponds to a configuration center. If yes, executing step 2 to obtain the next service identifier; if not, executing step 4 to configure the service corresponding to the service identifier. And 4, determining whether the service corresponding to the service identifier needs to be opened or updated. If yes, executing step 5 to open or update service; if not, executing step 2 to obtain the next service identifier. And 5, opening or updating the service corresponding to the service identifier. And circularly executing the steps 2 to 5 until the service identifier in the service identifier list is traversed, so as to realize asynchronous opening or updating of the service in the service identifier list.

The method provided by the embodiment of the application acquires the service identifier list from the current dependency definition file; and sequentially acquiring standardized service identifiers except the configuration center in the service identifier list to sequentially execute the step of configuring the dependent services, so that the services corresponding to the service identifiers in the current dependency definition file can be sequentially configured, and the missing configuration of the dependent services can be avoided.

Step S302, obtaining the dependency definition file of the previous version in the code warehouse.

Specifically, the application version information of the previous version may be determined according to the current application version information, and the dependency definition file of the previous version may be obtained from the code repository according to the application version information of the previous version.

Step S303, if the standardized service identifier does not exist in the previous version of the dependency definition file, determining a service activation policy corresponding to the standardized service identifier.

The service opening strategy comprises a method step of opening corresponding service, and the service opening can be realized according to the corresponding service opening strategy.

In the embodiment of the application, if the standardized service identifier does not exist in the dependency definition file of the previous version, it is determined that the service corresponding to the standardized service identifier is the newly added dependent service applied to the current version, the service is not opened yet, and the service needs to be opened according to the service opening policy corresponding to the service identifier.

In the embodiment of the application, the service identifier and the corresponding service provisioning policy may be pre-stored in a certain storage space in an associated manner, and the corresponding service provisioning policy may be determined from the storage space according to the service identifier.

And step S304, opening the service according to the corresponding service opening strategy and acquiring the calling parameter of the opened service.

In the embodiment of the application, after the service is opened according to the corresponding service opening strategy, the calling parameter of the opened service can be obtained.

The method provided by the embodiment of the application obtains the standardized service identification in the current dependence definition file; acquiring a dependency definition file of a previous version in a code warehouse; if the standardized service identifier does not exist in the dependency definition file of the previous version, determining a service opening strategy corresponding to the standardized service identifier; opening the service according to the corresponding service opening strategy, and acquiring a calling parameter of the opened service; and if the standardized service identifier exists in the dependency definition file of the previous version, determining whether to update the calling parameter of the service according to the corresponding standardized parameter value. Whether the service corresponding to the service identifier needs to be opened or not can be determined, and repeated opening of the service is avoided, so that the efficiency of service configuration is improved, and the efficiency of application deployment is further improved.

Optionally, if the dependent service includes a configuration center, where the configuration center is used to store the invocation parameter, after the step S304 acquires the invocation parameter of the opened service, the method further includes: and storing the calling parameters by adopting a configuration center.

Specifically, after the calling parameter of the opened service is obtained, the calling parameter of the opened service is sent to the configuration center, so that the configuration center stores the calling parameter. The calling parameter may further include a corresponding service identifier.

According to the method provided by the embodiment of the application, the configuration center is adopted to store the calling parameters, so that the management of the dependent service can be facilitated, the efficiency of configuring the dependent service is improved, and the efficiency of deploying the application is further improved.

Step S305, if the standardized service identification exists in the dependency definition file of the previous version, determining whether to update the calling parameter of the service according to the corresponding standardized parameter value.

Specifically, if the standardized service identifier exists in the dependency definition file of the previous version, it is determined that the service corresponding to the standardized service identifier has been opened. And if the calling parameter of the updated service is determined according to the corresponding standardized parameter value, updating the calling parameter corresponding to the standardized service identifier by adopting a service updating strategy.

Optionally, a method for determining whether to update a call parameter of a service according to a corresponding standardized parameter value is: and if the quantity of the demand parameters of which the standardized parameter values corresponding to the standardized service identification in the current dependency definition file and the dependency definition file of the previous version are inconsistent is larger than a preset quantity threshold value or the standardized parameter values of the preset important demand parameters are inconsistent, determining the calling parameters of the updated service.

The important demand parameters are demand parameters with large service influence caused by the change of preset parameter values.

In the embodiment of the application, if the standardized parameter value of the preset important demand parameter changes or the changed standardized parameter values are determined to be more according to the preset number threshold, the calling parameter of the update service is determined.

In the method provided by the embodiment of the application, if the quantity of the demand parameters, for which the standardized parameter values corresponding to the standardized service identifier in the current dependency definition file and the dependency definition file of the previous version are inconsistent, is greater than the preset quantity threshold, or the standardized parameter values of the preset important demand parameters are inconsistent, the call parameter for updating the service is determined. Whether the service corresponding to the service identifier needs to be updated or not can be determined, and invalid updating of the service with less change of the demand parameter is avoided, so that the efficiency of configuring the service is improved, and the efficiency of deploying the application is further improved.

And step S306, updating the calling parameter corresponding to the standardized service identifier by adopting a service updating strategy.

Wherein, the corresponding configuration policy comprises a service updating policy. The service updating strategy comprises a method step of updating the corresponding service, and the updating of the service can be realized according to the corresponding service updating strategy. For example, the service update policy may be to update an opened service according to the corresponding standardized demand parameter value, and may also be to reopen the service according to the corresponding standardized demand parameter value.

Optionally, if the dependent service includes a configuration center, the method for updating the call parameter includes: and updating the calling parameters corresponding to the standardized service identification in the configuration center by adopting a service updating strategy.

Specifically, after the service is updated according to the service update policy, the call parameter of the updated service may be obtained, and the call parameter corresponding to the standardized service identifier in the configuration center is updated to the obtained call parameter of the updated service.

Optionally, after the step S103 obtains the integrated code obtained by the application construction, the deploying the application according to the calling parameter and the integrated code specifically includes:

and step S1031, after acquiring the integrated code obtained by the application construction, judging whether the configuration of the service depending on the current version application is finished.

Step S1032, if the configuration of the service dependent on the current version application is determined to be completed, deployment of the application is carried out according to the current dependency definition file, the calling parameter and the integrated code.

In this embodiment of the present application, the acquiring of the integration code obtained by the application building in step S103 may be executed in parallel with the configuring of the dependent service according to the current dependency definition file and the corresponding configuration policy in step S102, and the acquiring of the call parameter of the configured dependent service. After acquiring the integrated code obtained by application construction, judging whether the configuration of the service depending on the current version application is finished; if yes, executing step S1032 to deploy the application according to the current dependency definition file, the calling parameter and the integrated code; if not, judging whether the configuration of the service depending on the current version application is finished or not at intervals until the configuration of the service depending on the current version application is finished, and deploying the application.

One configuration mode for optionally judging whether to complete the service dependent on the current version application is as follows: and under the condition that the standardized service identifiers in the current dependency definition file are obtained in a mode of sequentially obtaining the standardized service identifiers except the configuration center in the service identifier list so as to sequentially execute the step of configuring the dependent services, if the next standardized service identifier does not exist in the service identifier list, determining that the configuration of the service dependent on the current version application is completed.

According to the method provided by the embodiment of the application, whether the configuration of the service dependent on the current version application is completed or not is judged after the integrated code obtained by the application construction is obtained, so that the application deployment can be ensured after the configuration of the service dependent on the application is completed, and the application deployment failure is avoided; and the step of acquiring the integrated code acquired by the application construction can be executed in parallel with the configuration-dependent service, so that the application deployment efficiency can be improved.

Example four

Fig. 4 is a schematic structural diagram of an application deployment apparatus according to a fourth embodiment of the present application. The application deployment device provided in the fourth embodiment of the present application can execute the processing procedure provided in the embodiment of the application deployment method. As shown in fig. 4, the application deployment apparatus 40 includes: an acquisition module 401, a configuration module 402, and a deployment module 403.

Specifically, the obtaining module 401 is configured to obtain a preconfigured current dependency definition file after receiving an application deployment instruction; the current dependency definition file includes: the current version applies standardized relevant information of the service on which development depends.

A configuration module 402, configured to configure a dependent service according to the current dependency definition file and the corresponding configuration policy, and obtain a call parameter of the configured dependent service; the call parameters are parameters required for calling the service.

The deployment module 403 is configured to, after obtaining the integration code obtained through the application construction, deploy the application according to the call parameter and the integration code.

The apparatus provided in the embodiment of the present application may be specifically configured to execute the method embodiment provided in the first embodiment, and specific functions are not described herein again.

Optionally, the application deployment apparatus 40 further comprises: a generating module; the normalization related information includes: standardized service identification and standardized demand parameter values; the generation module is to: acquiring a service identifier of a dependent service input by a user and a corresponding demand parameter value; carrying out standardization processing on the service identification and the corresponding demand parameter value; writing the service identifier after the standardization processing and the corresponding demand parameter value into a current dependence definition file, and storing the current dependence definition file and the application version information in a code warehouse in an associated manner; the obtaining module 401 is specifically configured to: and acquiring a current dependency definition file corresponding to the current version application from the code warehouse.

Optionally, the generating module is specifically configured to: and acquiring the service identifier of the service which is determined by the user in the application arrangement interface through the dragging operation and depends on the application.

Optionally, the corresponding configuration policy includes a service provision policy, and the configuration module 402 is specifically configured to: acquiring a standardized service identifier in a current dependency definition file; acquiring a dependency definition file of a previous version in a code warehouse; if the standardized service identifier does not exist in the dependency definition file of the previous version, determining a service opening strategy corresponding to the standardized service identifier; opening the service according to the corresponding service opening strategy, and acquiring a calling parameter of the opened service; and if the standardized service identifier exists in the dependency definition file of the previous version, determining whether to update the calling parameter of the service according to the corresponding standardized parameter value.

Optionally, the configuration module 402 is specifically configured to: if the quantity of the demand parameters, corresponding to the standardized parameter values of the standardized service identifier, in the current dependency definition file and the dependency definition file of the previous version is not consistent, is larger than a preset quantity threshold value, or the standardized parameter values of the preset important demand parameters are not consistent, determining the calling parameters of the updated service, and updating the calling parameters corresponding to the standardized service identifier by adopting a corresponding service updating strategy.

Optionally, the dependent service comprises a configuration center; the standardized service identifiers are stored in the current dependency definition file in a list, and the configuration module 402 is specifically configured to: acquiring a service identifier list from a current dependency definition file; and acquiring standardized service identifiers outside the configuration center in the service identifier list in sequence to execute the step of configuring the dependent services in sequence.

Optionally, the configuration module 402 is specifically configured to: storing and calling parameters by adopting a configuration center; and updating the calling parameters corresponding to the standardized service identification in the configuration center by adopting a service updating strategy.

Optionally, the deployment module 403 is specifically configured to: after acquiring the integrated code obtained by application construction, judging whether the configuration of the service depending on the current version application is finished; and if the configuration of the service dependent on the current version application is determined to be completed, deploying the application according to the current dependence definition file, the calling parameter and the integrated code.

The apparatus provided in the embodiment of the present application may be specifically configured to execute the method embodiment, and specific functions are not described herein again.

EXAMPLE five

Fig. 5 is a schematic structural diagram of an electronic device according to a fifth embodiment of the present application, and as shown in fig. 5, the present application further provides an electronic device 50, including: memory 501, processor 502.

The memory 501 is used for storing computer execution instructions and is connected to the processor 502 in communication. In particular, the program may include program code comprising computer-executable instructions. The memory 501 may comprise high-speed RAM memory, and may also include non-volatile memory (non-volatile memory), such as at least one disk memory.

A processor 502 for executing computer-executable instructions stored in the memory 501.

Wherein computer executable instructions are stored in the memory 501 and configured to be executed by the processor 502 to implement the method provided by any one of the embodiments of the present application. The related description may be understood by referring to the related description and effect corresponding to the steps in the drawings, and redundant description is not repeated here.

In the embodiment of the present application, the memory 501 and the processor 502 are connected by a bus. The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended ISA (Extended Industry Standard Architecture) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 5, but this is not intended to represent only one bus or type of bus.

The embodiment of the present application further provides a computer-readable storage medium, in which computer-executable instructions are stored, and when the computer-executable instructions are executed by a processor, the computer-executable instructions are used to implement the method provided in any one of the embodiments of the present application.

The embodiment of the present application further provides a computer program product, which includes computer executable instructions, and when the computer executable instructions are executed by a processor, the method provided in any embodiment of the present application is implemented.

In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, a division of modules is merely a logical division, and other divisions may be realized in practice, for example, a plurality of modules or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or modules, and may be in an electrical, mechanical or other form.

Modules described as separate parts may or may not be physically separate, and parts displayed as modules may or may not be physical modules, may be located in one place, or may be distributed on a plurality of network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, functional modules in the embodiments of the present application may be integrated into one processing module, or each module may exist alone physically, or two or more modules are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a mode of hardware and a software functional module.

Program code for implementing the methods of the present application may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable full path trajectory fusion device such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowchart and/or block diagram to be performed. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of this application, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

Further, while operations are depicted in a particular order, this should be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. Under certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the application. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single implementation. Conversely, various features that are described in the context of a single implementation can also be implemented in multiple implementations separately or in any suitable subcombination.

Other embodiments of the present application will be 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 variations, uses, or adaptations of the invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.

It will be understood that the present application is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the appended claims.

Claims (12)

1. An application deployment method, comprising:

acquiring a pre-configured current dependency definition file after receiving an application deployment instruction; the current dependency definition file comprises: standardization related information of a service on which the current version application depends;

configuring the dependent service according to the current dependency definition file and the corresponding configuration strategy, and acquiring a calling parameter of the configured dependent service; the calling parameter is a parameter required by calling service;

and after the integrated code obtained by the application construction is obtained, deploying the application according to the calling parameter and the integrated code.

2. The method of claim 1, wherein the normalization-related information comprises: a standardized service identification and a standardized demand parameter value; before the obtaining of the pre-configured dependency definition file, the method includes:

acquiring a service identifier of a dependent service input by a user and a corresponding demand parameter value;

standardizing the service identification and the corresponding demand parameter value;

writing the service identification after the standardization processing and the corresponding demand parameter value into a current dependence definition file, and storing the current dependence definition file and the application version information in a code warehouse in an associated manner;

the obtaining the pre-configured current dependency definition file comprises:

and acquiring a current dependency definition file corresponding to the current version application from the code warehouse.

3. The method of claim 2, wherein obtaining the identification of the dependent service input by the user comprises:

and acquiring the service identifier of the service which is determined by the user in the application arrangement interface through the dragging operation and is depended on by the application.

4. The method according to claim 2, wherein the corresponding configuration policy includes a service provisioning policy, and the configuring a dependent service according to the current dependency definition file and the corresponding configuration policy and obtaining a call parameter of the configured dependent service includes:

acquiring a standardized service identifier in a current dependency definition file;

acquiring a dependency definition file of a previous version in a code warehouse;

if the standardized service identifier does not exist in the dependency definition file of the previous version, determining a service opening strategy corresponding to the standardized service identifier;

opening the service according to the corresponding service opening strategy, and acquiring a calling parameter of the opened service;

and if the standardized service identifier exists in the dependency definition file of the previous version, determining whether to update the calling parameter of the service according to the corresponding standardized parameter value.

5. The method of claim 4, wherein the corresponding configuration policy comprises a service update policy, and wherein the determining whether to update the invocation parameter of the service according to the corresponding standardized parameter value comprises:

if the quantity of the demand parameters, corresponding to the standardized parameter values of the standardized service identification, in the current dependency definition file and the last version of dependency definition file is not consistent, is larger than a preset quantity threshold value, or the standardized parameter values of the preset important demand parameters are not consistent, determining the calling parameters of the updated service, and updating the calling parameters corresponding to the standardized service identification by adopting a corresponding service updating strategy.

6. The method of claim 4, wherein the dependent service comprises a configuration center; storing standardized service identifications in the current dependency definition file in a list form, and acquiring the standardized service identifications in the current dependency definition file includes:

acquiring a service identifier list from a current dependency definition file;

and acquiring standardized service identifiers outside the configuration center in the service identifier list in sequence to execute the step of configuring the dependent services in sequence.

7. The method of claim 6, wherein obtaining the invocation parameters of the opened service comprises:

storing the calling parameters by adopting a configuration center;

the updating of the call parameter corresponding to the standardized service identifier by using the service update policy includes:

and adopting a service updating strategy to update the calling parameter corresponding to the standardized service identifier in the configuration center.

8. The method of claim 1, wherein deploying the application according to the invocation parameter and the integration code comprises:

after acquiring the integrated code obtained by application construction, judging whether the configuration of the service depending on the current version application is finished;

and if the configuration of the service dependent on the current version application is determined to be completed, deploying the application according to the current dependence definition file, the calling parameter and the integrated code.

9. An application deployment apparatus, comprising:

the acquisition module is used for acquiring a pre-configured current dependency definition file after receiving an application deployment instruction; the current dependency definition file comprises: standardization related information of a service on which the current version of application development depends;

the configuration module is used for configuring the dependent service according to the current dependency definition file and the corresponding configuration strategy and acquiring the calling parameter of the configured dependent service; the calling parameters are parameters required by calling service;

and the deployment module is used for deploying the application according to the calling parameter and the integrated code after the integrated code obtained by the application construction is obtained.

10. An electronic device, comprising: a processor, and a memory communicatively coupled to the processor;

the memory stores computer execution instructions;

the processor executes computer-executable instructions stored by the memory to implement the method of any of claims 1-8.

11. A computer-readable storage medium having computer-executable instructions stored therein, which when executed by a processor, are configured to implement the method of any one of claims 1-8.

12. A computer program product comprising computer executable instructions, wherein the computer executable instructions when executed by a processor implement the method of any one of claims 1 to 8.

Images