CN114237634A

CN114237634A - Application release risk identification method, device, equipment, medium and program product

Info

Publication number: CN114237634A
Application number: CN202111607169.XA
Authority: CN
Inventors: 李杰超; 肖瑶; 高鹏
Original assignee: CCB Finetech Co Ltd
Current assignee: CCB Finetech Co Ltd
Priority date: 2021-12-24
Filing date: 2021-12-24
Publication date: 2022-03-25

Abstract

The invention provides an application release risk identification method, and relates to the field of application release, in particular to the field of application version release of financial enterprises. Creating a release scene of an application; generating a corresponding risk pre-inspection scheduling task according to the release scene of the application; and analyzing the risk pre-inspection scheduling task into different types of automatic operation tasks, and sequentially issuing the operation tasks to the target virtual machine according to the execution logic set by scheduling. Risks are detected in advance before release, blind spots that risk check before release is easy to ignore in traditional application release are covered, possible release problems are exposed in advance, smooth execution of application release in a production period is guaranteed, and therefore success rate of enterprise-level application release and normal operation of enterprise-level services are improved. The invention also provides an application release risk identification device, electronic equipment, a storage medium and a program product.

Description

Application release risk identification method, device, equipment, medium and program product

Technical Field

The invention relates to the technical field of application release, in particular to the field of application version release of financial enterprises, and more particularly relates to an application release risk identification method, device, equipment, medium and program product.

Background

Application publishing refers to the process of deploying an application system software package to a designated computer and providing the application system software package for use by a user. Typically consisting of a number of operations (e.g., get version package, backup, deploy package, service check, etc.) in a specified orchestration order.

With the rapid development of enterprise business and the frequent change of IT technology, the enterprise-level application deployment architecture is complicated, the system scale is enlarged, and the trend of application production release and daily change high frequency becomes more obvious. However, the application release in the prior art has some problems: risk check before release is ignored, so that release failure is caused, and normal operation of the service is influenced; the risk is released by manual inspection, so that time and labor are wasted, the implementation efficiency is low, and a larger operation risk exists; the risk is detected by using the script, the adaptability is poor, and the repeated utilization rate is low.

Disclosure of Invention

The invention mainly aims to provide an application release risk identification method, device, equipment, storage medium and program product, aiming at improving the technical problems of low risk check efficiency, poor adaptability and low repeated utilization rate before application release in the prior art.

In order to achieve the purpose, the invention provides an application release risk identification method. The application release risk identification method comprises the following steps:

creating a release scene of an application;

generating a corresponding risk pre-inspection scheduling task according to the release scene of the application;

and analyzing the risk pre-inspection scheduling task into different types of automatic operation tasks, and sequentially issuing the operation tasks to the target virtual machine according to the execution logic set by scheduling.

Optionally, before the step of creating a publishing scenario of the application, the method further includes:

creating an automation operation corresponding to each risk pre-detection script or program according to the risk pre-detection script or program, and associating the risk pre-detection script or program with the automation operation corresponding to the risk pre-detection script or program;

the automation operations are concatenated according to a specific execution order.

Optionally, the step of generating a corresponding risk pre-inspection task according to the release scenario of the application includes:

acquiring risk pre-inspection arrangement matched with the current application release scene;

when only one matched risk pre-inspection task exists, transmitting execution parameters to the matched risk pre-inspection task, and instantiating the risk pre-inspection task;

and when a plurality of matched risk pre-inspection tasks exist, selecting one of the matched risk pre-inspection tasks as a matched risk pre-inspection incoming execution parameter, and instantiating the risk pre-inspection tasks.

Optionally, after the step of analyzing the risk pre-scheduling task into different types of automated operation tasks and issuing the operation tasks to the target virtual machine in sequence according to the execution logic set by scheduling, the method further includes:

after receiving the execution result of the operation task, recording result information;

if the execution of the operation task fails, pushing an execution result to a scene release module, and finishing issuing the operation task;

and if the operation tasks are successfully executed, continuing to send the next operation task according to the execution sequence of the operation tasks until all the tasks are executed.

updating result information of risk pre-inspection;

if the pre-check is passed, performing application release operation;

and if the pre-check is not passed, the application is checked.

In addition, in order to achieve the above purpose, the invention further provides an application release risk identification device, which comprises a scene release module and an automation module, wherein the scene release module is electrically connected with the automation module;

the scene publishing module is used for creating a publishing scene and generating a publishing task, creating a pre-checking task according to the publishing pre-checking, calling the automation module to execute the pre-checking task and calling the automation module to execute the publishing task;

the automation module is used for creating and managing automation operation and arrangement, receiving the arrangement task of the scene release module, analyzing the arrangement task into an operation task, sending the operation task to the virtual machine, receiving the execution result and summarizing the execution result to the scene release module.

Optionally, the scene publishing module includes an orchestration task management module, and the orchestration task management module is responsible for creating, maintaining, and issuing an orchestration task, acquiring automatic orchestration through the automation module, transmitting a parameter to the orchestration to generate an orchestration task, transmitting the orchestration task to the automation module, and receiving an execution result.

Optionally, the automation module comprises:

the operation management module is responsible for creating and maintaining automatic operation;

the arrangement management module is responsible for creating and maintaining automatic arrangement and serially connecting the single automatic operation according to a specific execution sequence;

and the execution module is responsible for receiving the scheduling tasks, analyzing the scheduling tasks into different types of automatic operation tasks, then sequentially issuing the execution tasks to the target virtual machine according to the execution logic set by scheduling, collecting the execution results of the virtual machines, and feeding back the execution results to the scene release module.

In addition, to achieve the above object, the present invention also provides an electronic device including:

one or more processors;

a storage device for storing one or more programs,

wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform any of the methods described above.

Furthermore, to achieve the above object, the present invention also provides a computer-readable storage medium having stored thereon executable instructions, which when executed by a processor, implement the steps of the application issuance risk identification method as described above.

Furthermore, to achieve the above object, the present invention also proposes a computer program product comprising a computer program which, when being executed by a processor, realizes the steps of the application issuance risk identification method as described above.

According to the technical scheme provided by the invention, the risk is detected in advance before actual execution of the release, a blind spot that risk check before the release is easily ignored in the traditional application release is covered, the possible release problem is exposed in advance, and the smooth execution of the application release in a production period is ensured, so that the success rate of enterprise-level application release and the normal operation of enterprise-level services are improved. The risk pre-inspection is realized through automatic arrangement, the defects of low execution efficiency and high operation risk of manual inspection and script inspection are overcome, and the method can adapt to complicated and changeable issuing scenes and implementation environments.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the structures shown in the drawings without creative efforts.

FIG. 1 is a schematic diagram of an application scenario of an embodiment of the present invention;

fig. 2 is a schematic flowchart of an embodiment of an application release risk identification method provided in the present invention;

fig. 3 is a schematic flowchart of an embodiment of an application release risk identification method provided in the present invention;

FIG. 4 is a schematic structural diagram of an application issuance risk identification apparatus;

fig. 5 is a schematic structural diagram of the electronic device in fig. 4.

The reference numbers illustrate:

reference numerals	Name (R)	Reference numerals	Name (R)
				100	Application scenarios	1806	Input part
101	Server	1807	Output section
				102	Network	1808	Storage section
103	Virtual machine	1809	Communication part
				1800	Electronic device	1810	Driver
1801	Processor with a memory having a plurality of memory cells	1811	Removable media
				1802	Read-only memory	104	Scene publishing module
1803	Random access memory	105	Automation module
				1804	Bus line	106	Operation management module
1805	I/O interface	107	Orchestration management module
						108	Execution module

The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to specific embodiments and the accompanying drawings. The technical solutions in the present invention are clearly and completely described, and it is obvious that the described embodiments are some, not all embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. It is to be understood that such description is merely illustrative and not intended to limit the scope of the present invention. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the invention. It may be evident, however, that one or more embodiments may be practiced without these specific details. Moreover, in the following description, descriptions of well-known structures and techniques are omitted so as to not unnecessarily obscure the concepts of the present invention.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. The terms "comprises," "comprising," and the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.

All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It is noted that the terms used herein should be interpreted as having a meaning that is consistent with the context of this specification and should not be interpreted in an idealized or overly formal sense.

Where a convention analogous to "at least one of A, B and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B and C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.). Where a convention analogous to "A, B or at least one of C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B or C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).

Some block diagrams and/or flow diagrams are shown in the figures. It will be understood that some blocks of the block diagrams and/or flowchart illustrations, or combinations thereof, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the instructions, which execute via the processor, create means for implementing the functions/acts specified in the block diagrams and/or flowchart block or blocks. The techniques of the present invention may be implemented in hardware and/or in software (including firmware, microcode, etc.). Furthermore, the techniques of this disclosure may take the form of a computer program product on a computer-readable storage medium having instructions stored thereon for use by or in connection with an instruction execution system.

It should be noted that, if directional indication is involved in the embodiment of the present invention, the directional indication is only used for explaining the relative positional relationship, the motion situation, and the like between the components in a certain posture, and if the certain posture is changed, the directional indication is changed accordingly.

In addition, if there is a description of "first", "second", etc. in an embodiment of the present invention, the description of "first", "second", etc. is for descriptive purposes only and is not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. In addition, the meaning of "and/or" appearing throughout includes three juxtapositions, exemplified by "A and/or B" including either A or B or both A and B. Also, the technical solutions in the embodiments may be combined with each other, but must be based on the realization of those skilled in the art, and when the technical solutions are contradictory or cannot be realized, the combination of the technical solutions should be considered to be absent and not be within the protection scope of the present invention.

In the description of the present invention, it should be noted that the terms "upper", "lower", "top", "bottom", "inner", "outer", and the like indicate orientations or positional relationships based on those shown in the drawings, and are only for convenience of description and simplification of description, but do not indicate or imply that the referred device or element must have a specific orientation, be constructed in a specific orientation, and be operated, and thus, should not be construed as limiting the present invention.

In the description of the present invention, it should be noted that, unless otherwise explicitly specified or limited, the terms "mounted," "connected," and "connected" are to be construed broadly, e.g., as meaning either a fixed connection, a removable connection, or an integral connection; can be mechanically or electrically connected; they may be connected directly or indirectly through intervening media, or they may be interconnected between two elements. The specific meanings of the above terms in the present invention can be understood in specific cases to those skilled in the art.

In addition, in the description of the present invention, "a plurality", and "a plurality" mean two or more unless otherwise specified.

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

Fig. 1 schematically shows an application scenario diagram of an application publication risk identification method, apparatus, electronic device, storage medium, and program product according to an embodiment of the present invention.

It should be noted that fig. 1 is only an example of an application scenario in which the embodiment of the present invention may be applied to help those skilled in the art understand the technical content of the present invention, and does not mean that the embodiment of the present invention may not be applied to other devices, systems, environments or scenarios.

As shown in fig. 1, the application scenario 100 according to this embodiment may include a server 101, a network 102, and a virtual machine 103. Network 102 is the medium used to provide communication links between servers 101 and virtual machines 103. Network 102 may include various connection types, such as wired and/or wireless communication links, and so forth.

Based on the hardware structure, the embodiment of the application release risk identification method is provided.

Referring to fig. 2, fig. 2 is a schematic flowchart of an embodiment of an application release risk identification method according to the present invention, and in an embodiment, the application release risk identification method includes the following steps:

s10: a publishing scenario of the application is created.

S20: and generating a corresponding risk pre-inspection scheduling task according to the release scene of the application.

S30: and analyzing the risk pre-inspection scheduling task into different types of automatic operation tasks, and sequentially issuing the operation tasks to the target virtual machine according to the execution logic set by scheduling.

In this embodiment, the release schedules used for different scenes are different, and then the previewed contents are also different, so that when the application is released, there may be different scenes, such as some release-only packages, some update database tables, and some patch, so that the user can create the release scene according to the needs of the user. After the release scene is created, risk pre-inspection operations can be performed according to specific scene generation requirements, and the risk pre-inspection operations are arranged according to a certain sequence to form a risk pre-inspection arrangement task corresponding to the release scene generation. And when the task is executed, analyzing the risk pre-inspection scheduling task into different types of automatic operation tasks, and sequentially issuing the operation tasks to the target virtual machine according to the execution logic set by scheduling for risk inspection.

The risk possibly existing in the release is arranged into the check items, reusable automation operations are formed for each check item, and then the risk pre-check arrangement is generated by setting the dependency relationship between the automation operations. Different application releases can flexibly generate differentiated risk pre-inspection arrangement according to different inspection items. And before release implementation, an automatic module is called to execute a risk pre-checking scheduling task, so that risk pre-checking under different release scenes is realized.

The risk that may appear in enterprise-level application release needs to be combed first, and a risk preview script or program corresponding to the risk needs to be written. This is a preliminary preparation. Therefore, the following steps are also included before step S10:

step S1: and creating an automation operation corresponding to each risk preview script or program according to the risk preview script or program, and associating the risk preview script or program with the automation operation corresponding to the risk preview script or program.

Step S2: the automation operations are concatenated according to a specific execution order.

Risks common in enterprise-level application publishing include, but are not limited to: 1. whether the network connection between the application issuing system and the virtual machine is normal or not is judged; 2. whether an agent on the virtual machine operates normally; 3. whether an executing user in the application release arrangement exists in the virtual machine or not or whether an executing authority exists or not; 4. whether the configuration file of the version package meets the format requirement or not; 5. and whether the execution script in the version packet has high-risk command operation or not. Other differentiated risks also exist according to the difference of the specification system or the release environment of different enterprises. Each risk requires writing a corresponding risk preview script or program. Due to the variety of the operating system, the agent and the file format of the virtual machine, a plurality of scripts or programs are prepared for some risks.

The operations management module 106 in the automation module 105 then creates the automation operations. Each risk preview script or program requires the creation of a corresponding automation operation. After the automation operation is created, the automation operation is associated with a risk pre-inspection script or program. Therefore, when other modules call the automation operation, the risk pre-check script or program can be actually called through the input parameters and the automation operation, and the automation operation can also return the execution result of the script or program to other modules.

Referring to FIG. 3, when an automation operation is created, it is programmed. Step S20 includes:

step S201: and acquiring risk pre-inspection arrangement matched with the current application release scene.

Step S202: and when only one matched risk pre-check-up task exists, transmitting execution parameters to the matched risk pre-check-up task, and instantiating the risk pre-check-up task.

Step S203: and when a plurality of matched risk pre-inspection tasks exist, selecting one of the matched risk pre-inspection tasks as a matched risk pre-inspection incoming execution parameter, and instantiating the risk pre-inspection tasks.

In this embodiment, after the automatic operation of risk pre-inspection is completed, the corresponding automatic arrangement needs to be created by the arrangement management module 107. Automated orchestration may be cascaded with multiple independent operations, enabling the automated operations to be performed in a set logical order. The orchestration may pass the results of previously performed operation executions as input parameters to subsequent automation operations. Another benefit of creating automated choreographies is that automation operations can be reused. Different choreographies can be created depending on different application scenarios or distribution environments. Different choreographies identify applicable scenes or environments with tags.

The automated orchestration corresponds to a template that can be instantiated by passing in execution parameters. There may be multiple instances per orchestration, each instance being an orchestration task. In the release scene module, a user firstly creates a release scene and a release task, and needs to perform release risk pre-check before actually executing the release task. The first step of risk pre-inspection is to generate an arranging task of risk pre-inspection, and the specific process is as follows:

in this embodiment, the orchestration task management module in the scene publishing module 104 calls the orchestration management module 107 to obtain the risk pre-orchestration matching the current application scene or environment, and instantiates the risk pre-orchestration task by introducing the execution parameters into the risk pre-orchestration. If there are multiple matching risk pre-checkups, the system provides a manual selection function. The system also provides secondary selection of operations in the arrangement, namely, a user can select to execute only part of operations in the arrangement, thereby meeting the requirement of flexibly adapting to various scenes.

Then, after receiving the risk pre-inspection scheduling task issued by the scene publishing module 104, the execution module 108 of the automation module 105 parses the risk pre-inspection operation task according to the operation and execution parameters selected in the scheduling task. The order of execution of the operational tasks is determined by the orchestration logic of the automated orchestration. The execution module 108 issues the operation task to the execution agent (the plug-in previously installed on the virtual machine 103 by the automation module 105) on the virtual machine 103, and the operation task is actually executed by the agent. Some operational tasks, such as testing network connectivity with the virtual machine 103 or testing the state of an agent, are prerequisites for performing other operational tasks, which are performed directly by the execution module 108. And other operation tasks can be normally issued only after the execution is correct.

After the execution of the operation task is completed, the result of the execution of the operation task may be queried, which further includes after step S30:

step S40: and after receiving the execution result of the operation task, recording result information.

Step S50: and if the execution of the operation task fails, pushing an execution result to the scene release module, and finishing issuing the operation task.

Step S60: and if the operation tasks are successfully executed, continuing to send the next operation task according to the execution sequence of the operation tasks until all the tasks are executed.

In this embodiment, after receiving the execution result of the operation task, the execution module 108 records the result information. And if the execution of the operation task fails, pushing an execution result to the release scene module, and ending the release of the risk pre-detection operation task. And if the operation tasks are successfully executed, continuing to send the next operation task according to the execution sequence of the operation tasks until all the tasks are completely executed.

In the embodiment, the result of the pre-detection can be synchronously updated, so that the pre-detection result is convenient to check. The following steps are also included after step S30:

step S70: and updating the result information of the risk pre-inspection.

Step S80: and if the preview is passed, performing application issuing operation.

Step S90: and if the pre-check is not passed, the application is checked.

In this embodiment, the execution module 108 pushes the risk preview result to the scenario publishing module 104. And the scene publishing module 104 updates the risk pre-inspection result information and performs subsequent processing according to the result information. Normally, if the risk pre-inspection fails, the existing risk must be solved first and the risk pre-inspection is performed again to execute the publishing task.

Referring to fig. 4, the application release risk identification device includes a scenario release module 104 and an automation module 105, and the scenario release module 104 is electrically connected to the automation module 105. The scene publishing module 104 is configured to create a publishing scene and generate a publishing task, create a pre-check scheduling task according to the publishing pre-check scheduling, call the automation module 105 to execute the pre-check scheduling task, and call the automation module 105 to execute the publishing task. The automation module 105 is used for creating and managing automation operation and scheduling, receiving the scheduling task of the scene publishing module 104, analyzing the scheduling task into an operation task, sending the operation task to the virtual machine 103, receiving the execution result and summarizing the execution result to the scene publishing module 104.

The automation module 105 includes an operations management module 106, and an orchestration management module 107. The operations management module 106 is responsible for creating and maintaining automation operations; the orchestration management module 107 is responsible for creating and maintaining automated orchestrations, concatenating the individual automation operations in a specific execution order; the execution module 108 is responsible for receiving the scheduling tasks, analyzing the scheduling tasks into different types of automation operation tasks, then sequentially issuing the execution tasks to the target virtual machine according to the execution logic set by scheduling, collecting the execution results of the virtual machines 103, and feeding back the execution results to the scene publishing module 104.

Fig. 5 is a schematic structural diagram of an electronic device 1800 in a hardware operating environment according to an embodiment of the present invention. As shown in fig. 5, the electronic device 1800 may include: a processor 1801, which may perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)1802 or a program loaded from a storage portion 1808 into a Random Access Memory (RAM) 1803. The processor 1801 may include, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or associated chipset, and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), among others. The processor 1801 may also include onboard memory for caching purposes. The processor 1801 may include a single processing unit or multiple processing units for performing the various actions of the method flows in accordance with embodiments of the present invention.

In the RAM1803, the electronic device 1800 includes various programs and data necessary for operation. A processor 1801 and a memory unit 3, the memory unit 3 including a ROM 1802 and a RAM1803 being connected to each other by a bus 1804. The processor 1801 performs various operations of method flows according to embodiments of the present invention by executing programs in the ROM 1802 and/or RAM 1803. Note that the programs may also be stored in one or more memories other than ROM 1802 and RAM 1803. The processor 1801 may also perform various operations of method flows according to embodiments of the present invention by executing programs stored in the one or more memories.

According to an embodiment of the invention, the electronic device 1800 may also include input/output (I/O) interface 1805, where the input/output (I/O) interface 1805 is also connected to the bus 1804. The electronic device 1800 may also include one or more of the following components connected to the I/O interface 1805: an input portion 1806 including a keyboard, a mouse, and the like; an output portion 1807 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 1808 including a hard disk and the like; and a communication section 1809 including a network interface card such as a LAN card, a modem, or the like. The communication section 1809 performs communication processing via a network such as the internet. A driver 1810 is also connected to the I/O interface 1805 as needed. A removable medium 1811 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 1810 as necessary, so that a computer program read out therefrom is mounted in the storage portion 1808 as necessary. The communication section 1809 is used for implementing connection communication among these components, and includes various connection types such as wired, wireless communication links, or fiber optic cables. The input/output (I/O) interface 1805 may also include a standard wired interface, which may be a USB interface, a wireless interface.

The electronic device 1800 shown in fig. 5 further comprises: the network interface is mainly used for connecting the background server 103 and performing data communication with the background server 103; the user interface is mainly used for connecting user equipment; the electronic device 1800 calls the control program of the automatic operation and maintenance platform adaptation method stored in the memory through the processor 1801, and executes the control steps of the automatic operation and maintenance platform adaptation method provided by the embodiment of the present invention.

Those skilled in the art will appreciate that the configuration shown in fig. 5 is not intended to be limiting of the electronic device 1800 and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.

The present invention also provides a computer-readable storage medium, which may be contained in the apparatus/system described in the above embodiments; or may exist separately and not be incorporated into the device/system. The computer-readable storage medium carries one or more programs which, when executed, implement the method according to an embodiment of the present invention.

According to an embodiment of the present invention, the computer readable storage medium may be a non-volatile computer readable storage medium. Examples may include, but are not limited to: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present invention, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

For example, according to embodiments of the present invention, a computer-readable storage medium may include the ROM and/or RAM described above and/or one or more memories other than ROM and RAM.

According to an embodiment of the invention, the method flow according to an embodiment of the invention may be implemented as a computer software program. For example, embodiments of the invention include a computer program product comprising a computer program embodied on a computer-readable storage medium, the computer program comprising program code for performing the method illustrated by the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication section, and/or installed from a removable medium. The computer program, when executed by a processor, performs the above-described functions defined in the system of the embodiment of the present invention. The above described systems, devices, apparatuses, modules, units, etc. may be implemented by computer program modules according to embodiments of the present invention.

When the computer program product runs in a computer system, the program code is used for causing the computer system to realize the item recommendation method provided by the embodiment of the invention. The computer program performs the above-described functions defined in the system/apparatus of the embodiment of the present invention when executed by the processor 1801. The above described systems, devices, modules, units, etc. may be implemented by computer program modules according to embodiments of the invention.

In one embodiment, the computer program may be hosted on a tangible storage medium such as an optical storage device, a magnetic storage device, or the like. In another embodiment, the computer program may also be transmitted in the form of a signal on a network medium, distributed, downloaded and installed via the communication section 1809, and/or installed from a removable media 1811. The computer program containing program code may be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.

In such embodiments, the computer program may be downloaded and installed from a network via the communication portion 1809, and/or installed from the removable media 1811. The computer program, when executed by the processor 1801, performs the above-described functions defined in the system of an embodiment of the present invention. The above described systems, devices, apparatuses, modules, units, etc. may be implemented by computer program modules according to embodiments of the present invention.

According to embodiments of the present invention, program code for executing a computer program provided by embodiments of the present invention may be written in any combination of one or more programming languages, and in particular, the computer program may be implemented using a high level procedural and/or object oriented programming language, and/or an assembly/machine language. The programming language includes, but is not limited to, programming languages such as Java, C + +, python, the "C" language, or the like. The program code may execute entirely on the user computing device, partly on the user device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention or portions thereof that contribute to the prior art may be embodied in the form of a software product, where the computer software product is stored in a storage medium (e.g., a Read Only Memory (ROM)/Random Access Memory (RAM), a magnetic disk, an optical disk), and includes several instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.

Finally, it should be noted that: the above examples are only intended to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention. The above-mentioned embodiments are intended to illustrate the objects, technical solutions and advantages of the present invention in further detail, and it should be understood that the above-mentioned embodiments are only exemplary embodiments of the present invention, and are not intended to limit the present invention, and any modifications, equivalents, improvements and the like made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. An application release risk identification method is characterized by comprising the following steps:

creating a release scene of an application;

2. The application publication risk identification method of claim 1, further comprising, before the step of creating the publication scenario of the application:

3. The application release risk identification method of claim 2, wherein the step of generating the corresponding risk pre-inspection task according to the release scenario of the application comprises:

4. The method for identifying risk of application publication according to claim 1, wherein after the steps of parsing the risk pre-inspection task into different types of automation operation tasks and issuing the operation tasks to the target virtual machine in sequence according to the execution logic set by the scheduling, the method further comprises:

5. The method for identifying risk of application publication according to claim 1, wherein after the steps of parsing the risk pre-inspection task into different types of automation operation tasks and issuing the operation tasks to the target virtual machine in sequence according to the execution logic set by the scheduling, the method further comprises:

updating result information of risk pre-inspection;

if the pre-check is passed, performing application release operation;

and if the pre-check is not passed, the application is checked.

6. The application release risk identification device is characterized by comprising a scene release module and an automation module, wherein the scene release module is electrically connected with the automation module;

7. The application distribution risk recognition device of claim 6, wherein the scene distribution module comprises an orchestration task management module, and the orchestration task management module is responsible for creating, maintaining, and issuing orchestration tasks, and obtains automated orchestration through the automation module, then transmits parameters to the orchestration to generate orchestration tasks, and sends the orchestration tasks to the automation module, and receives execution results.

8. The application publication risk identification apparatus of claim 6, wherein the automation module comprises:

9. An electronic device, comprising:

one or more processors;

a storage device for storing one or more programs,

wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the method of any of claims 1-5.

10. A computer-readable storage medium having stored thereon executable instructions that, when executed by a processor, cause the processor to perform the method of any one of claims 1 to 5.

11. A computer program product, comprising a computer program which, when executed by a processor, implements a method according to any one of claims 1 to 5.