Application deployment system and method based on DevOps platform and electronic equipment

Abstract

The invention relates to the technical field of DevOps platforms, and discloses an application deployment system and method based on a DevOps platform and electronic equipment. According to the application, the dynamic application data is acquired by utilizing the dynamic Schame information corresponding to the target platform through the front-end module, and the corresponding target processor is determined for the application deployment platform through the rear-end module, so that the target application is deployed on the target platform by utilizing the target processor corresponding to the target platform according to the dynamic application data; on one hand, different dynamic application data are obtained by utilizing dynamic Schame information corresponding to different deployment platforms respectively, unified deployment of the different deployment platforms is realized, on the other hand, multiple proxy processors are firstly arranged, and then the proxy processors are allocated to the application deployment platforms, so that the proxy processors are reused to realize data unvarnished transmission capability, and the deployment efficiency is improved. According to the method, the application is deployed on the target platform, so that the code complexity and the maintenance cost of the DevOps platform are reduced from two aspects, and the application deployment efficiency of the DevOps platform is improved.

Description

Technical Field

[0001] The present invention relates to the technical field of DevOps platform, and in particular to an application deployment system, method and electronic device based on a DevOps platform. Background Art

[0002] In recent years, with the rapid development of cloud computing technology and the gradual deepening and widespread practice of containerization concepts in the IT industry, Kubernetes-based deployment management platforms have rapidly emerged. At the same time, with the popularization of microservice architecture and the growing demand of enterprises for rapid iteration and flexible deployment of applications, multi-environment isolation deployment scenarios have become more and more common. Enterprises need to efficiently run and manage applications independently in multiple environments such as development, testing, and production. Therefore, the DevOps (Development-Operations) platform that integrates development and operation functions has become one of the choices, thereby improving the efficiency of software development and deployment through automation and collaboration, while ensuring the quality and stability of the software.

[0003] However, since different deployment platforms may adopt different technology stacks, configuration requirements, and management strategies, DevOps platforms often need to customize specific operating procedures for each platform when deploying applications, which increases the complexity and maintenance costs of the platform, and thus seriously affects the application deployment efficiency of the DevOps platform. Summary of the invention

[0004] In order to provide a basic understanding of some aspects of the disclosed embodiments, a brief summary is given below. The summary is not an extensive review, nor is it intended to identify key / critical components or delineate the scope of protection of these embodiments, but rather serves as a prelude to the detailed description that follows.

[0005] In view of the above-mentioned shortcomings of the prior art, the present application discloses an application deployment system, method and electronic device based on a DevOps platform to improve the application deployment efficiency of the DevOps platform.

[0006] The present application discloses an application deployment system based on a DevOps platform, comprising: a front-end module, used to determine a target platform from an application deployment platform connected to the DevOps platform, and obtain dynamic Schame information corresponding to the target platform, so as to obtain dynamic application data corresponding to a target application according to the dynamic Schame information corresponding to the target platform, wherein the dynamic Schame information is used to carry a data structure and a data type corresponding to the dynamic application data; a back-end module, used to allocate a target processor to the application deployment platform from a preset proxy processor if the DevOps platform is connected to the application deployment platform; and to deploy the target application on the target platform according to the dynamic application data using the target processor corresponding to the target platform.

[0007] In one embodiment of the present application, the front-end module obtains the dynamic Schame information corresponding to the target platform in the following manner to obtain the dynamic application data corresponding to the target application according to the dynamic Schame information corresponding to the target platform: pre-setting the dynamic Schame information corresponding to each of the application deployment platforms; in response to the target platform, searching from the dynamic Schame information corresponding to each of the application deployment platforms to obtain the dynamic Schame information corresponding to the target platform; performing form rendering according to the dynamic Schame information corresponding to the target platform to form a dynamic form, and using the dynamic form to receive dynamic application data.

[0008] In one embodiment of the present application, the front-end module uses the dynamic form to receive dynamic application data in at least one of the following ways: if the dynamic form receives interface request information, encapsulates the dynamic interface request according to the interface request information, injects a preset first identifier into the dynamic interface request, and obtains a first data packet, wherein the first identifier is used to carry the platform identifier corresponding to the target platform; sends the first data packet to the back-end module, and uses the dynamic interface data fed back by the back-end module as dynamic application data; if the dynamic form receives dynamic entry information, uses the dynamic entry information as dynamic application data.

[0009] In one embodiment of the present application, the back-end module is also used to: in response to the first identifier, perform a search based on the platform identifier in the first identifier to obtain the target platform; input the dynamic interface request into the target processor corresponding to the target platform, trigger the target processor corresponding to the target platform to transmit the dynamic interface request to the platform interface of the target platform, and receive dynamic interface data fed back by the platform interface based on the dynamic interface request; and feed back the dynamic interface data to the front-end module.

[0010] In one embodiment of the present application, the back-end module allocates a target processor to the application deployment platform from a preset proxy processor in the following manner: obtaining interface Schame information corresponding to the application deployment platform, wherein the interface Schame information includes a platform interface corresponding to the application deployment platform; generating current matching parameters according to the interface Schame information, wherein the current matching parameters include the interface Schame information and / or a platform type corresponding to the application deployment platform, and the platform type is obtained by performing feature detection on the interface Schame information; matching is performed from a preset processor matching table according to the current matching parameters to obtain a processor matching result, wherein the processor matching table stores a correspondence between the original matching parameters and the proxy processor; if the processor matching result includes a proxy processor corresponding to the current matching parameter, the proxy processor corresponding to the current matching parameter is used as the target processor; if the processor matching result includes a matching failure, the preset default processor is used as the target processor.

[0011] In one embodiment of the present application, the front-end module is also used to: obtain public application data corresponding to the target application; generate a second data packet according to a preset second identifier, the public application data, and the dynamic application data, and send the second data packet to the back-end module.

[0012] In one embodiment of the present application, the back-end module deploys the target application on the target platform according to the dynamic application data using the target processor corresponding to the target platform in the following manner: in response to the second identifier, using the DevOps platform to process the public application data, and obtain the interface Schame information corresponding to the target platform, wherein the data processing includes data parsing and data warehousing, and the interface Schame information includes a platform interface set corresponding to the target platform; according to the interface Schame information, the dynamic application data is interface-encapsulated to obtain a proxy interface, and the platform identifier corresponding to the target platform is injected into the proxy interface; the proxy request is input into the target processor corresponding to the target platform, triggering the target processor corresponding to the target platform to determine the target platform according to the platform identifier in the proxy interface, and deploying the target application on the target platform through the proxy interface.

[0013] In one embodiment of the present application, the back-end module is also used to: obtain the current user permissions; if the current user permissions include the platform deployment permissions corresponding to the target platform, then deployment of the target application on the target platform is allowed; if the current user permissions do not include the platform deployment permissions corresponding to the target platform, then deployment of the target application on the target platform is prohibited.

[0014] The present application discloses an application deployment method based on a DevOps platform, comprising: if the DevOps platform is connected to an application deployment platform, allocating a target processor to the application deployment platform from a preset proxy processor; determining a target platform from the application deployment platform connected to the DevOps platform; obtaining dynamic Schame information corresponding to the target platform, so as to obtain dynamic application data corresponding to a target application according to the dynamic Schame information corresponding to the target platform, wherein the dynamic Schame information is used to carry a data structure and a data type corresponding to the dynamic application data; and deploying the target application on the target platform according to the dynamic application data using a target processor corresponding to the target platform.

[0015] The present application discloses an electronic device, comprising: a processor and a memory; the memory is used to store a computer program, and the processor is used to execute the computer program stored in the memory, so that the electronic device executes the above method.

[0016] Beneficial effects of this application:

[0017] The dynamic Schame information corresponding to the target platform is used to obtain dynamic application data through the front-end module, and the corresponding target processor is determined for the application deployment platform through the back-end module, so that the target application is deployed on the target platform according to the dynamic application data using the target processor corresponding to the target platform. In this way, on the one hand, the dynamic Schame information corresponding to different deployment platforms is used to obtain differentiated dynamic application data, so as to achieve unified deployment of different deployment platforms. On the other hand, multiple proxy processors are first set up, and then the proxy processors are assigned to the application deployment platform, so as to reuse the proxy processors to achieve data transparent transmission capabilities and deploy the application on the target platform. Therefore, the code complexity and maintenance cost of the DevOps platform are reduced from two aspects, thereby improving the application deployment efficiency of the DevOps platform. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 It is a schematic diagram of an interface of an application deployment system based on a DevOps platform in an embodiment of the present application;

[0019] Figure 2 It is an interface diagram of another application deployment system based on the DevOps platform in an embodiment of the present application;

[0020] Figure 3 It is a flowchart of a dynamic interface data acquisition method in an embodiment of the present application;

[0021] Figure 4 It is a flow chart of an application deployment method based on a DevOps platform in an embodiment of the present application;

[0022] Figure 5 It is a flowchart of another application deployment method based on the DevOps platform in an embodiment of the present application;

[0023] Figure 6 It is a schematic diagram of the structure of an electronic device in an embodiment of the present invention. DETAILED DESCRIPTION

[0024] The following describes the embodiments of the present invention through specific examples, and those skilled in the art can easily understand other advantages and effects of the present invention from the contents disclosed in this specification. The present invention can also be implemented or applied through other different specific embodiments, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present invention. It should be noted that the following embodiments and sub-samples in the embodiments can be combined with each other without conflict.

[0025] It should be noted that the illustrations provided in the following embodiments are only schematic illustrations of the basic concept of the present invention, and thus the drawings only show components related to the present invention rather than being drawn according to the number, shape and size of components in actual implementation. In actual implementation, the type, quantity and proportion of each component may be changed arbitrarily, and the component layout may also be more complicated.

[0026] In the following description, numerous details are discussed to provide a more thorough explanation of the embodiments of the present invention. However, it is obvious to those skilled in the art that the embodiments of the present invention can be implemented without these specific details. In other embodiments, well-known structures and devices are shown in the form of block diagrams rather than in detail to avoid making the embodiments of the present invention difficult to understand.

[0027] The terms "first", "second", etc. in the specification and claims of the embodiments of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the terms used in this way can be interchanged where appropriate, so that the embodiments of the embodiments of the present disclosure described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions.

[0028] Unless otherwise stated, the term "plurality" means two or more.

[0029] In the embodiment of the present disclosure, the character " / " indicates that the preceding and following objects are in an "or" relationship. For example, A / B indicates: A or B.

[0030] The term "and / or" is a description of the association relationship between objects, indicating that three relationships can exist. For example, A and / or B means: A or B, or, A and B.

[0031] Combination Figure 1 As shown, an embodiment of the present disclosure provides an application deployment system based on a DevOps platform, including a front-end module 101 and a back-end module 102 .

[0032] The front-end module 101 is used to determine the target platform from the application deployment platform accessed by the DevOps platform, and obtain the dynamic Schame information corresponding to the target platform, so as to obtain the dynamic application data corresponding to the target application according to the dynamic Schame information corresponding to the target platform, wherein the dynamic Schame information is used to carry the data structure and data type corresponding to the dynamic application data.

[0033] The backend module 102 is used to allocate a target processor from a preset proxy processor to the application deployment platform if the DevOps platform is connected to the application deployment platform; and deploy the target application on the target platform according to the dynamic application data using the target processor corresponding to the target platform.

[0034] The application deployment system based on the DevOps platform provided by the embodiment of the present disclosure is adopted. The dynamic Schame information corresponding to the target platform is used to obtain dynamic application data through the front-end module, and the corresponding target processor is determined for the application deployment platform through the back-end module, so as to use the target processor corresponding to the target platform to deploy the target application on the target platform according to the dynamic application data. In this way, on the one hand, the dynamic Schame information corresponding to different deployment platforms is used to obtain differentiated dynamic application data, so as to realize the unified deployment of different deployment platforms. On the other hand, a variety of proxy processors are first set, and then the proxy processors are allocated to the application deployment platform, so as to reuse the proxy processors to realize the data transparent transmission capability and deploy the application on the target platform. Therefore, the code complexity and maintenance cost of the DevOps platform are reduced from two aspects, thereby improving the application deployment efficiency of the DevOps platform.

[0035] Combination Figure 2 As shown, an embodiment of the present disclosure provides an application deployment system based on a DevOps platform, including a front-end module 101 and a back-end module 102 .

[0036] The front-end module 101 is used to determine the target platform from the application deployment platform accessed by the DevOps platform.

[0037] In some embodiments, the front-end module stores public application data and custom attributes of each application deployment platform in dynamic Schame information.

[0038] In some embodiments, if the DevOps platform is connected to the application deployment platform, the platform information of the application deployment platform, such as platform identification, platform authentication information, platform authentication method, interface address information and interface authentication information, is entered through the front-end module.

[0039] The front-end module 101 is provided with an application component 1011, which is used to obtain the dynamic Schame information corresponding to the target platform through the application component, so as to obtain the dynamic application data corresponding to the target application according to the dynamic Schame information corresponding to the target platform; generate an interface request according to the dynamic application data, so as to generate a data packet to be sent according to the first identifier and the interface request, and send the data packet to be sent to the back-end module; generate a data packet to be sent according to the second identifier, the dynamic application data, and the public application data, and send the data packet to be sent to the back-end module.

[0040] Optionally, the front-end module obtains the dynamic Schame information corresponding to the target platform in the following manner to obtain the dynamic application data corresponding to the target application according to the dynamic Schame information corresponding to the target platform: pre-setting the dynamic Schame information corresponding to each application deployment platform; in response to the target platform, searching from the dynamic Schame information corresponding to each application deployment platform to obtain the dynamic Schame information corresponding to the target platform; performing form rendering according to the dynamic Schame information corresponding to the target platform to form a dynamic form, and using the dynamic form to receive dynamic application data.

[0041] In some embodiments, the dynamic Schame information carries the data structure and data type corresponding to the dynamic application data. At the same time, the dynamic Schame information defines the display method and interaction method of the form interface; the front-end module renders the form through the dynamic Schame information to form a dynamic form, so as to display different dynamic Schame information based on the target platform selected by the user, wherein the dynamic Schame information includes the dynamic application data required for deployment of the corresponding deployment platform. The dynamic application data can be the dynamic entry information input by the user, or it can generate a dynamic interface request based on the interface request information input by the user, and collect the dynamic interface data from the target platform through the dynamic interface request.

[0042] In this way, through the dynamic Schame information definition of the front-end module and the interactive API of each deployment platform, as well as the data format and front-end form display, application information can be dynamically input. Regardless of different deployment platforms or different versions of the same deployment platform, new platform access can be dynamically realized without modifying the front-end, making docking with multiple platforms more seamless and more compatible.

[0043] Optionally, the front-end module receives dynamic application data using a dynamic form in the following manner: if the dynamic form receives interface request information, encapsulates the dynamic interface request according to the interface request information, injects a preset first identifier into the dynamic interface request, and obtains a first data packet, wherein the first identifier is used to carry a platform identifier corresponding to the target platform; sends the first data packet to the back-end module, and uses the dynamic interface data fed back by the back-end module as dynamic application data.

[0044] In some embodiments, the front-end module includes a dynamic form component, which can generate different form items according to different configurations, such as input boxes, drop-down selection boxes, etc., wherein the user enters data or selects options through the form, and these data will be used as interface request information; when the user submits the form, the front-end module listens to the form submission event and obtains the interface request information input by the user, wherein this information includes the field values ​​filled in by the user, the selected options, etc.; based on the received interface request information, the front-end module encapsulates a dynamic interface request, wherein the dynamic interface request includes the interface URL, etc.; when encapsulating the request, a preset first identifier is injected into the request header, wherein the first identifier is used by the back-end module to identify and process requests for a specific platform; after the front-end module receives the dynamic interface data returned by the back-end module, it processes it as dynamic application data.

[0045] Optionally, the front-end module receives the dynamic application data using the dynamic form in the following manner: if the dynamic form receives dynamic input information, the dynamic input information is used as the dynamic application data.

[0046] Optionally, the front-end module is further used to: obtain public application data corresponding to the target application; generate a second data packet according to a preset second identifier, public application data, and dynamic application data, and send the second data packet to the back-end module.

[0047] The backend module 102 includes a platform access module 1021 , a data processing module 1022 , a processor abstraction layer 1023 and a proxy processor.

[0048] The platform access module 1021 is used to manage the platform information of the application deployment platform, manage user permissions, verify the connectivity of the application deployment platform, determine the target processor, etc.

[0049] In some embodiments, the backend module verifies the connectivity of the application deployment platform; if the application deployment platform cannot be connected, the DevOps platform does not access the application deployment platform; if the application deployment platform passes the connectivity verification, the DevOps platform is allowed to use the application deployment platform.

[0050] In this way, the back-end module uniformly handles the authentication issues, authentication conversion and request encapsulation of each platform, and realizes centralized management and control of user permissions between different platforms.

[0051] Optionally, the back-end module allocates a target processor to the application deployment platform from a preset proxy processor in the following manner: obtaining interface Schame information corresponding to the application deployment platform, wherein the interface Schame information includes a platform interface corresponding to the application deployment platform; generating current matching parameters according to the interface Schame information, wherein the current matching parameters include the interface Schame information and / or the platform type corresponding to the application deployment platform, and the platform type is obtained by performing feature detection on the interface Schame information; matching from a preset processor matching table according to the current matching parameters to obtain a processor matching result, wherein the processor matching table stores a correspondence between the original matching parameters and the proxy processor; if the processor matching result includes a proxy processor corresponding to the current matching parameter, then the proxy processor corresponding to the current matching parameter is used as the target processor; if the processor matching result includes a matching failure, then the preset default processor is used as the target processor.

[0052] In some embodiments, the interface Schame information corresponding to the application deployment platform includes the set of operation interfaces required by the application deployment platform to deploy the target application, so as to encapsulate the corresponding proxy interface; the interface Schame information corresponding to the OpenAPI is extracted from the interface Schame information corresponding to the application deployment platform to obtain key interface information, and a proxy processor is recommended to the application deployment platform according to different definitions of the key interface information.

[0053] In some embodiments, some application deployment platforms have built-in feature matching and feature detection. Application deployment platforms of the same mainstream platform type have the same platform features. The platform type corresponding to the application deployment platform is obtained by performing feature detection on the interface Schame information, thereby recommending a proxy processor to application deployment platforms of the same platform type.

[0054] In some embodiments, the target processor is displayed to the user, and in order to increase the flexibility of selecting the proxy processor, the user is supported to subsequently select the desired proxy processor by modifying the target processor or Schame information.

[0055] In some embodiments, the back-end module is further configured to: if a processor change instruction corresponding to the target processor is received, update the target processor according to the processor change instruction.

[0056] In some embodiments, the backend module is further used to: if an information change instruction corresponding to the target processor is received, then the interface Schame information corresponding to the application deployment platform is changed according to the information change instruction, and the target processor is updated according to the changed interface Schame information.

[0057] The data processing module 1022 is used to unpack the public application data and dynamic application data from the second data packet if the second identifier is received; perform data analysis and data storage on the public application data; strip the dynamic application data, and encapsulate the stripped dynamic application data using the interface Schame information of the target platform to obtain the proxy interface corresponding to the target platform, and send the proxy interface to the processor abstraction layer 1023.

[0058] Optionally, the back-end module deploys the target application on the target platform according to the dynamic application data using the target processor corresponding to the target platform in the following manner: in response to the second identifier, using the DevOps platform to process the public application data, and obtaining the interface Schame information corresponding to the target platform, wherein data processing includes data parsing and data warehousing, and the interface Schame information includes a platform interface set corresponding to the target platform; performing interface encapsulation on the dynamic application data according to the interface Schame information to obtain a proxy interface, and injecting the platform identifier corresponding to the target platform into the proxy interface; inputting the proxy request into the target processor corresponding to the target platform, triggering the target processor corresponding to the target platform to determine the target platform according to the platform identifier in the proxy interface, and deploying the target application on the target platform through the proxy interface.

[0059] The processor abstraction layer 1023 is used to verify the current user authority; if the first identifier is received, the dynamic interface request in the first data packet is input into the proxy processor 1024; if the proxy interface is received, the first identifier is injected into the proxy interface, and the proxy interface with the first identifier is input into the proxy processor 1024.

[0060] Optionally, the backend module is also used to: obtain the current user permissions; if the current user permissions include the platform deployment permissions corresponding to the target platform, then deployment of the target application on the target platform is allowed; if the current user permissions do not include the platform deployment permissions corresponding to the target platform, then deployment of the target application on the target platform is prohibited.

[0061] Optionally, the back-end module is also used to: respond to the first identifier, search according to the platform identifier in the first identifier to obtain the target platform; input the dynamic interface request into the target processor corresponding to the target platform, trigger the target processor corresponding to the target platform to transmit the dynamic interface request to the platform interface of the target platform, and receive dynamic interface data fed back by the platform interface based on the dynamic interface request; and feed back the dynamic interface data to the front-end module.

[0062] The proxy processor 1024 is used to, if a dynamic interface request is received, transmit the dynamic interface request to the platform interface of the target platform; if a proxy interface is received, determine the target platform according to the platform identifier in the proxy interface, and deploy the target application on the target platform through the proxy interface.

[0063] In some embodiments, the proxy handler acts as an intermediary between the DevOps platform and the application deployment platform, mainly realizing the interface transparent transmission capability, wherein the default handler directly transmits the interface request to the target platform without performing data logic processing, and transmits the result returned by the target platform back to the DevOps platform, while the specific proxy handler has user-defined implementation logic. At the same time, the specific proxy handler can call the implementation logic of the default handler, thereby realizing code reuse and reducing code writing.

[0064] In this way, the backend module sets up a proxy processor. For the default proxy processor, the conventional data transmission capability is realized, which can effectively handle application deployment. If some additional docking logic needs to be implemented, the backend module also supports custom platform proxy processors, thereby simplifying the docking management of multiple deployment platforms.

[0065] Combination Figure 3 As shown, the embodiment of the present disclosure provides a method for acquiring dynamic interface data, including:

[0066] Step S301, the front-end module selects a target platform for target application entry;

[0067] Step S302, the front-end module obtains the platform identifier and dynamic Schame information corresponding to the target platform, and obtains interface request information according to the dynamic Schame information;

[0068] Step S303, the front-end module encapsulates the dynamic interface request according to the interface request information, injects the first identifier into the dynamic interface request, and obtains a first data packet;

[0069] The first identifier includes / proxy / {platformId}, where "proxy" is used to represent a "proxy processor" and "platformId" is used to carry the platform identifier of the target platform;

[0070] Step S304, the front-end module sends a first data packet to the back-end module;

[0071] The data packet to be sent includes an interface request and a first identifier;

[0072] Step S305, the backend module queries the platform authentication information of the target platform according to the platform identifier in the first data packet, and sets the DevOps platform according to the platform authentication information;

[0073] Step S306, the backend module queries whether the current user has the authority of the target platform;

[0074] Step S307, if the current user has the permission, the backend module sends a dynamic interface request to the target processor corresponding to the target platform;

[0075] Step S308, the backend module transparently transmits the dynamic interface request to the target platform through the target processor corresponding to the target platform;

[0076] Step S309, if the platform authentication information is verified, the target platform processes the dynamic interface request and obtains dynamic interface data;

[0077] Step S310, the target platform sends dynamic interface data to the target processor;

[0078] Step S311, the back-end module sends dynamic interface data to the front-end module;

[0079] Step S312: the front-end module displays dynamic interface data.

[0080] In some embodiments, the application deployment system is in the preparation stage, and needs to complete the setting of the proxy processor, the setting of the dynamic Schame information corresponding to the application deployment platform, the setting of the interface Schame information corresponding to the application deployment platform, etc.; after the preparation stage, the application deployment system is in the platform access stage, and needs to complete the entry of the platform information of the application deployment platform, the recommendation of the target processor to the application deployment platform, the verification of the platform connectivity of the application deployment platform, the access to the application deployment platform, etc.; after accessing the node, the application deployment system determines the target platform selected by the user through the front-end module, renders the form according to the dynamic Schame information corresponding to the target platform, and uses the form to obtain dynamic application information, wherein the dynamic application information includes the dynamic entry information directly input by the user and the dynamic interface information collected through the target platform interface, and the dynamic interface information needs to be transparently transmitted by the proxy server in the back-end module; if the front-end module obtains all the dynamic application information, the second identifier, the public application information, and the dynamic application information are sent to the back-end module, so that the back-end module uses the target processor corresponding to the target platform to implement application deployment.

[0081] Combination Figure 4 As shown, the embodiment of the present disclosure provides an application deployment method based on a DevOps platform, including:

[0082] Step S401, the front-end module pre-sets public application data;

[0083] Step S402, the front-end module selects a target platform for target application entry;

[0084] Step S403, the front-end module obtains dynamic application data according to the dynamic Schame information corresponding to the target platform;

[0085] Among them, rendering is performed according to the dynamic Schame information to form a form, and the form is filled out through user input, user selection, platform interface collection, etc. to obtain dynamic application data;

[0086] Step S404, the front-end module generates a second data packet according to the second identifier, the public application data, and the dynamic application data;

[0087] The second identifier includes / api / app / **, where “**” represents public application data and dynamic application data;

[0088] Step S405, the front-end module sends a second data packet to the back-end module;

[0089] Step S406, the backend module performs data analysis and data storage on the public application data in response to the second identifier;

[0090] Step S407, the backend module encapsulates the dynamic application data according to the interface Schame information corresponding to the target platform, obtains the proxy interface corresponding to the target platform, and injects the first identifier as a prefix into the proxy interface;

[0091] Step S408, the backend module sends the proxy interface to the target processor corresponding to the target platform;

[0092] Step S409, the backend module determines the target platform according to the platform identifier in the first identifier through the target processor corresponding to the target platform;

[0093] Step S410, the backend module uses the target processor corresponding to the target platform to process the proxy interface to deploy the target application on the target platform;

[0094] Among them, since the dynamic application data needs to use the platform interface of the target platform, the platform interface needs to be transmitted to the target processor to realize application deployment through the data transmission capability of the target processor.

[0095] In this way, the DevOps platform-based application deployment method provided by the embodiment of the present disclosure uses the dynamic Schame information corresponding to the target platform to obtain dynamic application data through the front-end module, and determines the corresponding target processor for the application deployment platform through the back-end module, so as to use the target processor corresponding to the target platform to deploy the target application on the target platform according to the dynamic application data, which has the following advantages:

[0096] First, the front-end and back-end modules use dynamic and scalable mechanisms to simplify and speed up access to the entire platform;

[0097] Second, preset default processors and proxy processors to recommend target processors to different application deployment platforms, minimizing platform access costs as much as possible. This allows for rapid and dynamic expansion without intruding on DevOps processes and codes.

[0098] Third, for common authentication, permissions are handled in a unified manner. During platform access, there is no need to do special processing for each platform separately, which reduces development costs and access costs.

[0099] Combination Figure 5 As shown, the embodiment of the present disclosure provides an application deployment method based on a DevOps platform, including:

[0100] Step S501: if the DevOps platform is connected to the application deployment platform, a target processor is allocated to the application deployment platform from the preset proxy processors;

[0101] Step S502, determining a target platform from application deployment platforms accessed by the DevOps platform;

[0102] Step S503, obtaining dynamic Schame information corresponding to the target platform, so as to obtain dynamic application data corresponding to the target application according to the dynamic Schame information corresponding to the target platform, wherein the dynamic Schame information is used to carry the data structure and data type corresponding to the dynamic application data;

[0103] Step S504: deploy the target application on the target platform according to the dynamic application data using the target processor corresponding to the target platform.

[0104] By adopting the application deployment method based on the DevOps platform provided by the embodiment of the present disclosure, the dynamic Schame information corresponding to the target platform is used to obtain dynamic application data through the front-end module, and the corresponding target processor is determined for the application deployment platform through the back-end module, so as to use the target processor corresponding to the target platform to deploy the target application on the target platform according to the dynamic application data. In this way, on the one hand, the dynamic Schame information corresponding to different deployment platforms is used to obtain differentiated dynamic application data, so as to realize the unified deployment of different deployment platforms. On the other hand, a variety of proxy processors are first set, and then the proxy processors are allocated to the application deployment platform, so as to reuse the proxy processors to realize the data transparent transmission capability and deploy the application on the target platform. Therefore, the code complexity and maintenance cost of the DevOps platform are reduced from two aspects, thereby improving the application deployment efficiency of the DevOps platform.

[0105] An embodiment of the present disclosure further provides an electronic device, including: a processor and a memory; the memory is used to store a computer program, and the processor is used to execute the computer program stored in the memory, so that the electronic device executes the above method.

[0106] Figure 6 The structure diagram of the computer system suitable for implementing the electronic device of the embodiment of the present application is shown. It should be noted that: Figure 6 The computer system 600 of the electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0107] like Figure 6 As shown, the computer system 600 includes a central processing unit (CPU) 601, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 602 or the program loaded from the storage part 608 to the random access memory (RAM) 603, such as executing the method in the above embodiment. In the random access memory 603, various programs and data required for system operation are also stored. The central processing unit 601, the read-only memory 602 and the random access memory 603 are connected to each other through a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

[0108] The following components are connected to the input / output interface 605: an input section 606 including a keyboard, a mouse, etc.; an output section 607 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 608 including a hard disk, etc.; and a communication section 609 including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication section 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to the input / output interface 605 as needed. A removable medium 611, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 610 as needed so that a computer program read therefrom is installed into the storage section 608 as needed.

[0109] In particular, according to an embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a computer program for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication section 609, and / or installed from a removable medium 611. When the computer program is executed by a central processing unit (CPU) 601, various functions defined in the system of the present application are executed.

[0110] The above description and the accompanying drawings fully illustrate the embodiments of the present disclosure so that those skilled in the art can practice them. Other embodiments may include structural, logical, electrical, process and other changes. The embodiments represent possible changes only. Unless explicitly required, separate components and functions are optional, and the order of operation can be changed. Parts and sub-samples of some embodiments may be included in or replace parts and sub-samples of other embodiments. Moreover, the words used in this application are only used to describe the embodiments and are not used to limit the claims. As used in the description of the embodiments and the claims, unless the context clearly indicates, the singular forms of "a", "an" and "the" are intended to include plural forms as well. Similarly, the term "and / or" as used in this application refers to any and all possible combinations of listings containing one or more associated ones. In addition, when used in the present application, the term "comprise" and its variants "comprises" and / or comprising refer to the presence of a stated sub-sample, whole, step, operation, element, and / or component, but do not exclude the presence or addition of one or more other sub-samples, wholes, steps, operations, elements, components and / or groups of these. In the absence of further restrictions, the elements defined by the sentence "comprising a ..." do not exclude the presence of other identical elements in the process, method or device comprising the elements. In this article, each embodiment may focus on the differences from other embodiments, and the same and similar parts between the various embodiments may refer to each other. For the methods, products, etc. disclosed in the embodiments, if they correspond to the method part disclosed in the embodiments, then the relevant parts can refer to the description of the method part.

[0111] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software may depend on the specific application and design constraints of the technical solution. Technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the embodiments of the present disclosure. Technicians can clearly understand that for the convenience and simplicity of description, the specific working process of the above-described system, device and unit can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here.

[0112] In the embodiments disclosed herein, the disclosed methods and products (including but not limited to devices, equipment, etc.) can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of units can be only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some sub-samples can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between each other shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms. The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to implement this embodiment. In addition, each functional unit in the embodiment of the present disclosure may be integrated in a processing unit, or each unit may exist physically alone, or two or more units may be integrated in one unit.

[0113] The flowchart and block diagram in the accompanying drawings show the possible architecture, functions and operations of the system, method and computer program product according to the embodiment of the present disclosure. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of the code, and a part of the module, program segment or code contains one or more executable instructions for realizing the specified logical function. In some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, which can depend on the functions involved. In the description corresponding to the flowchart and block diagram in the accompanying drawings, the operations or steps corresponding to different boxes can also occur in a different order from the order disclosed in the description, and sometimes there is no specific order between different operations or steps. For example, two consecutive operations or steps can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, which can depend on the functions involved. Each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented by a dedicated hardware-based system that performs the specified functions or actions, or may be implemented by a combination of dedicated hardware and computer instructions.

Claims

1. An application deployment system based on a DevOps platform, characterized in that: include: A front-end module, used to determine a target platform from the application deployment platform accessed by the DevOps platform, and obtain dynamic Schame information corresponding to the target platform, so as to obtain dynamic application data corresponding to the target application according to the dynamic Schame information corresponding to the target platform, wherein the dynamic Schame information is used to carry the data structure and data type corresponding to the dynamic application data; The back-end module is used to allocate a target processor from a preset proxy processor to the application deployment platform if the DevOps platform is connected to the application deployment platform; and to deploy the target application on the target platform according to the dynamic application data using the target processor corresponding to the target platform.

2. The system according to claim 1, characterized in that The front-end module obtains the dynamic Schame information corresponding to the target platform in the following manner, so as to obtain the dynamic application data corresponding to the target application according to the dynamic Schame information corresponding to the target platform: Pre-setting the dynamic Schame information corresponding to each of the application deployment platforms; In response to the target platform, searching from the dynamic Schame information corresponding to each of the application deployment platforms to obtain the dynamic Schame information corresponding to the target platform; The form is rendered according to the dynamic Schame information corresponding to the target platform to form a dynamic form, and the dynamic application data is received using the dynamic form.

3. The system according to claim 2, characterized in that The front-end module receives dynamic application data using the dynamic form in at least one of the following ways: If the dynamic form receives the interface request information, encapsulate the dynamic interface request according to the interface request information, inject a preset first identifier into the dynamic interface request, and obtain a first data packet, wherein the first identifier is used to carry the platform identifier corresponding to the target platform; send the first data packet to the back-end module, and use the dynamic interface data fed back by the back-end module as dynamic application data; If the dynamic form receives dynamic input information, the dynamic input information is used as dynamic application data.

4. The system according to claim 3, characterized in that The backend module is also used for: In response to the first identifier, searching according to the platform identifier in the first identifier to obtain the target platform; Inputting the dynamic interface request into the target processor corresponding to the target platform, triggering the target processor corresponding to the target platform to transparently transmit the dynamic interface request to the platform interface of the target platform, and receiving dynamic interface data fed back by the platform interface based on the dynamic interface request; The dynamic interface data is fed back to the front-end module.

5. The system according to claim 1, characterized in that The backend module allocates a target processor from a preset proxy processor to the application deployment platform in the following manner: Obtaining interface Schame information corresponding to the application deployment platform, wherein the interface Schame information includes a platform interface corresponding to the application deployment platform; Generate a current matching parameter according to the interface Schame information, wherein the current matching parameter includes the interface Schame information and / or a platform type corresponding to the application deployment platform, and the platform type is obtained by performing feature detection on the interface Schame information; Matching from a preset processor matching table according to the current matching parameters to obtain a processor matching result, wherein the processor matching table stores a correspondence between the original matching parameters and the proxy processor; If the processor matching result includes the proxy processor corresponding to the current matching parameter, taking the proxy processor corresponding to the current matching parameter as the target processor; If the processor matching result includes a matching failure, a preset default processor is used as a target processor.

6. The system according to claim 1, characterized in that The front-end module is also used for: Acquire public application data corresponding to the target application; A second data packet is generated according to the preset second identifier, the public application data, and the dynamic application data, and the second data packet is sent to the back-end module.

7. The system according to claim 6, characterized in that The backend module deploys the target application on the target platform according to the dynamic application data by using the target processor corresponding to the target platform in the following manner: In response to the second identifier, the public application data is processed using the DevOps platform, and interface Schame information corresponding to the target platform is obtained, wherein the data processing includes data parsing and data warehousing, and the interface Schame information includes a platform interface set corresponding to the target platform; Performing interface encapsulation on the dynamic application data according to the interface Schame information to obtain a proxy interface, and injecting a platform identifier corresponding to the target platform into the proxy interface; The proxy request is input into a target processor corresponding to the target platform, triggering the target processor corresponding to the target platform to determine the target platform according to the platform identifier in the proxy interface, and deploying the target application on the target platform through the proxy interface.

8. The system according to claim 1, characterized in that The backend module is also used for: Get the current user's permissions; If the current user authority includes the platform deployment authority corresponding to the target platform, deployment of the target application on the target platform is allowed; If the current user permission does not have the platform deployment permission corresponding to the target platform, deployment of the target application on the target platform is prohibited.

9. An application deployment method based on a DevOps platform, characterized in that: include: If the DevOps platform is connected to the application deployment platform, a target processor is allocated to the application deployment platform from a preset proxy processor; Determine a target platform from application deployment platforms accessed by the DevOps platform; Acquire dynamic Schame information corresponding to the target platform, so as to acquire dynamic application data corresponding to the target application according to the dynamic Schame information corresponding to the target platform, wherein the dynamic Schame information is used to carry the data structure and data type corresponding to the dynamic application data; The target application is deployed on the target platform according to the dynamic application data using a target processor corresponding to the target platform.

10. An electronic device, characterized in that: include: Processor and memory; The memory is used to store a computer program, and the processor is used to execute the computer program stored in the memory, so that the electronic device executes the method as claimed in claim 9.

Images