Application release risk identification methods, devices, equipment, media, and program products

Abstract

The present invention provides a method for identifying application release risks, and the present invention relates to the field of application release, and in particular to the field of application version release of financial enterprises. Create an application release scenario; generate a corresponding risk pre-check orchestration task according to the application release scenario; parse the risk pre-check orchestration task into different types of automated operation tasks, and issue the operation tasks to the target virtual machine in sequence according to the execution logic set by the orchestration. Pre-detecting risks before release covers the blind spot of traditional application release that easily ignores pre-release risk checks, exposes possible release problems in advance, and ensures the smooth execution of application release during the production period, thereby improving the success rate of enterprise-level application release and the normal operation of enterprise-level business. The present invention also provides an application release risk identification device, an electronic device, a storage medium, and a program product.

Description

Technical Field

[0001] The present invention relates to the field of application release technology, in particular to the field of application version release of financial enterprises, and more specifically to an application release risk identification method, device, equipment, medium, and program product. Background Art

[0002] Application release refers to the process of deploying the application system software package to a specified computer and providing it to users. It usually consists of multiple operations (such as obtaining version packages, backup, deploying program packages, service checks, etc.) in a specified order.

[0003] With the rapid development of enterprise business and the frequent changes of IT technology, the deployment architecture of enterprise-level applications has become more complex, the scale of the system has expanded, and the trend of high frequency of application production release and daily changes has become more obvious. However, there are some problems with application release in existing technologies: ignoring risk checks before release leads to release failures and affects the normal operation of business; using manual inspections for release risks is not only time-consuming and labor-intensive, but also inefficient and has greater operational risks; using scripts to detect risks has poor adaptability and low reuse rates. Summary of the invention

[0004] The main purpose of the present invention is to provide an application release risk identification method, device, equipment, storage medium, and program product, aiming to improve the technical problems in the prior art of low efficiency, poor adaptability, and low reuse rate of risk inspection before application release.

[0005] To achieve the above-mentioned purpose, the present invention provides a method for identifying application release risks. The method for identifying application release risks comprises the following steps:

[0006] Create a release scenario for the application;

[0007] Generate corresponding risk pre-check orchestration tasks based on the application release scenario;

[0008] The risk pre-checking orchestration task is parsed into different types of automated operation tasks, and the operation tasks are sequentially issued to the target virtual machine according to the execution logic set by the orchestration.

[0009] Optionally, before the step of creating a release scenario for the application, the following steps are further included:

[0010] Creating an automated operation corresponding to each risk pre-check script or program, and associating the risk pre-check script or program with the automated operation corresponding to the risk pre-check script or program;

[0011] The automation operations are linked together in a specific execution order.

[0012] Optionally, the step of generating a corresponding risk pre-checking orchestration task according to the application release scenario includes:

[0013] Get the risk pre-check arrangement that matches the current application release scenario;

[0014] When there is only one matching risk pre-check arrangement, the execution parameters are passed to the matching risk pre-check arrangement to instantiate the risk pre-check arrangement task;

[0015] When there are multiple matching risk pre-check orchestrations, one of them is selected as the matching risk pre-check orchestration to pass in execution parameters, and the risk pre-check orchestration task is instantiated.

[0016] Optionally, after the step of parsing the risk pre-checking orchestration task into different types of automated operation tasks, and sending the operation tasks to the target virtual machine in sequence according to the execution logic set by the orchestration, the step further includes:

[0017] After receiving the execution result of the operation task, the result information is recorded;

[0018] If the operation task fails to execute, the execution result is pushed to the scenario publishing module, and the operation task is terminated;

[0019] If the operation task is executed successfully, the next operation task will be issued according to the execution order of the operation tasks until all tasks are executed.

[0020] Optionally, after the step of parsing the risk pre-checking orchestration task into different types of automated operation tasks, and sending the operation tasks to the target virtual machine in sequence according to the execution logic set by the orchestration, the step further includes:

[0021] Update the risk pre-check result information;

[0022] If the pre-check passes, the application is released;

[0023] If the precheck fails, troubleshoot the application.

[0024] In addition, to achieve the above-mentioned purpose, the present invention also proposes an application release risk identification device, comprising a scenario release module and an automation module, wherein the scenario release module is electrically connected to the automation module;

[0025] The scenario publishing module is used to create a publishing scenario and generate a publishing task, and to create a pre-check arrangement task according to the publishing pre-check arrangement, and to call the automation module to execute the pre-check arrangement task and to call the automation module to execute the publishing task;

[0026] The automation module is used to create and manage automated operations and orchestrations, receive the orchestration tasks of the scenario publishing module and parse them into operation tasks, issue the operation tasks to the virtual machine, receive the execution results and summarize them to the scenario publishing module.

[0027] Optionally, the scenario publishing module includes an orchestration task management module, which is responsible for creating, maintaining, and issuing orchestration tasks, and obtaining automated orchestration through the automation module, then passing parameters to the orchestration to generate orchestration tasks, and sending the orchestration tasks to the automation module, and receiving execution results.

[0028] Optionally, the automation module includes:

[0029] The operations management module is responsible for creating and maintaining automated operations;

[0030] The orchestration management module is responsible for creating and maintaining automation orchestrations, connecting the individual automation operations in series according to a specific execution order;

[0031] The execution module is responsible for receiving the orchestration tasks, parsing the orchestration tasks into different types of automated operation tasks, and then sending the execution tasks to the target virtual machines in sequence according to the execution logic set by the orchestration, and collecting the execution results of the virtual machines and feeding them back to the scenario publishing module.

[0032] In addition, to achieve the above object, the present invention further provides an electronic device, comprising:

[0033] one or more processors;

[0034] a storage device for storing one or more programs,

[0035] When the one or more programs are executed by the one or more processors, the one or more processors execute any of the methods described above.

[0036] In addition, to achieve the above-mentioned purpose, the present invention also proposes a computer-readable storage medium, on which executable instructions are stored, and when the instructions are executed by a processor, the steps of the application release risk identification method as described above are implemented.

[0037] In addition, to achieve the above-mentioned purpose, the present invention also proposes a computer program product, including a computer program, which implements the steps of the application release risk identification method as described above when executed by a processor.

[0038] In the technical solution provided by the present invention, risks are pre-detected before the actual execution of the release, covering the blind spot of the traditional application release that is easy to ignore the risk check before the release, exposing possible release problems in advance, and ensuring the smooth execution of the application release during the production period, thereby improving the success rate of enterprise-level application release and the normal operation of enterprise-level business. The present invention implements risk pre-checking through automated orchestration, which not only makes up for the shortcomings of low execution efficiency and high operational risk of manual inspection and script inspection, but also can adapt to complex and changeable release scenarios and implementation environments. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art 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 the structures shown in these drawings without paying creative work.

[0040] Figure 1 It is a schematic diagram of an application scenario of an embodiment of the present invention;

[0041] Figure 2 A schematic diagram of a flow chart of an embodiment of a method for identifying application release risks provided by the present invention;

[0042] Figure 3 A schematic diagram of a flow chart of an embodiment of a method for identifying application release risks provided by the present invention;

[0043] Figure 4 A schematic diagram of the structure of the risk identification device for application release;

[0044] Figure 5 for Figure 4 Schematic diagram of the structure of the electronic equipment.

[0045] Description of Figure Numbers:

[0046] Label name Label name 100 Application Scenario 1806 Input section 101 server 1807 Output section 102 network 1808 Storage 103 Virtual Machines 1809 communication part 1800 Electronic devices 1810 Drive 1801 processor 1811 Removable media 1802 Read-only memory 104 Scene publishing module 1803 Random Access Memory 105 Automation Module 1804 bus 106 Operation Management Module 1805 I / O Interface 107 Orchestration management module 108 Execution Module

[0047] The realization of the purpose, functional features and advantages of the present invention will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0048] In order to make the purpose, technical solution and advantages of the present invention more clearly understood, the present invention is further described in detail below in combination with specific embodiments and with reference to the accompanying drawings. The technical solution in the present invention is clearly and completely described. Obviously, the described embodiments are 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 are within the scope of protection of the present invention.

[0049] Below, embodiments of the present invention will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the present invention. In the following detailed description, for ease of explanation, many specific details are set forth to provide a comprehensive understanding of embodiments of the present invention. However, it is apparent that one or more embodiments may also be implemented without these specific details. In addition, in the following description, descriptions of known structures and technologies are omitted to avoid unnecessary confusion of concepts of the present invention.

[0050] The terms used herein are only for describing specific embodiments and are not intended to limit the present invention. The terms "comprise", "include", etc. used herein indicate the existence of the features, steps, operations and / or components, but do not exclude the existence or addition of one or more other features, steps, operations or components.

[0051] All terms (including technical and scientific terms) used herein have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification, and should not be interpreted in an idealized or overly rigid manner.

[0052] In the case of using expressions such as "at least one of A, B, and C, etc.", it should generally be interpreted in accordance with the meaning of the expression generally understood by those skilled in the art (for example, "a system having at least one of A, B, and C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.). In the case of using expressions such as "at least one of A, B, or C, etc.", it should generally be interpreted in accordance with the meaning of the expression generally understood by those skilled in the art (for example, "a system having at least one of A, B, or C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.).

[0053] Some block diagrams and / or flow charts are shown in the accompanying drawings. It should be understood that some blocks or combinations thereof in the block diagrams and / or flow charts can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that these instructions can create a device for implementing the functions / operations described in these block diagrams and / or flow charts when executed by the processor. The technology of the present invention can be implemented in the form of hardware and / or software (including firmware, microcode, etc.). In addition, the technology of the present invention can take the form of a computer program product on a computer-readable storage medium storing instructions, which can be used by an instruction execution system or used in conjunction with an instruction execution system.

[0054] It should be noted that if a directional indication is involved in the embodiment of the present invention, the directional indication is only used to explain the relative position relationship, movement status, etc. between the components in a certain specific posture. If the specific posture changes, the directional indication will also change accordingly.

[0055] In addition, if there are descriptions involving "first", "second", etc. in the embodiments of the present invention, the descriptions of "first", "second", etc. are only used for descriptive purposes and cannot be understood as indicating or implying their relative importance or implicitly indicating the number of technical features indicated. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In addition, the meaning of "and / or" appearing in the full text includes three parallel schemes. Taking "A and / or B" as an example, it includes scheme A, or scheme B, or a scheme that satisfies both A and B. In addition, the technical solutions between the various embodiments can be combined with each other, but it must be based on the ability of ordinary technicians in this field to implement. When the combination of technical solutions is contradictory or cannot be implemented, it should be deemed that such a combination of technical solutions does not exist and is not within the scope of protection required by the present invention.

[0056] In the description of the present invention, it should be noted that the terms "upper", "lower", "top", "bottom", "inside", "outside", etc. indicate orientations or positional relationships based on the orientations or positional relationships shown in the accompanying drawings. They are only for the convenience of describing the present invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation. Therefore, they cannot be understood as limitations on the present invention.

[0057] In the description of the present invention, it should be noted that, unless otherwise clearly specified and limited, the terms "installed", "connected", and "connected" should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection, or it can be indirectly connected through an intermediate medium, or it can be the internal communication of two components. For ordinary technicians in this field, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

[0058] Furthermore, in the description of the present invention, unless otherwise specified, “plurality”, “multiple roots”, and “multiple groups” mean two or more.

[0059] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions 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 are within the scope of protection of the present invention.

[0060] Figure 1 The application scenario diagram of the application release risk identification method, device, electronic device, storage medium and program product according to an embodiment of the present invention is schematically shown.

[0061] It should be noted that Figure 1 The examples shown are merely examples of application scenarios to which the embodiments of the present invention can be applied, to help those skilled in the art understand the technical content of the present invention, but do not mean that the embodiments of the present invention cannot be used in other devices, systems, environments or scenarios.

[0062] like Figure 1 As shown, the application scenario 100 according to this embodiment may include a server 101, a network 102, and a virtual machine 103. The network 102 is used to provide a medium for a communication link between the server 101 and the virtual machine 103. The network 102 may include various connection types, such as wired and / or wireless communication links, and the like.

[0063] Based on the above hardware structure, an embodiment of the application release risk identification method of the present invention is proposed.

[0064] See also Figure 2 , Figure 2 The following is a flow chart of an embodiment of a method for identifying application release risks of the present invention. In one embodiment, the method for identifying application release risks includes the following steps:

[0065] S10: Create a release scenario for the application.

[0066] S20: Generate corresponding risk pre-checking orchestration tasks according to the application release scenario.

[0067] S30: Parse the risk pre-check orchestration task into different types of automated operation tasks, and issue the operation tasks to the target virtual machine in sequence according to the execution logic set by the orchestration.

[0068] In this embodiment, the release arrangement used for different scenarios is different, and the pre-check content will also be different. When the application is released, there may be unused scenarios, such as some only release the program package, some will also update the database table, and some may just apply a patch, so the user can create a release scenario according to their own needs. After the release scenario is created, the risk pre-check operation can be performed according to the specific scenario generation needs, and these risk pre-check operations can be arranged in a certain order to form a risk pre-check arrangement task corresponding to the release scenario generation. When the task is executed, the risk pre-check arrangement task is parsed into different types of automated operation tasks, and the operation tasks are sent to the target virtual machine in sequence according to the execution logic set by the arrangement to perform risk checks.

[0069] The risks that may exist in the release are organized into check items, and reusable automated operations are formed for each check item. Then, risk pre-check orchestration is generated by setting dependencies between automated operations. Different application releases can flexibly generate differentiated risk pre-check orchestrations based on different check items. Before the release is implemented, the automation module is called to perform the risk pre-check orchestration task, thereby realizing early risk checks in different release scenarios.

[0070] First, it is necessary to sort out the risks that may occur in the release of enterprise-level applications and write corresponding risk pre-check scripts or programs. This is preliminary preparation work. Therefore, the following steps are also included before step S10:

[0071] Step S1: creating an automated operation corresponding to each risk pre-check script or program, and associating the risk pre-check script or program with the automated operation corresponding to the risk pre-check script or program.

[0072] Step S2: Connect the automation operations in series according to a specific execution order.

[0073] Common risks in enterprise-level application releases include but are not limited to: 1. Whether the network connection between the application release system and the virtual machine is normal; 2. Whether the agent on the virtual machine is running normally; 3. Whether the execution user in the application release orchestration exists in the virtual machine, or whether it has execution permissions; 4. Whether the configuration file of the version package meets the format requirements; 5. Whether the execution script in the version package contains high-risk command operations. There are other differentiated risks depending on the regulatory systems or release environments of different companies. Each risk requires the writing of a corresponding risk pre-check script or program. Due to the variety of virtual machine operating systems, agents, and file formats, some risks require the preparation of multiple scripts or programs.

[0074] Then, the operation management module 106 in the automation module 105 creates an automation operation. Each risk pre-check script or program needs to create a corresponding automation operation. After the automation operation is created, the automation operation is associated with the risk pre-check script or program. In this way, when other modules call the automation operation, they can actually call the risk pre-check script or program through the automation operation by passing in input parameters, and the automation operation can also return the results of the script or program execution to other modules.

[0075] See also Figure 3 After the automated operation is created, it needs to be orchestrated. Step S20 includes:

[0076] Step S201: Obtain risk pre-check arrangement matching the current application release scenario.

[0077] Step S202: when there is only one matching risk pre-check arrangement, an execution parameter is passed to the matching risk pre-check arrangement to instantiate the risk pre-check arrangement task.

[0078] Step S203: when there are multiple matching risk pre-check arrangements, one of them is selected as the matching risk pre-check arrangement, and execution parameters are passed in to instantiate the risk pre-check arrangement task.

[0079] In this embodiment, after creating the automated operation of risk pre-check, it is necessary to create the corresponding automated orchestration in the orchestration management module 107. Automated orchestration can connect multiple independent operations in series so that the automated operation can be executed in a set logical order. At the same time, the orchestration can pass the execution results of the previously executed operations as input parameters to subsequent automated operations. Another benefit of creating automated orchestration is that automated operations can be reused. Different orchestrations can be created according to different application scenarios or release environments. Different orchestrations use tags to identify applicable scenarios or environments.

[0080] Automated orchestration is equivalent to a template, and the template can be instantiated by passing in execution parameters. Each orchestration can have multiple instances, and each instance is an orchestration task. In the release scenario module, the user first creates a release scenario and a release task. Before actually executing the release task, a risk pre-check is required for the release. The first step of risk pre-check is to generate a risk pre-check orchestration task. The specific process is as follows:

[0081] In this embodiment, the orchestration task management module in the scenario publishing module 104 calls the orchestration management module 107 to obtain the risk pre-check orchestration that matches the current application scenario or environment, and instantiates the risk pre-check orchestration task by passing execution parameters to the risk pre-check orchestration. If there are multiple matching risk pre-check orchestrations, the system provides a manual selection function. The system also provides a secondary selection of operations in the orchestration, that is, the user can choose to execute only part of the operations in the orchestration, so as to flexibly adapt to the needs of various scenarios.

[0082] Then, after receiving the risk pre-check orchestration task issued by the scenario publishing module 104, the execution module 108 of the automation module 105 parses the risk pre-check operation task according to the operation selected in the orchestration task, execution parameters, etc. The execution order of the operation tasks is determined by the orchestration logic of the automation orchestration. The execution module 108 issues the operation task to the execution agent on the virtual machine 103 (a plug-in pre-installed on the virtual machine 103 by the automation module 105), and the agent actually executes the operation task. Some operation tasks, such as testing the network connectivity with the virtual machine 103 or testing the status of the agent, are prerequisites for executing other operation tasks and are directly executed by the execution module 108. Other operation tasks can only be issued normally after the execution is correct.

[0083] After the operation task is executed, the result of the operation task execution can be queried, and after step S30, the following steps are further included:

[0084] Step S40: After receiving the execution result of the operation task, the result information is recorded.

[0085] Step S50: If the operation task fails to be executed, the execution result is pushed to the scene publishing module, and the operation task is terminated.

[0086] Step S60: If the operation task is executed successfully, the next operation task is continuously issued according to the execution sequence of the operation tasks until all tasks are executed.

[0087] In this embodiment, after receiving the execution result of the operation task, the execution module 108 records the result information. If the operation task fails to execute, the execution result is pushed to the release scenario module, and the risk pre-check operation task is issued. If the operation task is executed successfully, the next operation task is issued according to the execution order of the operation task until all tasks are executed.

[0088] In this embodiment, the results of the pre-check can also be updated synchronously for easy viewing. After step S30, the following steps are also included:

[0089] Step S70: Update the risk pre-check result information.

[0090] Step S80: If the pre-check is passed, the application publishing operation is performed.

[0091] Step S90: If the pre-check fails, the application is checked.

[0092] In this embodiment, the execution module 108 pushes the risk pre-check result to the scenario publishing module 104. The scenario publishing module 104 updates the risk pre-check result information and performs subsequent processing according to the result information. Under normal circumstances, if the risk pre-check fails, the existing risks must be resolved first and the risk pre-check must be performed again before the release task can be executed.

[0093] See also Figure 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 scenario release module 104 is used to create a release scenario and generate a release task, and create a pre-check arrangement task according to the release pre-check arrangement, and call the automation module 105 to execute the pre-check arrangement task and call the automation module 105 to execute the release task. The automation module 105 is used to create and manage automated operations and arrangements, receive the arrangement tasks of the scenario release module 104 and parse them into operation tasks, and send the operation tasks to the virtual machine 103, receive the execution results and summarize them to the scenario release module 104.

[0094] The automation module 105 includes an operation management module 106 and an orchestration management module 107. The operation management module 106 is responsible for creating and maintaining automated operations; the orchestration management module 107 is responsible for creating and maintaining automated orchestrations, and connecting the individual automated operations in series according to a specific execution order; the execution module 108 is responsible for receiving orchestration tasks, parsing the orchestration tasks into different types of automated operation tasks, and then sending execution tasks to the target virtual machine in sequence according to the execution logic set by the orchestration, and collecting the execution results of the virtual machine 103, and feeding them back to the scenario publishing module 104.

[0095] Figure 5FIG. 1 is a schematic diagram of the structure of an electronic device 1800 in a hardware operating environment according to an embodiment of the present invention. Figure 5 As shown, the electronic device 1800 may include: a processor 1801, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1802 or a program loaded from a storage part 1808 into a random access memory (RAM) 1803. The processor 1801 may, for example, include a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or a related chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 1801 may also include an onboard memory for caching purposes. The processor 1801 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present invention.

[0096] In RAM 1803, various programs and data required for the operation of electronic device 1800 are stored. Processor 1801 and storage unit 3, storage unit 3 including ROM 1802 and RAM 1803 are connected to each other via bus 1804. Processor 1801 performs various operations of the method flow according to the embodiment of the present invention by executing the programs in ROM 1802 and / or RAM 1803. It should be noted that the program may also be stored in one or more memories other than ROM 1802 and RAM 1803. Processor 1801 may also perform various operations of the method flow according to the embodiment of the present invention by executing the programs stored in the one or more memories.

[0097] According to an embodiment of the present invention, the electronic device 1800 may further include an input / output (I / O) interface 1805, which is also connected to the bus 1804. The electronic device 1800 may further include one or more of the following components connected to the I / O interface 1805: an input portion 1806 including a keyboard, a mouse, etc.; an output portion 1807 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage portion 1808 including a hard disk, etc.; and a communication portion 1809 including a network interface card such as a LAN card, a modem, etc. The communication portion 1809 performs communication processing via a network such as the Internet. A drive 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, etc., is installed on the drive 1810 as needed, so that a computer program read therefrom is installed into the storage portion 1808 as needed. The communication part 1809 is used to realize the connection communication between these components, including various connection types, such as wired, wireless communication links or optical fiber cables, etc. The input / output (I / O) interface 1805 can also include a standard wired interface and a wireless interface, wherein the wired interface can be a USB interface.

[0098] exist Figure 5 The electronic device 1800 shown also includes: a network interface mainly used to connect to the background server 103 and communicate data with the background server 103; a user interface is mainly used to connect to user equipment; the electronic device 1800 calls the control program of the automated operation and maintenance platform adaptation method stored in the memory through the processor 1801, and executes the control steps of the automated operation and maintenance platform adaptation method provided in the embodiment of the present invention.

[0099] Those skilled in the art will understand that Figure 5 The structure shown in the figure does not constitute a limitation on the electronic device 1800, and may include more or less components than shown in the figure, or combine certain components, or arrange the components differently.

[0100] The present invention also provides a computer-readable storage medium, which may be included in the device / system described in the above embodiment; or may exist independently without being assembled into the device / system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the method according to the embodiment of the present invention is implemented.

[0101] According to an embodiment of the present invention, the computer-readable storage medium may be a non-volatile computer-readable storage medium. For example, it may include, but is not limited to: 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), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present invention, the computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, an apparatus or a device.

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

[0103] According to an embodiment of the present invention, the method flow according to an embodiment of the present invention can be implemented as a computer software program. For example, an embodiment of the present invention includes a computer program product, which includes a computer program carried on a computer-readable storage medium, and the computer program contains a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through a communication part, and / or installed from a removable medium. When the computer program is executed by a processor, the above-mentioned functions defined in the system of an embodiment of the present invention are executed. According to an embodiment of the present invention, the system, equipment, device, module, unit, etc. described above can be implemented by a computer program module.

[0104] When the computer program product is run in a computer system, the program code is used to enable the computer system to implement the item recommendation method provided in the embodiment of the present invention. When the computer program is executed by the processor 1801, the above functions defined in the system / device of the embodiment of the present invention are performed. According to the embodiment of the present invention, the system, device, module, unit, etc. described above can be implemented by a computer program module.

[0105] In one embodiment, the computer program may be based on a tangible storage medium such as an optical storage device, a magnetic storage device, etc. In another embodiment, the computer program may also be transmitted and distributed in the form of a signal on a network medium, and downloaded and installed through the communication part 1809, and / or installed from a removable medium 1811. The program code contained in the computer program may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0106] In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 1809, and / or installed from the removable medium 1811. When the computer program is executed by the processor 1801, the above functions defined in the system of the embodiment of the present invention are performed. According to the embodiment of the present invention, the system, device, means, module, unit, etc. described above can be implemented by a computer program module.

[0107] According to an embodiment of the present invention, the program code for executing the computer program provided by the embodiment of the present invention can be written in any combination of one or more programming languages, specifically, these computing programs can be implemented using high-level process and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, such as Java, C++, python, "C" language or similar programming languages. The program code can be executed completely on the user computing device, partially on the user device, partially on the remote computing device, or completely on the remote computing device or server. In the case of a remote computing device, the remote computing device can be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (e.g., using an Internet service provider to connect through the Internet).

[0108] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium (such as a read-only memory image (ROM) / random access memory (RAM), a magnetic disk, or an optical disk), and includes a number of instructions for a terminal device (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in each embodiment of the present invention.

[0109] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit them; although the present invention has been described in detail with reference to the above embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the above embodiments, or replace some of the technical features therein by equivalents; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present invention. The specific embodiments described above further describe the purpose, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above description is only a specific embodiment of the present invention and is not used to limit the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for identifying application release risks, characterized in that: The steps include: Create a release scenario for the application; Generate corresponding risk pre-check orchestration tasks based on the application release scenario; Parsing the risk pre-checking orchestration 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 the orchestration; Before creating the release scenario for the application, the following steps are also included: Creating an automated operation corresponding to each risk pre-check script or program, and associating the risk pre-check script or program with the automated operation corresponding to the risk pre-check script or program; Connecting the automation operations in series according to a specific execution order; The steps for generating corresponding risk pre-check orchestration tasks according to the application release scenario include: Get the risk pre-check arrangement that matches the current application release scenario; When there is only one matching risk pre-check arrangement, the execution parameters are passed to the matching risk pre-check arrangement to instantiate the risk pre-check arrangement task; When there are multiple matching risk pre-check arrangements, one of them is selected as the matching risk pre-check arrangement, and the execution parameters are passed in to instantiate the risk pre-check arrangement task; After the step of parsing the risk pre-checking orchestration task into different types of automated operation tasks, and sending the operation tasks to the target virtual machine in sequence according to the execution logic set by the orchestration, the method further includes: After receiving the execution result of the operation task, the result information is recorded; If the operation task fails to execute, the execution result is pushed to the scenario publishing module, and the operation task is terminated; If the operation task is executed successfully, the next operation task will be issued according to the execution order of the operation tasks until all tasks are executed.

2. The application release risk identification method according to claim 1, characterized in that: After the step of parsing the risk pre-checking orchestration task into different types of automated operation tasks, and sending the operation tasks to the target virtual machine in sequence according to the execution logic set by the orchestration, the method further includes: Update the risk pre-check result information; If the pre-check passes, the application is released; If the precheck fails, troubleshoot the application.

3. An application release risk identification device, characterized in that: It includes a scene publishing module and an automation module, wherein the scene publishing module is electrically connected to the automation module; The scenario publishing module is used to create a publishing scenario and generate a publishing task, and to create a pre-check arrangement task according to the publishing pre-check arrangement, and to call the automation module to execute the pre-check arrangement task and to call the automation module to execute the publishing task; The automation module is used to create and manage automated operations and orchestrations, receive the orchestration tasks of the scenario publishing module and parse them into operation tasks, issue the operation tasks to the virtual machine, receive the execution results and summarize them to the scenario publishing module; Before creating the release scenario for the application, the following steps are also included: Creating an automated operation corresponding to each risk pre-check script or program, and associating the risk pre-check script or program with the automated operation corresponding to the risk pre-check script or program; Connecting the automation operations in series according to a specific execution order; The steps for generating corresponding risk pre-check orchestration tasks according to the application release scenario include: Get the risk pre-check arrangement that matches the current application release scenario; When there is only one matching risk pre-check arrangement, the execution parameters are passed to the matching risk pre-check arrangement to instantiate the risk pre-check arrangement task; When there are multiple matching risk pre-check arrangements, one of them is selected as the matching risk pre-check arrangement, and the execution parameters are passed in to instantiate the risk pre-check arrangement task; After the step of parsing the risk pre-checking orchestration task into different types of automated operation tasks, and sending the operation tasks to the target virtual machine in sequence according to the execution logic set by the orchestration, the method further includes: After receiving the execution result of the operation task, the result information is recorded; If the operation task fails to execute, the execution result is pushed to the scenario publishing module, and the operation task is terminated; If the operation task is executed successfully, the next operation task will be issued according to the execution order of the operation tasks until all tasks are executed.

4. The application release risk identification device according to claim 3, characterized in that: The scenario publishing module includes an orchestration task management module, which is responsible for creating, maintaining, and issuing orchestration tasks, and obtaining automated orchestration through the automation module, then passing parameters to the orchestration to generate orchestration tasks, and sending the orchestration tasks to the automation module, and receiving execution results.

5. The application release risk identification device according to claim 3, characterized in that: The automation module includes: The operations management module is responsible for creating and maintaining automated operations; The orchestration management module is responsible for creating and maintaining automation orchestrations, connecting the individual automation operations in series according to a specific execution order; The execution module is responsible for receiving the orchestration tasks, parsing the orchestration tasks into different types of automated operation tasks, and then sending the execution tasks to the target virtual machines in sequence according to the execution logic set by the orchestration, and collecting the execution results of the virtual machines and feeding them back to the scenario publishing module.

6. An electronic device, characterized in that: include: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors are enabled to execute the method according to any one of claims 1 to 2.

7. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores executable instructions, which, when executed by a processor, enable the processor to execute the method according to any one of claims 1 to 2.

8. A computer program product, characterized in that The invention comprises a computer program, which implements the method according to any one of claims 1 to 2 when being executed by a processor.

Images