Project deployment method and device, equipment, storage medium and program product

Abstract

The invention discloses a project deployment method and device, equipment, a storage medium and a program product, and relates to the technical field of project management. The method comprises the steps that under the condition that a target project corresponding to a first project template needing to be deployed exists, a version query request is sent to a target server, the version query request is used for requesting to query second version information of a second project template on a second device, the second project template is a basic template of the first project template, and the second version information is stored in the target server; the first project template is a second project template or a template obtained by expanding the second project template; receiving second version information of a second project template fed back by the target server based on the version query request; and deploying the target project to the first project template under the condition that the first version information of the first project template and the second version information of the second project template meet a preset matching condition. According to the embodiment of the invention, the compatibility and stability between project templates can be ensured.

Description

Technical Field

[0001] The present application belongs to the technical field of project management, and in particular, relates to a project deployment method, device, equipment, storage medium and program product. Background Art

[0002] In companies such as banks, telecom operators or chain enterprises, there is usually a head office and multiple branches. In the process of application development, the head office usually provides a standard development template for a project, and local branches can modify the standard development template according to local conditions, add some new functions to the standard development template, and obtain a personalized development template that meets local conditions.

[0003] Normally, the head office will update the standard development templates from time to time. These updates may only be minor changes and have little impact on the personalized development templates of the branches. In addition, it is difficult to notify each branch of the updates, so the head office usually does not force the branches to update the personalized development templates synchronously.

[0004] However, as time goes by, the template version of the personalized development template used by the branch may become increasingly different from the version of the standard development template of the head office. If some new projects continue to be developed based on the old version of the personalized development template, then when the branch's personalized development template finally needs to be upgraded to the latest version, it will become very difficult to integrate these new projects. Version incompatibility will affect the stability of project deployment. Summary of the invention

[0005] The embodiments of the present application provide a project deployment method, apparatus, device, storage medium and program product, which can solve the problem of low stability of project deployment caused by existing version incompatibility.

[0006] In a first aspect, an embodiment of the present application provides a project deployment method, the method comprising:

[0007] In the case where there is a target project corresponding to the first project template that needs to be deployed, sending a version query request to the target server, wherein the version query request is used to request querying second version information of the second project template on the second device, wherein the second project template is a base template of the first project template, the first project template is the second project template, or a template that is an extension of the second project template;

[0008] Receiving second version information of the second project template fed back by the target server based on the version query request;

[0009] When the first version information of the first project template and the second version information of the second project template meet a preset matching condition, the target project is deployed to the first project template.

[0010] In some embodiments, the version information includes a template version and a minimum required version, and the first version information and the second version information belong to the version information;

[0011] When the first version information of the first project template and the second version information of the second project template meet a preset matching condition, before deploying the target project to the first project template, the method further includes:

[0012] When the template version in the first version information is different from the template version in the second version information, obtaining the minimum required version in the second version information;

[0013] In a case where the template version in the first version information is not lower than the minimum required version in the second version information, it is determined that the first version information and the second version information meet a preset matching condition.

[0014] In some embodiments, after receiving the second version information of the second project template fed back by the target server based on the version query request, the method further includes:

[0015] If the first version information of the first project template and the second version information of the second project template do not meet a preset matching condition, canceling deployment of the target project to the first project template;

[0016] Outputting prompt information, wherein the prompt information is used to prompt that the first project template is incompatible with a basic second project template.

[0017] In some embodiments, the method further comprises:

[0018] In the case where there is a code update in the first project template, the updated first code update content is sent to the target server.

[0019] In a second aspect, an embodiment of the present application further provides a project deployment method, which is applied to a target server and includes:

[0020] Upon receiving the version query request sent by the first device, obtaining second version information corresponding to the version query request, wherein the target server stores version information of multiple project templates, the second version information is version information of a second project template among the multiple project templates, and the second project template is a base template for other project templates;

[0021] Send the second version information to the first device.

[0022] In some embodiments, the method further comprises:

[0023] In case of receiving the code update content sent by the third device, determining the third device corresponding to the code update content;

[0024] Determining third version information of a third project template in a third device;

[0025] The third version information is updated based on the code update content.

[0026] In a third aspect, an embodiment of the present application provides a project deployment device, the device comprising:

[0027] A sending module, used for sending a version query request to a target server when there is a target project corresponding to a first project template that needs to be deployed, wherein the version query request is used for requesting to query second version information of a second project template on a second device, wherein the second project template is a base template of the first project template, the first project template is the second project template, or is a template that is an extension of the second project template;

[0028] A receiving module, configured to receive second version information of the second project template fed back by the target server based on the version query request;

[0029] A deployment module is used to deploy the target project to the first project template when the first version information of the first project template and the second version information of the second project template meet a preset matching condition.

[0030] In a fourth aspect, an embodiment of the present application provides a project deployment device, the device comprising: a processor and a memory storing computer program instructions;

[0031] When the processor executes the computer program instructions, the deployment method of the above project is implemented.

[0032] In a fifth aspect, an embodiment of the present application provides a computer storage medium on which computer program instructions are stored, and when the computer program instructions are executed by a processor, the deployment method of the above project is implemented.

[0033] In a sixth aspect, an embodiment of the present application provides a computer program product, which includes computer program instructions, and when the computer program instructions are executed by a processor, the deployment method of the above project is implemented.

[0034] In the present application, when there is a target project that needs to be deployed on the first project template, a version query request is sent to the target server, and the version query request is used to request the second version information of the second project template on the second device, wherein the second project template is the base template of the first project template, and the first project template is the second project template, or a template after the second project template is extended; the second version information of the second project template fed back by the target server based on the version query request is received; when the first version information of the first project template and the second version information of the second project template meet the preset matching conditions, the target project is deployed to the first project template. In this way, it can be ensured that each time a project is deployed to the first project template on the first device, the version of the first project template matches the version of the underlying second project template, thereby ensuring the compatibility of templates on different devices, avoiding potential problems caused by version incompatibility, and improving the stability of project deployment. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments of the present application will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0036] Figure 1 It is a flowchart of a project deployment method provided by an embodiment of the present application;

[0037] Figure 2 It is a structural diagram of a deployment device for a project provided in an embodiment of the present application;

[0038] Figure 3 It is a schematic diagram of the hardware structure of a deployment device for a project provided in one embodiment of the present application. DETAILED DESCRIPTION

[0039] The features and exemplary embodiments of various aspects of the present application will be described in detail below. In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain the present application, rather than to limit the present application. For those skilled in the art, the present application can be implemented without the need for some of these specific details. The following description of the embodiments is only to provide a better understanding of the present application by illustrating the examples of the present application.

[0040] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the statement "include..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0041] It should be noted that the acquisition, storage, use, and processing of data in the technical solution of this application are in compliance with the relevant provisions of national laws and regulations.

[0042] It should be noted that in the embodiments of the present application, certain software, components, models and other existing solutions in the industry may be mentioned, and they should be regarded as exemplary. Their purpose is only to illustrate the feasibility of implementing the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.

[0043] It should be noted that, in the absence of conflict, the embodiments and features in the embodiments of the present application can be combined with each other. The embodiments will be described in detail below in conjunction with the accompanying drawings.

[0044] Specifically, in order to solve the problems of the prior art, the embodiments of the present application provide a project deployment method, device, equipment, storage medium and program product. The project deployment method provided by the embodiments of the present application is first introduced below.

[0045] Figure 1 A schematic diagram of a method for deploying a project provided by an embodiment of the present application is shown. The method is applied to a first device and includes the following steps:

[0046] S110, in the case where there is a target project corresponding to the first project template that needs to be deployed, a version query request is sent to the target server, wherein the version query request is used to request to query the second version information of the second project template on the second device, wherein the second project template is the base template of the first project template, the first project template is the second project template, or is an expanded template of the second project template.

[0047] In this embodiment, the project template is a set of predefined files, directory structures, configurations, and code snippets for quickly starting a new project or unifying the development standards of multiple projects. Based on the project template, the engineering project can be packaged and deployed to the target environment. Among them, engineering project packaging refers to compiling, compressing, merging, and other processing of the source code, resource files, etc. of the engineering project to generate deployable files or application packages for running in the target environment. The target project can be an engineering project corresponding to any first project template.

[0048] Different equipment applies different project templates to package the engineering project, the first project template is a project template applied to the first equipment, the second project template is a project template applied to the second equipment, and the second project template is a basic template of the first project template.

[0049] That is to say, the second project template is a standardized infrastructure that includes common functional modules, project structures, configuration files, etc. This template defines the core functions and standards of the application; and the first project template can develop and customize specific functions based on the second project template according to its own business needs and actual conditions. The first project template can be a project template obtained by the second device pulling the code of the second project template on the first device at a certain moment before the current moment.

[0050] In this embodiment, whenever an edited target project that needs to be deployed to the first project template is detected, it can be determined whether the first project template has been version-checked within the first time period before the current moment. If the version check has been performed within the first time period before the current moment, and the result of the version check is that the version of the first project template matches the version of the underlying second project template, the target project can be packaged and deployed directly. If the version check has not been performed within the first time period before the current moment, a version check is required.

[0051] During the version verification process, a version query request can be sent to the target server to query the version of the basic second project template, and further based on the obtained version information of the second project template, compare whether the version of the first project template matches the version of the second project template.

[0052] S120: Receive second version information of the second project template fed back by the target server based on the version query request.

[0053] In this embodiment, the target server stores version information of the second project template that is updated in real time. After receiving the version query request sent by the first device, the second version information of the basic second project template can be obtained based on the version query request, and the second version information can be sent back to the first device.

[0054] The version information of the project template is used to describe and manage the differences and update contents between different versions of the project template. The version information at least includes the current template version, update date, update description and minimum required version of the project template.

[0055] S130: When the first version information of the first project template and the second version information of the second project template meet a preset matching condition, deploy the target project to the first project template.

[0056] In this embodiment, the preset matching condition is a predefined standard or rule used to determine whether the versions of two templates are compatible or matching. For example, this condition may require that the template versions of the two project templates must be consistent, or the template version of the first project template cannot be lower than the minimum required version of the second project template.

[0057] In an embodiment of the present application, when there is a target project that needs to be deployed on the first project template, a version query request is sent to the target server, the version query request is used to request to query the second version information of the second project template on the second device, wherein the second project template is the base template of the first project template, the first project template is the second project template, or a template after the second project template is extended; the second version information of the second project template fed back by the target server based on the version query request is received; when the first version information of the first project template and the second version information of the second project template meet the preset matching conditions, the target project is deployed to the first project template. In this way, it can be ensured that each time a project is deployed to the first project template on the first device, the version of the first project template matches the version of the underlying second project template, thereby ensuring the compatibility of templates on different devices, avoiding potential problems caused by version incompatibility, and improving the stability of project deployment.

[0058] As an optional embodiment, the version information includes a template version and a minimum required version, and the first version information and the second version information belong to the version information;

[0059] When the first version information of the first project template and the second version information of the second project template meet a preset matching condition, before deploying the target project to the first project template, the method further includes:

[0060] When the template version in the first version information is different from the template version in the second version information, obtaining the minimum required version in the second version information;

[0061] In a case where the template version in the first version information is not lower than the minimum required version in the second version information, it is determined that the first version information and the second version information meet a preset matching condition.

[0062] In this embodiment, the minimum required version refers to the minimum version standard that the template version needs to meet when the project is deployed. In other words, it is the minimum compatibility requirement of the second project template for the first project template version. If the version of the first project template is lower than this minimum required version, the system will consider them incompatible.

[0063] The template version of the first project template can be obtained from the first version information, and the template version of the second project template can be obtained from the second version information. If the template version of the first project template and the template version of the second project template are the same, then the second project template and the first project template must be compatible, and it can be considered that the first project template and the second project template meet the preset matching conditions.

[0064] If the template version of the first project template and the template version of the second project template are different, then the minimum required version of the second project template in the second version information can be obtained. If the template version in the first version information is not lower than the minimum required version in the second version information, then the first project template and the second project template can still be considered compatible, and it is determined that the first version information and the second version information meet the preset matching conditions.

[0065] In this way, you can ensure compatibility between the template version used and the base template version when deploying the project.

[0066] As an optional embodiment, after receiving the second version information of the second project template fed back by the target server based on the version query request, the method further includes:

[0067] If the first version information of the first project template and the second version information of the second project template do not meet a preset matching condition, canceling deployment of the target project to the first project template;

[0068] Outputting prompt information, wherein the prompt information is used to prompt that the first project template is incompatible with a basic second project template.

[0069] In this embodiment, if the first version information and the second version information meet the preset matching conditions, it means that the first project template and the second project template are compatible, so the target project can be deployed directly. Even if the second project template is updated to the first project template later, it will not affect the normal operation of the target project.

[0070] However, if the first version information and the second version information do not meet the preset matching conditions, it means that the first project template and the second project template are not compatible. The first device can cancel the deployment of the target project and output a prompt message to prompt the user that the first project template and the underlying second project template are incompatible and that the first project template needs to be updated before the project can continue to be deployed.

[0071] In this way, it can be ensured that subsequent project templates are updated and the deployed projects can run normally.

[0072] As an optional embodiment, the method further includes:

[0073] When there is a code update in the first project template, the updated code update content is sent to the target server.

[0074] In this embodiment, when there is an update of the code in the first project template in the first device, the updated code update content can be obtained, and then the code update content can be sent to the target server. After receiving the code update content from the first device, the target server will identify and determine the current first version information of the first project template used on the first device. Then, the received code update content can be used to update the corresponding first version information on the first device. In this way, the records in the target server will reflect the latest template version status, ensuring that all version information is consistent with the actual situation.

[0075] For example, the first project template includes at least one folder for file development. When the developer inputs the newly developed content into a folder, it can be considered that the first project template has been updated. Then, the code of the project template in the git repository corresponding to the first project template will also be updated, where the git repository is a repository for storing and managing code for the project template.

[0076] When a code update occurs in the git repository, a webhook associated with the git repository will be triggered. The webhook can send a code update request to the target server. The code update request includes code update content. The code update request can be an HTTP request for requesting the target server to update the first version information based on the code update content.

[0077] In this way, whenever the project template in the first device is modified, the relevant information can be automatically and promptly transmitted to the backend for processing, thereby maintaining the consistency of the system and the synchronization of information.

[0078] Another embodiment of the present application provides a method for deploying a project as follows. The method is applied to a target server and includes the following steps:

[0079] Upon receiving the version query request sent by the first device, obtaining second version information corresponding to the version query request, wherein the target server stores version information of multiple project templates, the second version information is version information of a second project template among the multiple project templates, and the second project template is a base template for other project templates;

[0080] Send the second version information to the first device.

[0081] In this embodiment, the target device includes version information of a basic template and version information of at least one extended template expanded based on the basic template. The first project template in the first device is the extended template, and the version query information is used to query the version information of the basic template.

[0082] Then, whenever the target server detects that a version query request is sent to the target server to query the version of the basic second project template, the second version information of the second project template can be obtained, and the second version information is further sent back to the first device, so that the first device compares the basic second version information with the expanded first version information.

[0083] In this embodiment, the method further includes:

[0084] In case of receiving the code update content sent by the third device, determining the third device corresponding to the code update content;

[0085] Determining third version information of a third project template in a third device;

[0086] The third version information is updated based on the code update content.

[0087] In this embodiment, the third device may be a second device including a basic second project template, or a first device including an expanded first project template, and the target server stores version information of project templates on all devices.

[0088] Similarly, when there is an update to the code in the third project template in the third device, the updated code update content can be obtained, and then the code update content can be sent to the target server. After receiving the code update content from the third device, the target server will identify and determine the current third version information of the third project template used on the third device. Then, the received code update content can be used to update the corresponding third version information on the third device. In this way, the records in the target server will reflect the latest template version status, ensuring that all version information is consistent with the actual situation.

[0089] In this way, whenever the project template in the third device is modified, the relevant information can be automatically and promptly transmitted to the backend for processing, thereby maintaining the consistency of the system and the synchronization of information.

[0090] Based on the project deployment method provided in the above embodiment, the present application also provides a specific implementation of the project deployment device. Please refer to the following embodiment.

[0091] See first Figure 2 The project deployment device 200 provided in the embodiment of the present application includes the following modules:

[0092] A first sending module 201 is used to send a version query request to a target server when there is a target project corresponding to a first project template that needs to be deployed, wherein the version query request is used to request to query second version information of a second project template on a second device, wherein the second project template is a base template of the first project template, the first project template is the second project template, or is a template that is an extension of the second project template;

[0093] A receiving module 202 is configured to receive second version information of the second project template fed back by the target server based on the version query request;

[0094] The deployment module 203 is used to deploy the target project to the first project template when the first version information of the first project template and the second version information of the second project template meet a preset matching condition.

[0095] The device can send a version query request to the target server when there is a target project that needs to be deployed on the first project template, the version query request is used to request to query the second version information of the second project template on the second device, wherein the second project template is the base template of the first project template, the first project template is the second project template, or a template that is an extension of the second project template; receive the second version information of the second project template fed back by the target server based on the version query request; and deploy the target project to the first project template when the first version information of the first project template and the second version information of the second project template meet the preset matching conditions. In this way, it can be ensured that each time a project is deployed to the first project template on the first device, the version of the first project template matches the version of the underlying second project template, thereby ensuring the compatibility of templates on different devices, avoiding potential problems caused by version incompatibility, and improving the stability of project deployment.

[0096] As an implementation of the present application, the deployment device 200 of the above-mentioned project may also include:

[0097] A first acquisition module, configured to acquire a minimum required version in the second version information when the template version in the first version information is different from the template version in the second version information;

[0098] The first determining module is used to determine that the first version information and the second version information meet a preset matching condition when the template version in the first version information is not lower than the minimum required version in the second version information.

[0099] As an implementation of the present application, the deployment device 200 of the above-mentioned project may also include:

[0100] a cancelling module, configured to cancel deployment of the target project to the first project template if the first version information of the first project template and the second version information of the second project template do not meet a preset matching condition;

[0101] The output module is used to output prompt information, where the prompt information is used to prompt that the first project template is incompatible with the basic second project template.

[0102] As an implementation of the present application, the deployment device 200 of the above-mentioned project may also include:

[0103] The synchronization module is used to send the updated first code update content to the target server when there is a code update in the first project template.

[0104] As an implementation of the present application, the deployment device 200 of the above-mentioned project may also include:

[0105] a second acquisition module, configured to, upon receiving a version query request sent by the first device, acquire second version information corresponding to the version query request, wherein the target server stores version information of multiple project templates, the second version information is version information of a second project template among the multiple project templates, and the second project template is a base template for other project templates;

[0106] The second sending module is configured to send the second version information to the first device.

[0107] As an implementation of the present application, the deployment device 200 of the above-mentioned project may also include:

[0108] No. Second, confirm A module, configured to determine, upon receiving code update content sent by a third device, a third device corresponding to the code update content;

[0109] A third determining module, used to determine third version information of a third project template in a third device;

[0110] An updating module is used to update the third version information based on the code update content.

[0111] The project deployment device provided in the embodiment of the present invention can implement each step in the above method embodiment, and will not be described again here to avoid repetition.

[0112] Figure 3 A schematic diagram of the hardware structure of a deployment device for a project provided in an embodiment of the present application is shown.

[0113] The deployment device of the project may include a processor 1001 and a memory 1002 storing computer program instructions.

[0114] Specifically, the processor 1001 may include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present application.

[0115] The memory 1002 may include a large capacity memory for data or instructions. By way of example and not limitation, the memory 1002 may include a hard disk drive (HDD), a floppy disk drive, a flash memory, an optical disk, a magneto-optical disk, a magnetic tape, or a universal serial bus (USB) drive or a combination of two or more of these. In appropriate cases, the memory 1002 may include a removable or non-removable (or fixed) medium. In appropriate cases, the memory 1002 may be inside or outside the integrated gateway disaster recovery device. In a specific embodiment, the memory 1002 is a non-volatile solid-state memory.

[0116] The memory may include read-only memory (ROM), random access memory (RAM), magnetic disk storage media devices, optical storage media devices, flash memory devices, electrical, optical or other physical / tangible memory storage devices. Thus, typically, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the method according to an aspect of the present disclosure.

[0117] The processor 1001 implements any one of the project deployment methods in the above embodiments by reading and executing computer program instructions stored in the memory 1002 .

[0118] In one example, the deployment device of the project may further include a communication interface 1003 and a bus 1010. Figure 3 As shown, the processor 1001, the memory 1002, and the communication interface 1003 are connected via a bus 1010 and communicate with each other.

[0119] The communication interface 1003 is mainly used to implement communication between various modules, devices, units and / or equipment in the embodiments of the present application.

[0120] Bus 1010 includes hardware, software or both, and the components of the deployment equipment of the project are coupled to each other. For example, but not limitation, the bus may include accelerated graphics port (AGP) or other graphics bus, enhanced industrial standard architecture (EISA) bus, front-side bus (FSB), hypertransport (HT) interconnection, industrial standard architecture (ISA) bus, infinite bandwidth interconnection, low pin count (LPC) bus, memory bus, micro channel architecture (MCA) bus, peripheral component interconnect (PCI) bus, PCI-Express (PCI-X) bus, serial advanced technology attachment (SATA) bus, video electronics standard association local (VLB) bus or other suitable bus or two or more of these combinations. In appropriate cases, bus 1010 may include one or more buses. Although the present application embodiment describes and shows a specific bus, the present application considers any suitable bus or interconnection.

[0121] The deployment equipment of the project can be based on the above-mentioned embodiment, so as to implement the deployment method and device combined with the above-mentioned project.

[0122] In addition, in combination with the project deployment method in the above embodiment, the embodiment of the present application may provide a computer storage medium to implement. The computer storage medium stores computer program instructions; when the computer program instructions are executed by the processor, the deployment method of any one of the projects in the above embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here. Among them, the above-mentioned computer-readable storage medium may include a non-transitory computer-readable storage medium, such as a read-only memory (Read-Only Memory, referred to as ROM), a random access memory (Random Access Memory, referred to as RAM), a disk or an optical disk, etc., which is not limited here.

[0123] In addition, an embodiment of the present application further provides a computer program product, including computer program instructions, which can implement the steps and corresponding contents of the aforementioned method embodiment when the computer program instructions are executed by a processor.

[0124] It should be clear that the present application is not limited to the specific configuration and processing described above and shown in the figures. For the sake of simplicity, a detailed description of the known method is omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of the present application is not limited to the specific steps described and shown, and those skilled in the art can make various changes, modifications and additions, or change the order between the steps after understanding the spirit of the present application.

[0125] The functional blocks shown in the above block diagram can be implemented as hardware, software, firmware or a combination thereof. When implemented in hardware, it can be, for example, an electronic circuit, an application specific integrated circuit (ASIC), appropriate firmware, a plug-in, a function card, etc. When implemented in software, the elements of the present application are programs or code segments that are used to perform the required tasks. The program or code segment can be stored in a machine-readable medium, or transmitted on a transmission medium or a communication link by a data signal carried in a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, optical fiber media, radio frequency (RF) links, etc. The code segment can be downloaded via a computer network such as the Internet, an intranet, etc.

[0126] It should also be noted that the exemplary embodiments mentioned in this application describe some methods or systems based on a series of steps or devices. However, this application is not limited to the order of the above steps, that is, the steps can be performed in the order mentioned in the embodiment, or in a different order from the embodiment, or several steps can be performed simultaneously.

[0127] Aspects of the present disclosure are described above with reference to the flowchart and / or block diagram of the method, device and computer program product according to the embodiment of the present disclosure. It should be understood that each box in the flowchart and / or block diagram and the combination of each box in the flowchart and / or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine so that these instructions executed by the processor of the computer or other programmable data processing device enable the implementation of the function / action specified in one or more boxes of the flowchart and / or block diagram. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field programmable logic circuit. It can also be understood that each box in the block diagram and / or flowchart and the combination of boxes in the block diagram and / or flowchart can also be implemented by dedicated hardware that performs a specified function or action, or can be implemented by a combination of dedicated hardware and computer instructions.

[0128] The above are only specific implementation methods of the present application. Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working processes of the systems, modules and units described above can refer to the corresponding processes in the aforementioned method embodiments, and will not be repeated here. It should be understood that the protection scope of the present application is not limited to this. Any technician familiar with the technical field can easily think of various equivalent modifications or replacements within the technical scope disclosed in this application, and these modifications or replacements should be included in the protection scope of this application.

Claims

1. A project deployment method, characterized in that: The method is applied to a first device, and the method includes: In the case where there is a target project corresponding to the first project template that needs to be deployed, sending a version query request to the target server, wherein the version query request is used to request querying second version information of the second project template on the second device, wherein the second project template is a base template of the first project template, the first project template is the second project template, or a template that is an extension of the second project template; receiving second version information of the second project template fed back by the target server based on the version query request; When the first version information of the first project template and the second version information of the second project template meet a preset matching condition, the target project is deployed to the first project template.

2. The project deployment method according to claim 1, characterized in that: The version information includes a template version and a minimum required version, and the first version information and the second version information belong to the version information; When the first version information of the first project template and the second version information of the second project template meet a preset matching condition, before deploying the target project to the first project template, the method further includes: When the template version in the first version information is different from the template version in the second version information, obtaining the minimum required version in the second version information; In a case where the template version in the first version information is not lower than the minimum required version in the second version information, it is determined that the first version information and the second version information meet a preset matching condition.

3. The project deployment method according to claim 1, characterized in that: After receiving the second version information of the second project template fed back by the target server based on the version query request, the method further includes: If the first version information of the first project template and the second version information of the second project template do not meet a preset matching condition, canceling deployment of the target project to the first project template; Outputting prompt information, wherein the prompt information is used to prompt that the first project template is incompatible with a basic second project template.

4. The project deployment method according to claim 1, characterized in that: The method further comprises: In the case where there is a code update in the first project template, the updated first code update content is sent to the target server.

5. A project deployment method, characterized in that: The method is applied to a target server, and the method comprises: Upon receiving the version query request sent by the first device, obtaining second version information corresponding to the version query request, wherein the target server stores version information of multiple project templates, the second version information is version information of a second project template among the multiple project templates, and the second project template is a base template for other project templates; Send the second version information to the first device.

6. The project deployment method according to claim 5, characterized in that: The method further comprises: In case of receiving the code update content sent by the third device, determining the third device corresponding to the code update content; Determining third version information of a third project template in a third device; The third version information is updated based on the code update content.

7. A project deployment device, characterized in that: The device comprises: A first sending module is used to send a version query request to a target server when there is a target project corresponding to a first project template that needs to be deployed, wherein the version query request is used to request to query second version information of a second project template on a second device, wherein the second project template is a base template of the first project template, the first project template is the second project template, or is a template that is an extension of the second project template; A receiving module, configured to receive second version information of the second project template fed back by the target server based on the version query request; A deployment module is used to deploy the target project to the first project template when the first version information of the first project template and the second version information of the second project template meet a preset matching condition.

8. A project deployment device, characterized in that: The deployment device of the project includes: a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, the method for deploying the project according to any one of claims 1 to 6 is implemented.

9. A computer storage medium, characterized in that The computer storage medium stores computer program instructions, which, when executed by a processor, implement the project deployment method according to any one of claims 1 to 6.

10. A computer program product, characterized in that The computer program product comprises computer program instructions, and when the computer program instructions are executed by a processor, the method for deploying the project according to any one of claims 1 to 6 is implemented.

Images