Cloud platform environment deployment method and device based on Jenkins, equipment and medium

Abstract

The embodiment of the invention discloses a cloud platform environment deployment method and device based on Jenkins, equipment and a medium. The method comprises the following steps: acquiring at least two pieces of environment deployment information for performing environment deployment on a target cloud platform; wherein the target cloud platform comprises a plurality of environment deployment interfaces; calling a user-defined plug-in pre-installed in Jenkins, and constructing each piece of environment deployment information into a corresponding environment deployment request; wherein the user-defined plug-in is used for deploying a plurality of environments in the target cloud platform; and calling a target deployment interface matched with each environment deployment request in the plurality of environment deployment interfaces based on each environment deployment request, so as to deploy a plurality of environments in the target cloud platform. According to the technical scheme provided by the embodiment of the invention, multiple environments are automatically deployed for the cloud platform by using Jenkins, the complexity and risk of multi-environment deployment of the cloud platform are reduced, and the efficiency of multi-environment deployment of the cloud platform is further improved.

Description

Technical Field

[0001] Embodiments of the present invention relate to the field of computer technology, and in particular to a cloud platform environment deployment method, device, equipment and medium based on Jenkins. Background Art

[0002] Cloud platform environment deployment refers to the process of building, configuring and deploying various environments and resources required for applications on cloud platforms using cloud computing technology. In related technologies, Jenkins plug-ins are usually used for environment deployment. However, the functions of Jenkins plug-ins are relatively limited and only support the configuration and deployment of a single environment. Therefore, when deploying multiple environments on a cloud platform, it is often necessary to install cloud platform plug-ins on each Jenkins instance and perform tedious environment configuration. This process is not only complicated, but also prone to errors, which increases the complexity and risk of cloud platform environment deployment. Therefore, there is an urgent need for a cloud platform multi-environment deployment method based on Jenkins to automatically deploy multiple environments for the cloud platform. Summary of the invention

[0003] The present invention provides a cloud platform environment deployment method, device, equipment and medium based on Jenkins, so as to realize the automatic deployment of multiple environments for the cloud platform using Jenkins, reduce the complexity and risk of the multi-environment deployment of the cloud platform, and further improve the efficiency of the multi-environment deployment of the cloud platform.

[0004] According to one aspect of the present invention, a cloud platform environment deployment method based on Jenkins is provided, the method comprising:

[0005] Obtain at least two pieces of environment deployment information for environment deployment on a target cloud platform; wherein the target cloud platform includes a plurality of environment deployment interfaces;

[0006] Calling a custom plug-in pre-installed in Jenkins to construct each of the environment deployment information into a corresponding environment deployment request; wherein the custom plug-in is used to deploy multiple environments in the target cloud platform;

[0007] Based on each of the environment deployment requests, a target deployment interface among the multiple environment deployment interfaces that matches each of the environment deployment requests is called to deploy multiple environments in the target cloud platform.

[0008] Optionally, calling a custom plug-in pre-installed in Jenkins to construct each environment deployment information into a corresponding environment deployment request includes: for each environment deployment information, calling a custom plug-in pre-installed in Jenkins to construct the environment deployment information into an environment deployment request corresponding to the environment deployment information.

[0009] Optionally, the environment deployment information includes at least the regional identifier, domain name and credential information of the environment to be deployed; and constructing the environment deployment information into an environment deployment request corresponding to the environment deployment information includes: according to the HTTP communication protocol, performing information splicing processing on the regional identifier, domain name and credential information of the environment to be deployed to obtain an environment deployment request corresponding to the environment deployment information.

[0010] Optionally, calling a custom plug-in pre-installed in Jenkins includes: based on an environment deployment command in a target pipeline pre-created in Jenkins, calling the custom plug-in pre-installed in Jenkins.

[0011] Optionally, calling a target deployment interface among the multiple environment deployment interfaces that matches each environment deployment request based on each environment deployment request includes: authenticating the environment deployment request for each environment deployment request, and if the environment deployment request passes the authentication, calling a target deployment interface among the multiple environment deployment interfaces that matches the environment deployment request.

[0012] Optionally, the method further includes: generating a custom plug-in installable in Jenkins in response to a file compiling operation on a code file of the custom plug-in.

[0013] Optionally, the custom plug-in is used to deploy at least two environments among a development environment, a test environment, and a production environment in the target platform.

[0014] According to another aspect of the present invention, a cloud platform environment deployment device based on Jenkins is provided. The device comprises:

[0015] An information acquisition module, used to acquire at least two pieces of environment deployment information for environment deployment on a target cloud platform; wherein the target cloud platform includes a plurality of environment deployment interfaces;

[0016] A request building module, used to call a custom plug-in pre-installed in Jenkins to build each of the environment deployment information into a corresponding environment deployment request; wherein the custom plug-in is used to deploy multiple environments in the target cloud platform;

[0017] The environment deployment module is used to call the target deployment interface matching each of the environment deployment requests among the multiple environment deployment interfaces based on each of the environment deployment requests, so as to deploy multiple environments in the target cloud platform.

[0018] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:

[0019] at least one processor; and

[0020] a memory communicatively connected to the at least one processor; wherein,

[0021] The memory stores a computer program that can be executed by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the Jenkins-based cloud platform environment deployment method described in any embodiment of the present invention.

[0022] According to another aspect of the present invention, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the Jenkins-based cloud platform environment deployment method described in any embodiment of the present invention when executed.

[0023] The technical solution of the embodiment of the present invention is to obtain at least two environment deployment information for environment deployment on the target cloud platform; wherein the target cloud platform includes multiple environment deployment interfaces; call a custom plug-in pre-installed in Jenkins to construct each of the environment deployment information into a corresponding environment deployment request; wherein the custom plug-in is used to deploy multiple environments in the target cloud platform; based on each of the environment deployment requests, call the target deployment interface in the multiple environment deployment interfaces that matches each of the environment deployment requests to deploy multiple environments in the target cloud platform. The technical solution of the embodiment of the present invention realizes the automatic deployment of multiple environments for the cloud platform using Jenkins, reduces the complexity and risk of the multi-environment deployment of the cloud platform, and further improves the efficiency of the multi-environment deployment of the cloud platform.

[0024] It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0026] Figure 1 A schematic diagram of a process of deploying a cloud platform environment based on Jenkins provided in an embodiment of the present invention;

[0027] Figure 2A schematic diagram of the architecture of a custom plug-in applicable to a cloud platform environment deployment method based on Jenkins provided in an embodiment of the present invention;

[0028] Figure 3 An example diagram of an interface for a pipeline script configuration for a cloud platform environment deployment method based on Jenkins provided in an embodiment of the present invention;

[0029] Figure 4 A schematic diagram of a process of deploying a cloud platform environment based on Jenkins provided in an embodiment of the present invention;

[0030] Figure 5 A flowchart of an optional embodiment of a cloud platform environment deployment method based on Jenkins provided in an embodiment of the present invention;

[0031] Figure 6 A schematic diagram of the structure of a cloud platform environment deployment device based on Jenkins provided in an embodiment of the present invention;

[0032] Figure 7 A schematic diagram of the structure of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0033] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0034] It should be noted that the terms "including" and "having" and any variations thereof in the specification and claims of the present invention and the above-mentioned drawings are intended to cover non-exclusive inclusions. For example, a process, method, system, product or apparatus comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or apparatus.

[0035] It is understandable that before using the technical solutions disclosed in the embodiments of the present disclosure, the types, scope of use, usage scenarios, etc. of the personal information involved in the present disclosure should be informed to the user and the user's authorization should be obtained in an appropriate manner in accordance with relevant laws and regulations.

[0036] It is understandable that the data involved in this technical solution (including but not limited to the data itself, the acquisition or use of the data) shall comply with the requirements of relevant laws, regulations and relevant provisions.

[0037] Figure 1 A flow chart of a cloud platform environment deployment method based on Jenkins is provided for an embodiment of the present invention. This embodiment is applicable to the situation of deploying multiple environments on a cloud platform. The method can be executed by a cloud platform environment deployment device based on Jenkins. The cloud platform environment deployment device based on Jenkins can be implemented in the form of hardware and / or software. The cloud platform environment deployment device based on Jenkins can be configured in an electronic device such as a computer or a server.

[0038] like Figure 1 As shown, the method of this embodiment includes:

[0039] S110. Obtain at least two pieces of environment deployment information for environment deployment on a target cloud platform; wherein the target cloud platform includes multiple environment deployment interfaces.

[0040] Among them, the target cloud platform can be understood as a cloud platform that needs to be deployed in multiple environments. In an embodiment of the present invention, the target cloud platform can be set according to actual needs, which is not specifically limited here. For example, EDAS cloud platform. In an embodiment of the present invention, the environment deployment information includes at least the region identifier (RegionId), application identifier (AppId), domain name (Domain) and credential information of the environment to be deployed. Among them, the credential information may include an access key (accessKeyId) and a password (AccessKeySecret) corresponding to the AccessKeyID. In an embodiment of the present invention, the environment deployment interface in the target cloud platform may include a development environment deployment interface, a test environment deployment interface, a production environment deployment interface, and other environment deployment interfaces. In an embodiment of the present invention, the environment deployment interface of the target cloud platform can be used to deploy an environment in the target cloud platform. It can be understood that the development environment deployment interface in the target cloud platform can be used to deploy a development environment in the target cloud platform. The test environment deployment interface in the target cloud platform can be used to deploy a test environment in the target cloud platform. The production environment deployment interface of the target cloud platform can be used to deploy a generation environment in the target cloud platform.

[0041] In an embodiment of the present invention, obtaining environment deployment information for environment deployment on a target cloud platform may include: in response to an environment deployment information editing operation for environment deployment on a target platform, environment deployment information for environment deployment on the target cloud platform may be obtained. The environment deployment information editing operation may be used to edit at least two pieces of environment deployment information for environment deployment on the target cloud platform.

[0042] Based on this, in an embodiment of the present invention, after obtaining at least two environment deployment information for environment deployment on the target cloud platform, the method may also include: information modification and / or information deletion processing can be performed on the environment deployment information to obtain the environment deployment information required for environment deployment on the target cloud platform.

[0043] S120. Call a custom plug-in pre-installed in Jenkins to construct each of the environment deployment information into a corresponding environment deployment request; wherein the custom plug-in is used to deploy multiple environments in the target cloud platform.

[0044] In an embodiment of the present invention, the custom plug-in may be a custom plug-in based on Jenkins. The custom plug-in may be used to construct the environment deployment information into a corresponding environment deployment request to deploy an environment corresponding to the environment deployment information in the target cloud platform. In an embodiment of the present invention, the custom plug-in encapsulates a function capable of deploying multiple environments in the cloud platform. Figure 2 As shown, the custom plug-in can be a custom plug-in obtained through the Jenkins tool for deployment in multiple environments (such as development environment, test environment, production environment and other environments, etc.).

[0045] It should be noted that in the embodiments of the invention, a pre-developed custom Jenkins plug-in can be used to perform different environment deployment tasks for the target cloud platform, which not only simplifies the process of environment deployment of the cloud platform, but also reduces the possibility of operational errors, making the deployment process smoother, thereby improving the environment deployment experience. In addition, an integrated and automated environment deployment method can be implemented through a custom Jenkins plug-in, ensuring the consistency and reliability of environment deployment.

[0046] In an embodiment of the present invention, a specific method for obtaining the custom plug-in may include: generating a custom plug-in that can be installed in Jenkins in response to a file compilation operation on a code file of the custom plug-in. The file compilation operation may be understood as a compilation operation for the code file of the custom plug-in. In an embodiment of the present invention, the file format of the custom plug-in that can be installed in Jenkins may be an hpi format. Based on this, after obtaining the custom plug-in, the obtained custom plug-in may be installed in the Jenkins plug-in management so that the custom plug-in is installed on Jenkins, so as to complete the environment deployment task by calling the custom plug-in, that is, the task of environment deployment on the target cloud platform.

[0047] In the embodiment of the present invention, calling the custom plug-in pre-installed in Jenkins may specifically include: calling the custom plug-in pre-installed in Jenkins based on the environment deployment command in the target pipeline pre-created in Jenkins.

[0048] The target pipeline may be a pipeline created in advance in Jenkins, and is used to configure the environment deployment command to call the custom plug-in installed in Jenkins. In an embodiment of the present invention, the type of the target pipeline may be a pipeline type. In an embodiment of the present invention, when the target cloud platform is an EDAS cloud platform, the configuration environment deployment command may be an EDAS environment deployment command.

[0049] Specifically, first, you can create a target pipeline in Jenkins in advance. Then, you can set the environment deployment command in the pipeline script of the target pipeline (see Figure 3 ). Based on this, you can call the custom plug-in pre-installed in Jenkins based on the environment deployment command in the target pipeline pre-created in Jenkins.

[0050] S130. Based on each of the environment deployment requests, call a target deployment interface among the multiple environment deployment interfaces that matches each of the environment deployment requests, so as to deploy multiple environments in the target cloud platform.

[0051] Specifically, after each of the environment deployment requests is constructed, the environment deployment interface that matches each of the environment deployment requests can be determined from among multiple environment deployment interfaces in the target cloud platform based on each of the environment deployment requests, that is, the target deployment interface corresponding to each of the environment deployment requests can be determined. After multiple target deployment interfaces are determined, the environment corresponding to each of the target deployment interfaces can be deployed in the target cloud platform based on the target deployment interface, so that multiple environments are deployed in the target cloud platform.

[0052] The technical solution of the embodiment of the present invention obtains at least two environment deployment information for environment deployment on the target cloud platform; wherein the target cloud platform includes multiple environment deployment interfaces; calls a custom plug-in pre-installed in Jenkins to construct each of the environment deployment information into a corresponding environment deployment request; wherein the custom plug-in is used to deploy multiple environments in the target cloud platform; based on each of the environment deployment requests, calls a target deployment interface in the multiple environment deployment interfaces that matches each of the environment deployment requests to deploy multiple environments in the target cloud platform. The technical solution of the embodiment of the present invention realizes the use of Jenkins to automatically deploy multiple environments for the cloud platform, reduces the complexity and risk of multi-environment deployment of the cloud platform, and further improves the efficiency of multi-environment deployment of the cloud platform.

[0053] Figure 4 A flow chart of a cloud platform environment deployment method based on Jenkins provided in an embodiment of the present invention, based on the above-mentioned embodiment, optionally, the calling of a custom plug-in pre-installed in Jenkins to construct each of the environment deployment information into a corresponding environment deployment request includes: for each environment deployment information, calling a custom plug-in pre-installed in Jenkins to construct the environment deployment information into an environment deployment request corresponding to the environment deployment information. Among them, the technical features that are the same or similar to the above-mentioned embodiments are not repeated here.

[0054] like Figure 4 As shown, the method of this embodiment specifically includes:

[0055] S210. Obtain at least two pieces of environment deployment information for environment deployment on a target cloud platform; wherein the target cloud platform includes multiple environment deployment interfaces.

[0056] S220. For each environment deployment information, call a custom plug-in pre-installed in Jenkins to construct the environment deployment information into an environment deployment request corresponding to the environment deployment information; wherein the custom plug-in is used to deploy multiple environments in the target cloud platform.

[0057] Specifically, for each environment deployment information, an environment deployment function pre-installed in a custom plug-in of Jenkins that matches the environment deployment information can be determined. The environment deployment function can then be used to construct the environment deployment information into an environment deployment request corresponding to the environment deployment information.

[0058] In an embodiment of the invention, the environment deployment information may include at least a region identifier, a domain name, and credential information of the environment to be deployed. The step of constructing the environment deployment information into an environment deployment request corresponding to the environment deployment information specifically includes: performing information splicing processing on the region identifier, domain name, and credential information of the environment to be deployed according to the HTTP communication protocol to obtain an environment deployment request corresponding to the environment deployment information.

[0059] Specifically, the regional identifier, domain name and credential information of the environment to be deployed can be spliced ​​according to the HTTP communication protocol to obtain the spliced ​​information. Then, an environment deployment request corresponding to the environment deployment information can be obtained based on the spliced ​​information. Optionally, the spliced ​​information can be used as the request body of the environment deployment request.

[0060] S230. Based on each of the environment deployment requests, call a target deployment interface among the multiple environment deployment interfaces that matches each of the environment deployment requests, so as to deploy multiple environments in the target cloud platform.

[0061] The technical solution of the embodiment of the present invention, by calling a custom plug-in pre-installed in Jenkins for each environment deployment information, constructs the environment deployment information into an environment deployment request corresponding to the environment deployment information, so as to achieve relatively fast and convenient acquisition of environment deployment requests for multiple environments to be deployed on the target cloud platform, thereby improving the multi-environment deployment efficiency of the target cloud platform.

[0062] Figure 5 A flow chart of a cloud platform environment deployment method based on Jenkins provided in an embodiment of the present invention, based on the above-mentioned embodiment, optionally, the target deployment interface that matches each environment deployment request in the multiple environment deployment interfaces is called based on each environment deployment request, including: for each environment deployment request, the environment deployment request is authenticated, and when the environment deployment request passes the authentication, the target deployment interface that matches the environment deployment request in the multiple environment deployment interfaces is called. Among them, the technical features that are the same or similar to the above-mentioned embodiments are not repeated here.

[0063] like Figure 5 As shown, the method of this embodiment specifically includes:

[0064] S310. Obtain at least two pieces of environment deployment information for environment deployment on a target cloud platform; wherein the target cloud platform includes multiple environment deployment interfaces.

[0065] S320, calling a custom plug-in pre-installed in Jenkins, and constructing each of the environment deployment information into a corresponding environment deployment request; wherein the custom plug-in is used to deploy multiple environments in the target cloud platform.

[0066] S330. For each environment deployment request, authenticate the environment deployment request. If the environment deployment request passes the authentication, call a target deployment interface among the multiple environment deployment interfaces that matches the environment deployment request to deploy multiple environments in the target cloud platform.

[0067] Specifically, for each environment deployment request, the environment deployment request can be authenticated. When the environment deployment request passes the authentication, the environment deployment interface that matches the environment deployment request among the multiple environment deployment interfaces can be determined, that is, the target environment deployment interface corresponding to the environment deployment request can be determined. Then, the target environment deployment interface can be called to deploy the environment corresponding to the target deployment interface in the target cloud platform. This process automatically deploys multiple environments in the target cloud platform, so that the multiple environments deployed in the target cloud platform can be upgraded more conveniently and quickly in the future, and the operation is simple and convenient.

[0068] The technical solution of the embodiment of the present invention is to authenticate each environment deployment request, and if the environment deployment request passes the authentication, call the target deployment interface among the multiple environment deployment interfaces that matches the environment deployment request, so as to realize automatic deployment of multiple environments in the target cloud platform.

[0069] Figure 6 A schematic diagram of a cloud platform environment deployment device based on Jenkins provided in an embodiment of the present invention. Figure 6 As shown, the device includes: an information acquisition module 410, a request construction module 420 and an environment deployment module 430.

[0070] Among them, the information acquisition module 410 is used to obtain at least two environment deployment information for environment deployment on the target cloud platform; wherein the target cloud platform includes multiple environment deployment interfaces; the request construction module 420 is used to call the custom plug-in pre-installed in Jenkins to construct each of the environment deployment information into a corresponding environment deployment request; wherein the custom plug-in is used to deploy multiple environments in the target cloud platform; the environment deployment module 430 is used to call the target deployment interface in the multiple environment deployment interfaces that matches each of the environment deployment requests based on each of the environment deployment requests, so as to deploy multiple environments in the target cloud platform.

[0071] The technical solution of the embodiment of the present invention obtains at least two environment deployment information for environment deployment on the target cloud platform through the information acquisition module; wherein the target cloud platform includes multiple environment deployment interfaces; calls the custom plug-in pre-installed in Jenkins through the request construction module, and constructs each of the environment deployment information into a corresponding environment deployment request; wherein the custom plug-in is used to deploy multiple environments in the target cloud platform; and calls the target deployment interface that matches each of the environment deployment requests in the multiple environment deployment interfaces based on each of the environment deployment requests through the environment deployment module to deploy multiple environments in the target cloud platform. The technical solution of the embodiment of the present invention realizes the automatic deployment of multiple environments for the cloud platform using Jenkins, reduces the complexity and risk of the multi-environment deployment of the cloud platform, and further improves the efficiency of the multi-environment deployment of the cloud platform.

[0072] Optionally, the request construction module 420 is specifically configured to call a custom plug-in pre-installed in Jenkins for each environment deployment information, and construct the environment deployment information into an environment deployment request corresponding to the environment deployment information.

[0073] Optionally, the environment deployment information includes at least the regional identifier, domain name and credential information of the environment to be deployed; accordingly, the request construction module 420 is used to splice the regional identifier, domain name and credential information of the environment to be deployed in accordance with the HTTP communication protocol to obtain an environment deployment request corresponding to the environment deployment information.

[0074] Optionally, the request building module 420 is used to call a custom plug-in pre-installed in Jenkins based on the environment deployment command in the target pipeline pre-created in Jenkins.

[0075] Optionally, the environment deployment module 430 is used to authenticate each environment deployment request, and if the environment deployment request passes the authentication, call a target deployment interface among the multiple environment deployment interfaces that matches the environment deployment request.

[0076] Optionally, the device further comprises a custom plug-in generation module, which is used to generate a custom plug-in installable in Jenkins in response to a file compilation operation on a code file of the custom plug-in.

[0077] Optionally, the custom plug-in is used to deploy at least two environments among a development environment, a test environment, and a production environment in the target platform.

[0078] The Jenkins-based cloud platform environment deployment device provided in the embodiment of the present invention can execute the Jenkins-based cloud platform environment deployment method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0079] It is worth noting that the various units and modules included in the above-mentioned Jenkins-based cloud platform environment deployment device are only divided according to functional logic, but are not limited to the above-mentioned division, as long as the corresponding functions can be achieved; in addition, the specific names of the functional units are only for the convenience of distinguishing each other, and are not used to limit the protection scope of the embodiments of the present invention.

[0080] Figure 7 A schematic diagram of the structure of an electronic device 10 that can be used to implement an embodiment of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or required herein.

[0081] like Figure 7 As shown, the electronic device 10 includes at least one processor 11, and a memory connected to the at least one processor 11, such as a read-only memory (ROM) 12, a random access memory (RAM) 13, etc., wherein the memory stores a computer program that can be executed by at least one processor, and the processor 11 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 12 or the computer program loaded from the storage unit 18 to the random access memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the electronic device 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other through a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0082] A number of components in the electronic device 10 are connected to the I / O interface 15, including: an input unit 16, such as a keyboard, a mouse, etc.; an output unit 17, such as various types of displays, speakers, etc.; a storage unit 18, such as a disk, an optical disk, etc.; and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0083] The processor 11 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 11 executes the various methods and processes described above, such as a cloud platform environment deployment method based on Jenkins.

[0084] In some embodiments, the cloud platform environment deployment method based on Jenkins can be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 18. In some embodiments, part or all of the computer program can be loaded and / or installed on the electronic device 10 via the ROM 12 and / or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the cloud platform environment deployment method based on Jenkins described above can be performed. Alternatively, in other embodiments, the processor 11 can be configured to execute the cloud platform environment deployment method based on Jenkins in any other appropriate manner (for example, by means of firmware).

[0085] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0086] Computer programs for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that when the computer program is executed by the processor, the functions / operations specified in the flow chart and / or block diagram are implemented. The computer program may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0087] In the context of the present invention, a computer-readable storage medium may be a tangible medium that may contain or store a computer program for use by or in combination with an instruction execution system, device or equipment. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0088] To provide interaction with a user, the systems and techniques described herein may be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or trackball) through which the user can provide input to the electronic device. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form (including acoustic input, voice input, or tactile input).

[0089] The systems and techniques described herein may be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.

[0090] A computing system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The client and server relationship is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services.

[0091] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps described in the present invention can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solution of the present invention can be achieved, and this document does not limit this.

[0092] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A cloud platform environment deployment method based on Jenkins, characterized in that: The method comprises: Obtain at least two pieces of environment deployment information for environment deployment on a target cloud platform; wherein the target cloud platform includes a plurality of environment deployment interfaces; Calling a custom plug-in pre-installed in Jenkins to construct each of the environment deployment information into a corresponding environment deployment request; wherein the custom plug-in is used to deploy multiple environments in the target cloud platform; Based on each of the environment deployment requests, a target deployment interface among the multiple environment deployment interfaces that matches each of the environment deployment requests is called to deploy multiple environments in the target cloud platform.

2. The method according to claim 1, characterized in that: The calling of the custom plug-in pre-installed in Jenkins to construct each of the environment deployment information into a corresponding environment deployment request includes: For each piece of environment deployment information, a custom plug-in pre-installed in Jenkins is called to construct the environment deployment information into an environment deployment request corresponding to the environment deployment information.

3. The method according to claim 2, characterized in that The environment deployment information at least includes a region identifier, a domain name, and credential information of the environment to be deployed; and constructing the environment deployment information into an environment deployment request corresponding to the environment deployment information includes: According to the HTTP communication protocol, the region identifier, domain name and credential information of the to-be-deployed environment are concatenated to obtain an environment deployment request corresponding to the environment deployment information.

4. The method according to claim 1, characterized in that: The call is pre-installed in Jenkins custom plug-in, including: Based on the environment deployment command in the target pipeline pre-created in Jenkins, call the custom plug-in pre-installed in Jenkins.

5. The method according to claim 1, characterized in that The calling, based on each of the environment deployment requests, of a target deployment interface among the multiple environment deployment interfaces that matches each of the environment deployment requests comprises: For each environment deployment request, the environment deployment request is authenticated, and if the environment deployment request passes the authentication, a target deployment interface among the multiple environment deployment interfaces that matches the environment deployment request is called.

6. The method according to claim 1, characterized in that The method further comprises: In response to a file compiling operation on the code file of the custom plug-in, a custom plug-in that can be installed in Jenkins is generated.

7. The method according to claim 1, characterized in that The custom plug-in is used to deploy at least two environments among a development environment, a test environment, and a production environment in the target platform.

8. A cloud platform environment deployment device based on Jenkins, characterized in that: The device comprises: An information acquisition module, used to acquire at least two pieces of environment deployment information for environment deployment on a target cloud platform; wherein the target cloud platform includes a plurality of environment deployment interfaces; A request building module, used to call a custom plug-in pre-installed in Jenkins to build each environment deployment information into a corresponding environment deployment request; wherein the custom plug-in is used to deploy multiple environments in the target cloud platform; The environment deployment module is used to call the target deployment interface matching each of the environment deployment requests among the multiple environment deployment interfaces based on each of the environment deployment requests, so as to deploy multiple environments in the target cloud platform.

9. An electronic device, characterized in that: The electronic device comprises: at least one processor; and a memory communicatively connected to the at least one processor; wherein, The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the Jenkins-based cloud platform environment deployment method described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the Jenkins-based cloud platform environment deployment method described in any one of claims 1 to 7 when executed.

Images