CN116932337A

CN116932337A - Early warning method and early warning system based on software release process

Info

Publication number: CN116932337A
Application number: CN202310940628.9A
Authority: CN
Inventors: 梁绮琪
Original assignee: Guangzhou Chenqi Travel Technology Co Ltd
Current assignee: Guangzhou Chenqi Travel Technology Co Ltd
Priority date: 2023-07-28
Filing date: 2023-07-28
Publication date: 2023-10-24

Abstract

The invention discloses an early warning method and an early warning system based on a software release process. Setting early warning nodes according to the state of the release order; after setting different early warning values according to the early warning nodes, performing software release; in the software release process, when an abnormal situation occurs to the early warning node, early warning information is generated; pushing the early warning information to the associated account in an early warning reminding mode, and reading the early warning information and processing abnormal conditions by the associated account. By setting three early warning nodes of the early warning system, the state of the release order is tracked in real time, and the release plan and the release time are reasonably arranged and adjusted. And notifying, processing and tracking the early warning information sent by the early warning system to form a time closed loop so as to prevent information omission. And when the fault occurs, automatic notification, response and problem solving are realized, and the defect repair time is prolonged. In addition, the release progress and the situation are monitored in real time, and when problems occur, the service rollback plan can be started in time, so that the fault influence surface is reduced.

Description

Early warning method and early warning system based on software release process

Technical Field

The invention belongs to the technical field of computer software, and particularly relates to an early warning method and an early warning system based on a software release process.

Background

With the development of internet technology, technical products and services of technological companies have profound effects on society, and they can improve people's life and work patterns, and improve social productivity and quality of life. And the production release is taken as an important link of a technological company project management flow, and creating good production release conditions can help enterprises to improve release efficiency, reduce release risks, release cost and release quality.

The final goal of software release is to ensure that software can be smoothly released and normally used by users in limited time and limited resources, and meanwhile, the user experience is not influenced in the process of upgrading release, and the stability of the software is ensured. The traditional release process mainly relies on manual monitoring, and problems existing in the release process are controlled manually.

The applicant finds that the traditional release process has the problems of low efficiency and high manpower and communication cost in the operation process.

Disclosure of Invention

The invention aims to solve the technical problems and provides an early warning method and an early warning system based on a software release process.

In order to solve the problems, the invention is realized according to the following technical scheme:

according to an aspect of the present invention, there is provided an early warning method based on a software release process, the early warning method including:

setting early warning nodes according to the state of a release order, wherein the release order is a flow processing engine which penetrates through the whole software release, and the early warning nodes comprise time node early warning, UAT verification abnormality early warning and release abnormality early warning;

after setting different early warning values according to the early warning nodes, performing software release, wherein the early warning values are indexes of the early warning nodes for monitoring whether each link of the software release is abnormal or not;

in the software release process, generating early warning information after the early warning node has abnormal conditions;

pushing the early warning information to an associated account in an early warning reminding mode, and reading the early warning information and processing the abnormal situation by the associated account.

According to another aspect of the present invention, there is provided an early warning system based on a software release process, the system including:

the time node early warning module is used for generating early warning information when the time node early warning monitors that the state of the release order exceeds the corresponding circulation time and the state is not circulated;

the UAT verification abnormality early warning module is used for generating early warning information when the UAT verification abnormality early warning monitors that the defect quantity associated with all requirements is larger than an early warning value;

the abnormal issuing early warning module is used for generating early warning information when the abnormal issuing early warning monitors that the abnormal quantity of the operation log is greater than the early warning value;

the early warning information display module is used for displaying early warning information in a data list form and generating an early warning data billboard.

According to another aspect of the present invention, there is provided an electronic apparatus including:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein,,

the memory stores a computer program executable by the at least one processor, so that the at least one processor can execute the early warning method based on the software release flow according to the embodiment of the invention.

According to another aspect of the present invention, there is provided a computer readable storage medium storing a computer program, where the computer program is configured to enable a processor to implement the early warning method based on a software release process according to the embodiment of the present invention when executed.

In the embodiment of the invention, the early warning node is set according to the state of the release order, wherein the release order is a flow processing engine which penetrates through the whole software release, and the early warning node comprises time node early warning, UAT verification abnormality early warning and release abnormality early warning; after setting different early warning values according to the early warning nodes, performing software release, wherein the early warning values are indexes for monitoring whether each link of the software release is abnormal or not by the early warning nodes; in the software release process, when an abnormal situation occurs to the early warning node, early warning information is generated; pushing the early warning information to the associated account in an early warning reminding mode, and reading the early warning information and processing abnormal conditions by the associated account. By setting three early warning nodes of the early warning system, the state of the release order is tracked in real time, and the release plan and the release time are reasonably arranged and adjusted. And notifying, processing and tracking the early warning information sent by the early warning system to form a time closed loop so as to prevent information omission. And when the fault occurs, automatic notification, response and problem solving are realized, and the defect repair time is prolonged. In addition, the release progress and the situation are monitored in real time, and when problems occur, the service rollback plan can be started in time, so that the fault influence surface is reduced.

It should be understood that the description in this section is not intended to identify key or critical features of the embodiments of the invention or to delineate the scope of the invention. Other features of the present invention will become apparent from the description that follows.

Drawings

The invention is described in further detail below with reference to the attached drawing figures, wherein:

FIG. 1 is a flow chart of an early warning method based on a software release flow according to an embodiment of the invention;

FIG. 2 is an exemplary diagram of a software release process-based early warning method according to an embodiment of the present invention;

FIG. 3 is a schematic diagram of a software release process-based early warning system according to an embodiment of the present invention;

fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.

Detailed Description

In order that those skilled in the art will better understand the present invention, a technical solution in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in which it is apparent that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present invention without making any inventive effort, shall fall within the scope of the present invention.

The preferred embodiments of the present invention will be described below with reference to the accompanying drawings, it being understood that the preferred embodiments described herein are for illustration and explanation of the present invention only, and are not intended to limit the present invention.

The applicant finds that in the operation process, the progress and the condition of the software release process in the prior art are monitored by manual work, and problems in the release process are controlled by manual work, so that the following problems exist:

1. increase the communication cost: the current verification progress of the operation and maintenance can be informed only by the test line or the current verification progress of the operation and maintenance consultation is consulted with the test, the verification progress can not be known in real time and intuitively, and the release time and the release sequence are reasonably arranged.

2. Failure to respond quickly to a problem: problems in the release process cannot be timely notified to related personnel, so that the problems cannot be responded and solved quickly.

3. Increasing the manual burden: problems in the release process need to be monitored and found manually, and labor cost is increased.

4. And the user experience is reduced: problems in the release process may cause unstable services, so that problems exist in software functions, and user experience and satisfaction are affected.

5. Affecting release efficiency: the problem in the release process needs to wait for manual discovery, so that release efficiency is reduced, and project progress is affected.

Therefore, the technical scheme of the invention aims to reduce off-line communication, improve release efficiency, discover release problems, follow-up problems and record problems in time and reduce fault influence surfaces.

Fig. 1 is a flowchart of an early warning method based on a software release process according to an embodiment of the present invention, where the present embodiment is applicable to a case when an abnormal situation occurs in the software release process, the method may be performed by an early warning system based on the software release process, the system may be implemented in a form of hardware and/or software, and the system may be configured in an electronic device. As shown in fig. 1, the method includes:

and 101, setting an early warning node according to the state of the release order.

The release list is a flow processing engine which penetrates through the whole software release. The release list state is the condition of each link of the software release flow.

In the embodiment of the invention, a software release flow is firstly required to be established. The release process is specifically as follows:

a) Preparation for release: the project manager makes a release plan, determines release date, demand and defect to be released and a release-related end, creates a release sheet on a release platform, fills out the release sheet according to the release plan, and stores the release sheet in a draft state.

b) Packaging: the research and development team completes the code merging and packaging work according to the release plan formulated by the project manager and fills out the release sheet, comprising: service to be released and configuration to be released; the research and development responsible person reviews the content of the release order and circulates the release order to be 'developed and reviewed'.

c) UAT deployment: the operation and maintenance team pulls up and organizes the release review meeting, determines the service release sequence together with the research and development team, makes a deployment plan and a service rollback plan, and simultaneously completes UAT environment deployment and the circulation release order state is UAT deployment completion.

d) UAT verification: and the test team completes UAT verification according to the content of the release order and flows the release order to verify that the state is 'completed UAT'.

e) And (3) production and deployment: and the operation and maintenance team completes the production environment deployment according to the deployment plan.

And establishing an early warning system according to the software release flow, and controlling risks of the state of the release order, the UAT verification completion rate and the production deployment condition by the early warning system.

Specifically, the state of the release sheet of the software release flow specifically includes: draft, submitted, developed audited, UAT deployment completed, UAT verification passed, business acceptance passed and published.

Draft: the research and development personnel of the research and development personnel project group needs to sort the application, service, sql and cloud configuration related to the requirement to be released and fill in the release order, and the state of the circulation release order is draft.

Submitting: the research and development responsible person confirms that all research and development members of the project group fill in the application, service, sql and cloud configuration related to the requirement to be distributed to the distribution list, and the state of the circulation distribution list is 'submit'.

Research and development has been examined: the research and development responsible person examines the application, service, sql and cloud configuration related to all the requirements to be distributed in the current week, and after the examination is passed, the circulation distribution list state is 'research and development examined'.

UAT deployment is completed: after the SQL is successfully automatically executed, the system automatically completes UAT release according to release list content and automatically flows release list state UAT deployment completion "

UAT verification passes: and testing the requirement of the issuing list by a tester, and confirming whether the functions and the performances of the issuing list in the UAT environment meet the requirements or not, wherein the state of the issuing list is 'UAT verification passing' after verification passing.

Business acceptance passes: the demand sponsor performs service verification on the demand of the release order, confirms whether the service logic of the demand sponsor in the UAT environment is correct, and the state of the release order is 'service acceptance' after verification is passed.

Has been issued: and the operation and maintenance personnel deploy the contents such as the application, the service and the like of the release order into the production environment, finish the production loop, and determine that the system is not abnormal, and then the state of the circulation release order is 'released'.

The early warning system is provided with early warning nodes according to the state of a release order released by software. In the embodiment of the invention, the number of the early warning nodes is three, namely time node early warning, UAT verification abnormality early warning and abnormality early warning release.

Specifically, the time node early warning includes setting corresponding circulation time for each state of the release order. The UAT verification abnormality early warning comprises a defect quantity set early warning value associated with all requirements of the software release plan. The abnormal release early warning comprises the steps of setting early warning values for running logs of services which are subjected to software release and accounts responsible for the services.

And 102, after setting different early warning values according to the early warning nodes, releasing software.

The early warning value is an index for monitoring whether each link of software release is abnormal or not by the early warning node.

Specifically, different early warning values are set for the time node early warning, the UAT verification abnormality early warning and the issuing abnormality early warning in the early warning nodes, namely, the early warning values corresponding to different circulation times of the time node early warning setting, the defect number of the UAT verification abnormality early warning setting and the early warning values of the running log of the issuing abnormality early warning setting.

The pre-warning values of different circulation time, defect number and operation log can be set according to actual conditions, and the embodiment of the invention does not limit the implementation.

As the setting of the early warning node is carried out simultaneously with the state of the release order, when the release order is established, early warning is carried out on the state of the release order and the UAT verification completion rate, and the service to be released is started to carry out running log early warning on the release day. After the early warning value is set, software release is carried out, and the early warning system starts to monitor and early warn the software release flow.

It should be noted that, in the embodiment of the present invention, the early warning value is set by itself, for example: the distributed service is set to actively report information according to the set frequency, and if the information is not uploaded on time, the service has a problem.

And 103, in the software release process, generating early warning information after the early warning node has abnormal conditions.

In the software release process, when an abnormal situation occurs at an early warning node in the early warning system, early warning information is automatically generated.

For example, as shown in fig. 2, a release process is established, and an early warning system is established at the same time, and after different early warning values are set for different early warning nodes in the early warning system, if an abnormal condition is monitored, early warning information is automatically generated.

Specifically, abnormal conditions of different early warning nodes are as follows:

and when the time node early warning occurs that the state of the release order exceeds the corresponding circulation time, the state is not circulated, and early warning information is generated.

And when the UAT verification abnormal early warning shows that the defect number associated with all the requirements is larger than the early warning value, generating early warning information.

And when the abnormal quantity of the running logs is larger than the early warning value when the abnormal early warning is issued, generating early warning information.

In addition, in the software release process, when the abnormal condition does not occur at the early warning node, each link condition of the software release is normal, and the completion of the software release is determined.

As shown in fig. 2, the issuing process is established, the early warning system is established at the same time, after different early warning values are set for different early warning nodes in the early warning system, if no abnormal condition is monitored, the issuing is performed normally, and finally, the issuing is completed.

Step 104, pushing the early warning information to the associated account in an early warning reminding mode, and reading the early warning information and processing abnormal conditions by the associated account.

After the early warning system generates early warning information, an early warning prompt is sent to the associated account, and the early warning prompt contains the early warning information. Wherein the associated account is responsible for each state of the corresponding release order.

Specifically, in the embodiment of the present invention, the responsible person (related person) who issues the status of each stage of the sheet is as follows: when the states of the release order are a draft state and a submit state, the release order is responsible for artificial research and development team; when the state of the release order is 'research and development approved', the responsible person takes charge of the research and development; when the state of the release order is UAT deployment completion, the release order is responsible for the artificial operation and maintenance team; when the state of the release order is UAT verification passing, the release order is responsible for artificial test team; when the state of the release order is 'business acceptance passing', the release order is responsible for artificial business team; when the state of the release order is released, the release order is responsible for the human operation and maintenance team.

After the associated account (related personnel) receives the early warning prompt, the early warning information is read, and the problems in the release process are found out and solved.

Meanwhile, the early warning system adds early warning information to the early warning list, and generates an early warning data billboard, and the operation and maintenance account (operation and maintenance personnel) updates the early warning information in real time.

The early warning information is generated by an early warning system and added into an early warning list. The early warning list contains all early warning information created by the early warning system, and records basic information of each early warning event, such as time name, occurrence time, early warning level, early warning content and duration.

Based on the early warning list, the early warning system generates a visual early warning data board, and the early warning data board gathers and displays the number, trend and distribution of early warning events in a mode of icons and graphs.

Specifically, after the processing of the early warning information by the associated account (related personnel) is completed, the operation and maintenance account equipment closes the early warning reminding.

That is, the related personnel are responsible persons set by different early warning types, and the early warning content and the reverse running are solved, and the operation and maintenance personnel are informed of closing the early warning prompt after the solution is completed.

The operation and maintenance personnel follow the state and the reverse running of the early warning reminding, if the content related to the early warning reminding is solved, the early warning reminding is closed by the operation and maintenance personnel, and the operation and maintenance personnel can not solve the reminding content.

Illustratively, as shown in fig. 2, the early warning information is pushed to related personnel, and the early warning information is listed in an early warning list, and the operation and maintenance follow the early warning solution progress. And the related personnel receive the early warning information, solve the early warning problem and inform the operation and maintenance to close the early warning prompt. And the operation and maintenance personnel close the early warning reminding and continuously early warning reminding.

Fig. 3 is a schematic structural diagram of an early warning system based on a software release process according to an embodiment of the present invention. As shown in fig. 3, the system includes:

Fig. 4 shows a schematic diagram of the structure of an electronic device 10 that may be used to implement an embodiment of the invention. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. Electronic equipment may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the inventions described and/or claimed herein.

As shown in fig. 4, the electronic device 10 includes at least one processor 11, and a memory, such as a Read Only Memory (ROM) 12, a Random Access Memory (RAM) 13, etc., communicatively connected to the at least one processor 11, in which the memory stores a computer program executable by the at least one processor, and the processor 11 may perform various appropriate actions and processes according to the computer program stored in the Read Only Memory (ROM) 12 or the computer program loaded from the storage unit 18 into the Random Access Memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the electronic device 10 may also be stored. The processor 11, the ROM 12 and the RAM 13 are connected to each other via a bus 14. An input/output (I/O) interface 15 is also connected to bus 14.

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

The processor 11 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various processors running machine learning model algorithms, digital Signal Processors (DSPs), and any suitable processor, controller, microcontroller, etc. The processor 11 performs the respective methods and processes described above, such as the early warning method based on the software release flow.

In some embodiments, the early warning method based on the software release process may be implemented as a computer program, which is tangibly embodied on a computer-readable storage medium, such as the storage unit 18. In some embodiments, part or all of the computer program may be loaded and/or installed onto the electronic device 10 via the ROM 12 and/or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the above-described early warning method based on the software release process may be performed. Alternatively, in other embodiments, the processor 11 may be configured to perform the pre-warning method based on the software release procedure in any other suitable way (e.g. by means of firmware).

Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuit systems, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems On Chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs, the one or more computer programs may be executed and/or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general-purpose programmable processor, that may receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device.

A computer program for carrying out methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the computer programs, when executed by the processor, cause the functions/acts specified in the flowchart and/or block diagram block or blocks to be implemented. The computer program may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of the present invention, a computer-readable storage medium may be a tangible medium that can contain, or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. The computer readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, the computer readable storage medium may be a machine readable signal medium. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, 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), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

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

The systems and techniques described here can be implemented in a computing system that includes a background component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such background, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), blockchain networks, and the internet.

The computing system may include clients and servers. The client and server are typically remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical hosts and VPS service are overcome.

The embodiment of the invention also provides a computer program product, which comprises a computer program, and the computer program realizes the early warning method based on the software release flow provided by the embodiment of the invention when being executed by a processor.

Computer program product in the implementation, the computer program code for carrying out operations of the present invention may be written in one or more programming languages, including an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider).

It should be appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps described in the present invention may be performed in parallel, sequentially, or in a different order, so long as the desired results of the technical solution of the present invention are achieved, and the present invention is not limited herein.

The above embodiments do not limit the scope of the present invention. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the scope of the present invention.

Claims

1. An early warning method based on a software release process is characterized by comprising the following steps:

2. The early warning method based on the software release process according to claim 1, wherein the early warning node is set according to the release order state, specifically comprising:

the time node early warning comprises setting corresponding circulation time for each state of the release order;

the UAT verification abnormal early warning comprises defect quantity setting early warning values associated with all requirements of a software release plan;

the abnormal release early warning comprises the steps of setting an early warning value for a service which is releasing the software and setting an account responsible for the service for an operation log of the service.

3. The early warning method based on the software release process according to claim 2, wherein the generating early warning information after the abnormal situation occurs at the early warning node comprises:

when the time node gives an early warning that the state of the release order exceeds the corresponding circulation time, the state is not circulated, and early warning information is generated;

when the UAT verification abnormal early warning is larger than the early warning value in the defect quantity related to all requirements, early warning information is generated;

and when the abnormal quantity of the running logs is larger than the early warning value, generating early warning information.

4. The early warning method based on the software release process according to claim 1, comprising the following steps:

and when the early warning node does not have abnormal conditions, determining that each link condition of the software release is normal, and determining that the software release is completed.

5. The early warning method based on the software release process according to claim 1, further comprising:

and adding the early warning information to an early warning list, and updating the early warning information in real time by the operation and maintenance account.

6. The early warning method based on the software release process according to claim 5, wherein the operation and maintenance account updates early warning information in real time, and the method comprises the following steps:

and after the associated account finishes processing the early warning information, the operation and maintenance account equipment closes the early warning reminding.

7. An early warning system based on a software release process, the system comprising: