Online management method, system and related equipment for application version production problems

Abstract

The present invention provides an online management method, system and related equipment for application version production problems, and relates to the field of production problem management. The method includes: receiving a first setting type production work order execution information synchronized by a first system and a second setting type production work order execution information synchronized by a second system; generating a production problem sheet according to the first setting type production work order execution information or the second setting type production work order execution information; sending the production problem sheet to the associated executor of the production problem sheet, so that the associated executor can fill in the solution information of the production problem; sending the production problem sheet filled in with the solution information to the application manager according to the application system name in the production problem sheet, so that the application manager can review and confirm; after the application manager reviews and confirms, the production problem sheet is stored in the production problem library. Through the above method, the present invention can improve the efficiency of collecting and tracking application version production problems.

Description

Technical Field

[0001] The present invention relates to the field of application version production problem management, and in particular to an online management method, system and related equipment for application version production problem management. Background Art

[0002] With the rapid development of banking business, it is necessary to update and iterate the versions of various application systems of banking business, and the application versions are put into production more and more frequently. In the banking business system, there are application versions put into production almost every day, and there is a major version production point every two weeks. At a large production point, there will be hundreds of application versions put into production. With more production versions, the possibility of production incidents also increases, and the requirements for the quality of production versions are becoming more and more stringent. If the problems in production can be recorded, common production problems can be analyzed, and production risk management can be carried out in a targeted manner, effectively reducing production risks and production incidents, and providing a data basis for the production quality evaluation of the application system.

[0003] The existing production problem management mainly relies on manual sorting and reporting. The production quality manager collects the production problems offline after each production, and manually analyzes and summarizes them, which may result in statistical omissions. At the same time, production problems rely on offline summary statistics, which is labor-intensive and inefficient, resulting in the inability to effectively track production problems, and cannot adapt to a large number of frequent application version production scenarios, which is not conducive to the summary of production problems and the online production quality evaluation. Summary of the invention

[0004] To solve the above technical problems, an embodiment of the present invention provides an online management method, system and related equipment for application version production problems, so as to automatically collect and track production problems and improve the efficiency of collecting production problems.

[0005] On the one hand, an embodiment of the present invention provides an online management method for application version production problems, the method is applied to a production management and control platform, and the method includes:

[0006] Receive execution information of a first setting type production work order synchronized by a first system and execution information of a second setting type production work order synchronized by a second system, wherein the first system is used to review the application version before the application version is put into production, and the second system is used to perform automated changes according to the application version, and the first system is configured to synchronize the execution information of the first setting type production work order to the production control platform in real time when the first setting type production work order is detected, and the second system is configured to synchronize the execution information of the second setting type production work order to the production control platform in real time when the second setting type production work order is detected;

[0007] Generate a production problem sheet according to the execution information of the production work sheet of the first setting type or the execution information of the production work sheet of the second setting type, wherein the production problem sheet includes: application system name, version type, production time, production problem, and related tasks;

[0008] Sending the production problem sheet to the associated executor of the production problem sheet, so that the associated executor can fill in the solution information of the production problem in the production problem sheet, wherein the associated executor is the executor of the associated task in the production problem sheet or the designated handler of the production problem sheet;

[0009] Sending the production problem sheet filled with solution information to the application manager of the application system according to the name of the application system for review and confirmation by the application manager;

[0010] After the application manager reviews and confirms, the production problem sheet is stored in the production problem library.

[0011] In an implementation of this embodiment, the first set type of production work order of the first system includes: development and operation and maintenance handover process work order, version check work order;

[0012] The step of generating a production problem sheet according to the execution information of the production work sheet of the first setting type includes:

[0013] Acquire return information in the development and operation handover process from the execution information of the development and operation handover process work order synchronized with the first system, wherein the return information includes: application system name, version type, production time, return time, return reason, and associated tasks;

[0014] Generate a production problem ticket of development and operation handover return type according to the return information;

[0015] Acquire information about the arrival of the application version at the data center from the execution information of the version check work order synchronized by the first system, wherein the information about the arrival of the application version at the data center includes: application system name, version type, production time, arrival time, and associated tasks;

[0016] The arrival time is compared with the set arrival time. If the application version does not arrive on time, a production problem ticket of the type of version not arriving on time is generated according to the arrival information.

[0017] In one implementation of this embodiment, the second set type of production work order of the second system includes: application automation change work order, application version rollback work order, and emergency version online work order;

[0018] The step of generating a production problem sheet according to the execution information of the production work sheet of the second setting type includes:

[0019] Obtain error information in the application automation change process from the execution information of the application automation change work order synchronized by the second system, wherein the error information includes: application system name, version type, production time, error time, error reason, and associated tasks;

[0020] Generate a production problem ticket of the application automation change error type according to the error information;

[0021] Acquire application version rollback information from the execution information of the application version rollback work order synchronized by the second system, wherein the rollback information includes: application system name, version type, production time, rollback time, rollback reason, and associated tasks;

[0022] Generate a production problem sheet of application version rollback type according to the rollback information;

[0023] Acquire emergency version launch information from the execution information of the emergency version launch work order synchronized by the second system: the launch information includes: application system name, version type, production time, launch time, launch reason, and associated tasks;

[0024] A production problem sheet of the emergency version launch type is generated according to the launch information.

[0025] In an implementation of this embodiment, the method further includes:

[0026] Acquire a first setting type production work order synchronized with the first system and a second setting type production work order synchronized with the second system;

[0027] Generate a production task corresponding to the production work order according to the production work order;

[0028] Detecting the execution information of the production work order at a set time detection point;

[0029] If the production work order has not been completed when the set time point is reached, a production problem sheet of the production task delayed completion type is generated according to the execution information of the production work order.

[0030] In an implementation of this embodiment, the method further includes:

[0031] A production problem report is generated according to the production problems in the production problem library so as to analyze the production problems.

[0032] On the other hand, an embodiment of the present invention provides an online management system for application version production problems, the online management system is applied to a production management and control platform, and the online management system includes:

[0033] A receiving module, used to receive execution information of a first setting type production work order synchronized by a first system and execution information of a second setting type production work order synchronized by a second system, wherein the first system is used to review the application version before the application version is put into production, and the second system is used to perform automated changes according to the application version, and the first system is configured to synchronize the execution information of the first setting type production work order to the production control platform in real time when the first setting type production work order is detected, and the second system is configured to synchronize the execution information of the second setting type production work order to the production control platform in real time when the second setting type production work order is detected;

[0034] A production problem sheet generation module, used to generate a production problem sheet according to the execution information of the production work sheet of the first setting type or the execution information of the production work sheet of the second setting type, wherein the production problem sheet includes: application system name, version type, production time, production problem, and related tasks;

[0035] A solution filling module is used to send the production problem sheet to the associated executor of the production problem sheet, so that the associated executor can fill in the solution information of the production problem in the production problem sheet, wherein the associated executor is the executor of the associated task in the production problem sheet or the designated handler of the production problem sheet;

[0036] An audit confirmation module, used to send the production problem sheet filled with solution information to the application manager of the application system according to the name of the application system, for the application manager to review and confirm;

[0037] The storage module is used to store the production problem list in the production problem library after the application manager reviews and confirms it.

[0038] In an implementation of this embodiment, the first set type of production work order of the first system includes: development and operation and maintenance handover process work order, version check work order;

[0039] The production problem sheet generation module includes:

[0040] A return information acquisition unit is used to acquire return information in the development and operation handover process from the execution information of the development and operation handover process work order synchronized with the first system, wherein the return information includes: application system name, version type, production time, return time, return reason, and associated tasks;

[0041] A development and operation and maintenance handover return problem generating unit, used to generate a production problem sheet of a development and operation and maintenance handover return type according to the return information;

[0042] An arrival information acquisition unit, used to acquire information about the application version arriving at the data center from the execution information of the version check work order synchronized by the first system, wherein the information about the application version arriving at the data center includes: application system name, version type, production time, arrival time, and associated tasks;

[0043] The version non-arrival problem generating unit is used to compare the arrival time with the set arrival time, and if the application version does not arrive on time, generate a production problem ticket of the version non-arrival type according to the arrival information.

[0044] In one implementation of this embodiment, the second set type of production work order of the second system includes: application automation change work order, application version rollback work order, and emergency version online work order;

[0045] The production problem sheet generation module includes:

[0046] An error information acquisition unit, used to acquire error information in the application automation change process from the execution information of the application automation change work order synchronized by the second system, wherein the error information includes: application system name, version type, production time, error time, error reason, and associated tasks;

[0047] An application automation change error problem generating unit, used to generate a production problem ticket of an application automation change error type according to the error information;

[0048] A rollback information acquisition unit, used to acquire application version rollback information from the execution information of the application version rollback work order synchronized by the second system, wherein the rollback information includes: application system name, version type, production time, rollback time, rollback reason, and associated tasks;

[0049] An application version rollback problem generating unit, used to generate a production problem sheet of an application version rollback type according to the rollback information;

[0050] The emergency version online information acquisition unit is used to acquire the emergency version online information from the execution information of the emergency version online work order synchronized by the second system, wherein the online information includes: application system name, version type, production time, online time, online reason, and associated tasks;

[0051] The emergency version online problem generating unit is used to generate a production problem sheet of the emergency version online type according to the online information.

[0052] In one implementation of this embodiment, the system further includes:

[0053] A production work order acquisition module, used to acquire a production work order of a first setting type synchronized with a first system and a production work order of a second setting type synchronized with a second system;

[0054] A production task generation module, used to generate a production task corresponding to the production work order according to the production work order;

[0055] An information detection module, used to detect the execution information of the production work order at a set time detection point;

[0056] The production task delayed completion problem generation module is used to generate a production problem sheet of the production task delayed completion type according to the execution information of the production work sheet if the production work sheet has not been completed when the set time point is reached.

[0057] In one implementation of this embodiment, the system further includes:

[0058] The production problem report generation module is used to generate a production problem report according to the production problems in the production problem library so as to analyze the production problems.

[0059] On the other hand, an embodiment of the present invention provides a computer-readable storage medium having computer instructions stored thereon, which can be executed by a processor to implement the online management method for application version production problems described in any one of the above implementations.

[0060] In another aspect, an embodiment of the present invention provides a computer device, comprising:

[0061] Memory for storing computer programs;

[0062] A processor is used to execute the computer program to implement the online management method for application version production problems described in any one of the above implementation modes.

[0063] Compared with the prior art, the online management method, system and related devices for application version production problems provided by the embodiments of the present invention have the following beneficial technical effects:

[0064] In this embodiment, the first system and the second system are configured to actively synchronize the execution information of the production work order to the production control platform when a set type of production work order is detected. The production control platform receives the execution information of the production work order of the application version of each application system actively synchronized by the first system and the second system during the production and launch process, generates a production problem sheet based on the execution information, and tracks and reviews the production problems in the production problem sheet. Through this method, the embodiment of the present invention can adapt to the frequent launch scenarios of multiple application systems and multiple application versions, improve the efficiency of collecting and tracking application version production problems, and provide a data basis for subsequent production version quality management. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0066] Figure 1 This is a schematic diagram of an application scenario of the online management method for application version production problems according to Embodiment 1 of the present invention;

[0067] Figure 2 is a method flow chart of an online management method for application version production problems according to Embodiment 1 of the present invention;

[0068] Figure 3 1 is a schematic diagram of the system structure of an online management system for application version production issues according to Embodiment 2 of the present invention. DETAILED DESCRIPTION

[0069] To make the purpose, technical solution and advantages of the present invention clearer, the embodiments of the present invention will be further described in detail below in conjunction with the accompanying drawings. It should be understood that the following various embodiments are only used for illustration and are not used to limit the scope of protection of the present invention.

[0070] [Example 1]

[0071] This embodiment provides an online management method for application version production issues. Figure 1 A schematic diagram of an application scenario of Embodiment 1 of the present invention is shown. Figure 2 The flowchart of the online management method for the application version production problem according to the embodiment 1 of the present invention is shown. Figure 1 , Figure 2 As shown, the production control platform 100 can be communicated with the first system 200 and the second system 300 respectively. The online management method for application version production problems provided in this embodiment can be applied to the production control platform 100. The online management method may include the following processing:

[0072] S101: Receive execution information of a first-type production work order synchronized with a first system and execution information of a second-type production work order synchronized with a second system.

[0073] In this embodiment, the first system is used to review the application version before it goes into production. It can be configured to synchronize the detected first-set type of production work order and its execution information to the production management and control platform in real time when a first-set type of production work order is detected. The first-set type of production work order may include development and operation handover process work orders, version verification work orders, etc.

[0074] Exemplarily, the first system may be an IT (Information technology) service management system for process review of application versions. Before a new version of an application system is put into production and launched, it is necessary to conduct a process review on the version of the application system (i.e., the application version) to review whether the application version meets the conditions for production and launch. During the process review stage, the application development project team may submit a development and operation and maintenance handover process work order in the IT service management system. The development and operation and maintenance handover process work order may contain information related to the production of the application version. The relevant information may include, for example, the name of the application system to be launched, version type, production basis, implementation plan, test report, and other information. Afterwards, the application manager may review whether the application version to be launched meets the conditions for launch based on the process work order information. If the review fails, the application manager will return the development and operation and maintenance handover work order. At this time, the execution information of the development and operation and maintenance handover process work order may include return information, such as the name of the application system, version type, production time, return time, return reason, associated tasks, and the like. The IT service management system can be configured to synchronize the execution information of the development and operation process work order and the development and operation handover process work order containing return information to the production control platform in real time, so that the production control platform can generate the corresponding development and operation handover return type production problem ticket based on the execution information.

[0075] If the application version passes the review, that is, the application version meets the conditions for production and launch, the IT service management system can send the application version to the data center. At this time, the IT service management system can obtain the version check work order to detect the time when the application version arrives at the data center. The IT service management system can be configured to synchronize the execution information of the version check work order to the production control platform in real time when a version check work order is detected, so that the production control platform can generate a corresponding production problem ticket of the type of version not arriving on time based on the execution information of the version check work order, where the execution information of the version check task may include: the name of the application system to be checked, version type, production time, return time, return reason, related tasks and other information.

[0076] The second system is used to perform automated changes according to the application version, and can be configured to synchronize the execution information of the detected second set type of production work order to the production control platform in real time when a second set type of production work order is detected. The second set type of production work order may include: application automation change work order, application version rollback work order, emergency version online work order, etc.

[0077] Exemplarily, the second system may be an infrastructure and operation and maintenance management platform (hereinafter referred to as the cloud platform) for executing the application automation change process. During the automation change, the cloud platform may call various change services to execute the application automation change according to the application automation change work order. After execution, the execution information of each step of the automation change may be generated. If an error occurs in a certain change step, the execution information of the step may include error information. The cloud platform may be configured to synchronize the execution information of the application automation change work order and each step of the application automation change to the production control platform in real time when an application automation change work order is detected. Among them, the execution results of the application automation change task may include: the name of the application system that executes the automation change, version type, production time, error time, error reason, related tasks and other information.

[0078] If the application automation change of the current application version is unsuccessful, or some errors occur during the process, the cloud platform can generate an application version rollback task to automatically roll back the current application to the previous version of the current application version. At this time, the execution information of the application automation change work order can include rollback information, which can include: the name of the current application system, the current version type, the production time, the time when the rollback occurred, the reason for the rollback, and other information. The cloud platform can be configured to synchronize the execution information of the application automation change work order that should contain the rollback information to the production control platform in real time when it detects that a rollback task has been generated, so that the production control platform can generate a production problem ticket of the corresponding application version rollback type based on the rollback information.

[0079] In some implementations, the production and launch personnel can also submit an application version rollback work order to the cloud platform so that the cloud platform can execute the application version rollback according to the application version rollback work order. The cloud platform can be configured to synchronize the execution information of the application version rollback work order to the production management and control platform in real time when an application version rollback work order is detected, so that the production management and control platform can generate a corresponding production problem ticket of the application version rollback type according to the execution information of the application version rollback work order, wherein the execution information of the application version rollback work order can include application version rollback information, such as application system name, version type, production time, rollback time, rollback reason, associated tasks, etc.

[0080] In some implementations, if an application version rollback occurs, the production status of the application system in the production control platform will change to a rollback status. The production control platform can also be configured to automatically create a production problem ticket of the application version rollback type when detecting that the production status of the application system has changed to a rollback status. The rollback information of the application version may include: the name of the current application system, the current version type, the production time, the time when the rollback occurred, and other information.

[0081] If an emergency occurs, the cloud platform can generate an emergency version launch task based on the emergency version launch work order to launch the emergency version of the application. The cloud platform can be configured to synchronize the execution information of the emergency version launch work order to the production control platform in real time when the emergency version launch work order is detected, so that the production control platform can generate a corresponding emergency version launch type production problem ticket based on the execution information of the emergency version launch work order. The execution information of the emergency version launch task may include: application system name, version type, launch time, launch time, launch reason, related tasks and other information.

[0082] In this embodiment, the production time may refer to the production date.

[0083] For large business systems such as banks, different application versions of different application systems are launched every day. In this embodiment, the first system and the second system are configured to actively synchronize the execution information of the production work order to the production control platform in real time when a production work order of a set type is detected, and the production control platform receives the production information of the application versions of each application system synchronized by the first system and the second system during the production and online process. Through this method, this embodiment can adapt to the frequent online scenarios of multiple application systems and multiple application versions, and there is no need for the production control platform to go to each system separately to obtain the production information of each application version at each production stage, thereby saving the cost of obtaining production information.

[0084] S102: Generate a production problem sheet according to the execution information of the production work sheet of the first setting type or the execution information of the production work sheet of the second setting type.

[0085] In this embodiment, the production problem sheet may include: application system name, version type, production time, production problems, related tasks and other information. Among them, the production problem may further include problem type, problem summary, problem details and other information. The problem types of the generated production problem sheet may include: development and operation handover return type, version not arriving on time type, application automation change error type, application version rollback type, emergency version online type, etc.

[0086] After receiving the execution information of the production work order synchronized by the first system or the second system, the production control platform can generate a corresponding type of production problem ticket according to the execution information of the production work order.

[0087] Exemplarily, a production problem list template may be provided, which may include attributes such as application system name, version type, production time, production problems, and related tasks.

[0088] After receiving the execution information of the development and operation handover process work order or version review work order synchronized with the IT service management system, the production control platform can obtain the audited application system name, version type, production time, production problems, related tasks and other information from the execution information, fill in the obtained information into the production problem sheet template, and then generate a production problem sheet of the development and operation handover return type or the version not arriving on time type.

[0089] Specifically, for a development and operation handover return type production problem ticket, the return information during the development and operation handover process can be obtained from the execution information of the development and operation handover process work order synchronized with the IT service management system. The return information includes: application system name, version type, commissioning time, return time, return reason, and related tasks. Then, a development and operation handover return type production problem ticket can be generated based on the return information.

[0090] For production problem tickets of the type of version not arriving on time, the information on the application version arriving at the data center can be obtained from the execution information of the version review work order synchronized from the IT service management system. The information on the application version arriving at the data center includes: application system name, version type, production time, arrival time, and associated tasks. The arrival time is then compared with the set arrival time. If the application version does not arrive on time, a production problem ticket of the type of version not arriving on time is generated based on the arrival information.

[0091] In addition, after receiving the execution information of the application automation change work order, application version rollback work order or emergency version launch work order synchronized with the cloud platform, the production control platform can also obtain the name of the production application system, version type, production time, production problems, related tasks and other information from the execution information, fill in the obtained information into the production problem sheet template, and then generate a production problem sheet of the application automation error type, application version rollback type or emergency version launch type.

[0092] Specifically, for a production problem ticket of the application automation error type, the error information in the application automation change process can be obtained from the execution information of the application automation change work order synchronized with the cloud platform. The error information includes: application system name, version type, production time, error time, error reason, related tasks and other information, and then a production problem ticket of the application automation change error type is generated based on the error information.

[0093] For production issue tickets of the application version rollback type, the production management and control platform can obtain the application version rollback information from the execution information of the application version rollback work order synchronized with the cloud platform or the execution information of the application automation change work order containing rollback information. The rollback information includes: application system name, version type, production time, rollback time, rollback reason, related tasks and other information, and then a production issue ticket of the application version rollback type can be generated based on the rollback information.

[0094] In addition, the production control platform can also detect rollback information from the execution information of the application automation change work order, and generate a production problem ticket of the application version rollback type based on the rollback information in the application automation change work order execution information.

[0095] For the production problem ticket of the emergency version online type, the production management and control platform can obtain the emergency version online information from the execution information of the emergency version online work order synchronized with the cloud platform. The emergency version online information may include: application system name, version type, production time, online time, online reason, related tasks and other information, and then generate a production problem ticket of the emergency version online type according to the online information.

[0096] In one implementation of this embodiment, the production control platform can obtain a production work order of a second set type synchronized by the second system; generate a production task corresponding to the production work order based on the production work order; detect the execution information of the production work order at a set time detection point; if the production work order has not been executed when the set time point is reached, generate a production problem ticket of the delayed completion type of the production task based on the execution information of the production work order.

[0097] Among them, for the production problem ticket of the application automation change error type, after receiving the application automation change work order, the production control platform can parse the application automation change work order, obtain the process and each step of the application automation change, and then generate the production task corresponding to each step. Afterwards, the task status of the corresponding production task can be updated according to the execution information of each step. If a step is not completed on time, this embodiment can generate a production problem ticket of the application automation change error type corresponding to the step according to the execution information of the step.

[0098] This embodiment receives the execution information of the production work order synchronized by the first system or the second system, and automatically generates a production problem list according to the execution information of the production work order. Compared with the prior art of manually collecting production problems offline, this embodiment can automatically collect production problems online, thereby improving the efficiency of collecting production problems and avoiding omissions, and is more suitable for scenarios where large-scale and frequent application version commissioning is carried out.

[0099] In one implementation of this embodiment, in addition to automatically generating a production problem list, an interface for manually supplementing the production problem may also be provided so that the user can manually supplement the production problem.

[0100] For example, the production control platform can provide a page for manually supplementing production issues, which can provide items such as application system name, version type, production time, production issues, and related tasks for users to fill in. Users can choose to manually supplement the production issue list based on the automatically generated production issue list. At this time, the user can fill in the production issue information on the manual supplement production issue page, and then the production control platform can obtain the information filled in by the user and automatically generate a production issue list based on the information filled in by the user.

[0101] This embodiment provides an interface for manually supplementing the production problem list based on the automatic generation of the production problem list, and can provide a more flexible and diverse production problem collection method to improve the integrity and reliability of the production problem collection.

[0102] S103: Send the production problem list to the associated executor of the production problem list, so that the associated executor can fill in the solution information of the production problem in the production problem list.

[0103] In this embodiment, the solution information for the production problem may include: the problem resolution status, the root cause, the level classification of the problem, the associated problem ticket number, the solution information, etc. The associated executor is the executor of the associated task in the production problem ticket or the designated handler of the production problem ticket. The associated task may be a predecessor task or a dependent task of a set type of production work order. In some implementations, some types of production work orders have no associated tasks, and the information in their associated task attributes may be empty. At this time, a handler may be designated for the production problem ticket generated based on the production work order, and the handler may be an application manager or other personnel of the application system.

[0104] In one implementation of this embodiment, after generating a production problem sheet, the production control platform may send the production problem sheet to the account of the associated executor in the production control platform, and send a notification to the associated executor of the production problem sheet to remind the associated executor to fill in the solution information of the production problem. After receiving the notification, the associated executor may log in to the production control platform. At this time, the production control platform may display the production problem sheet to be supplemented in the user interface of the associated executor, so that the associated executor can fill in the solution information of the production problem in the production problem sheet.

[0105] S104: Sending the production problem sheet filled with solution information to the application manager of the application system according to the application system name in the production problem sheet for the application manager to review and confirm.

[0106] After the associated executor fills in the solution information, the commissioning control platform can send the commissioning problem sheet with the solution information filled in to the application manager account of the application system in the commissioning control platform according to the application system name in the commissioning problem sheet, and send a notification to the application manager to remind the application manager to review the commissioning problem sheet. After receiving the notification, the application manager can log in to the commissioning control platform. At this time, the commissioning control platform can display the commissioning problem sheet to be reviewed in the user interface of the application manager. The application manager can review whether the filled-in solution information is consistent with the actual situation. After the review is correct, the review can be confirmed by clicking the pass review button.

[0107] S105: After the application manager reviews and confirms, the production problem list is stored in a production problem library.

[0108] In one implementation of this embodiment, the commissioning problem sheets of each application system may be stored according to the dimensions of commissioning time (commissioning date) and application system name, thereby recording the commissioning problems of each commissioning system on each commissioning date.

[0109] Furthermore, in order to meet the requirements of production control and reduce production risks, the production control platform can generate a production problem report after each production date to facilitate analysis of production problems.

[0110] Among them, the production control platform can generate production problem reports from the dimensions of production time (each production point, each month, each quarter), problem cause, problem type, problem processing status, development unit, and implementation unit. Through these reports, production quality control personnel can view the changing trend of production problems, analyze whether they are caused by application version problems or change plan problems, which stages of production problems are concentrated, which development unit has more production problems, and which systems have more production problems.

[0111] In one implementation of this embodiment, the production control platform can also generate a production problem report using the system dimension. For example, a production problem report of a system in a certain period of time is generated based on the production problem list of a system in the period of time, or a production problem report of the entire system in a certain period of time is generated based on the production problem lists of all systems in production in a certain period of time.

[0112] By generating a production problem report according to different dimensions, this embodiment can provide a data basis for the quality evaluation of subsequent production versions, facilitate production quality management personnel to analyze production problems and strengthen risk control in a targeted manner.

[0113] [Example 2]

[0114] This embodiment provides an online management system for application version production issues. Figure 3This is a schematic diagram of the system structure of an online management system for application version production problems according to Embodiment 2 of the present invention. Figure 3 As shown, the online management system 10 for application version production problems provided in this embodiment can be applied to the production control platform, and the online management system 10 may include:

[0115] The receiving module 11 is used to receive the execution information of the first setting type production work order synchronized by the first system and the execution information of the second setting type production work order synchronized by the second system, wherein the first system is used to review the application version before the application version is put into production, and the second system is used to perform automated changes according to the application version. The first system is configured to synchronize the execution information of the first setting type production work order to the production control platform in real time when the first setting type production work order is detected, and the second system is configured to synchronize the execution information of the second setting type production work order to the production control platform in real time when the second setting type production work order is detected;

[0116] The production problem sheet generating module 12 is used to generate a production problem sheet according to the execution information of the production work sheet of the first setting type or the execution information of the production work sheet of the second setting type, wherein the production problem sheet includes: application system name, version type, production time, production problem, and related tasks;

[0117] A solution filling module 13 is used to send the production problem sheet to the associated executor of the production problem sheet, so that the associated executor can fill in the solution information of the production problem in the production problem sheet, wherein the associated executor is the executor of the associated task in the production problem sheet or the designated handler of the production problem sheet;

[0118] The review and confirmation module 14 is used to send the production problem sheet filled with solution information to the application manager of the application system according to the name of the application system for review and confirmation by the application manager;

[0119] The storage module 15 is used to store the production problem list into the production problem library after the application manager reviews and confirms it.

[0120] In an implementation of this embodiment, the first set type of production work order of the first system includes: development and operation and maintenance handover process work order, version check work order;

[0121] The production problem sheet generation module includes:

[0122] A return information acquisition unit, used to acquire return information in the development and operation handover process from the execution information of the development and operation handover process work order synchronized with the first system, wherein the return information includes: application system name, version type, production time, return time, return reason, and associated tasks;

[0123] A development and operation and maintenance handover return problem generating unit, used to generate a production problem sheet of a development and operation and maintenance handover return type according to the return information;

[0124] An arrival information acquisition unit, used to acquire information about the application version arriving at the data center from the execution information of the version check work order synchronized by the first system, wherein the information about the application version arriving at the data center includes: application system name, version type, production time, arrival time, and associated tasks;

[0125] The version non-arrival problem generating unit is used to compare the arrival time with the set arrival time, and if the application version does not arrive on time, generate a production problem ticket of the version non-arrival type according to the arrival information.

[0126] In one implementation of this embodiment, the second set type of production work order of the second system includes: application automation change work order, application version rollback work order, and emergency version online work order;

[0127] The production problem sheet generation module includes:

[0128] An error information acquisition unit, used to acquire error information in the application automation change process from the execution information of the application automation change work order synchronized by the second system, wherein the error information includes: application system name, version type, production time, error time, error reason, and associated tasks;

[0129] An application automation change error problem generating unit, used to generate a production problem ticket of an application automation change error type according to the error information;

[0130] A rollback information acquisition unit, used to acquire application version rollback information from the execution information of the application version rollback work order synchronized by the second system, wherein the rollback information includes: application system name, version type, production time, rollback time, rollback reason, and associated tasks;

[0131] An application version rollback problem generating unit, used to generate a production problem sheet of an application version rollback type according to the rollback information;

[0132] The emergency version online information acquisition unit is used to acquire the emergency version online information from the execution information of the emergency version online work order synchronized by the second system, wherein the online information includes: application system name, version type, production time, online time, online reason, and associated tasks;

[0133] The emergency version online problem generating unit is used to generate a production problem sheet of the emergency version online type according to the online information.

[0134] In one implementation of this embodiment, the online management system further includes:

[0135] A production work order acquisition module, used to acquire a production work order of a first setting type synchronized with a first system and a production work order of a second setting type synchronized with a second system;

[0136] A production task generation module, used to generate a production task corresponding to the production work order according to the production work order;

[0137] An information detection module, used to detect the execution information of the production work order at a set time detection point;

[0138] The production task delayed completion problem generation module is used to generate a production problem sheet of the production task delayed completion type according to the execution information of the production work sheet if the production work sheet has not been completed when the set time point is reached.

[0139] In one implementation of this embodiment, the online management system further includes:

[0140] The production problem report generation module is used to generate a production problem report according to the production problems in the production problem library so as to analyze the production problems.

[0141] The online management system for application version production problems provided in this embodiment can be used to implement the online management method for application version production problems described in the above embodiments. For the specific working process and processing flow, please refer to the corresponding process of the online management method for application version production problems in the above embodiments, which will not be repeated here.

[0142] Through the description of the above embodiments, those skilled in the art can clearly understand that the present invention can be implemented by combining software with a hardware platform. Based on such an understanding, all or part of the contribution of the technical solution of the present invention to the background technology can be embodied in the form of a software product, which can be stored in a storage medium such as ROM / RAM, a magnetic disk, an optical disk, etc., and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in certain parts of the various embodiments or implementation methods of the present invention.

[0143] [Example 3]

[0144] This embodiment provides a computer-readable storage medium, such as a hard disk, a CD, a flash memory, a floppy disk, a magnetic tape, etc., on which computer-readable instructions are stored. The computer-readable instructions can be executed by a processor to implement the online management method for application version production issues described in the above embodiment.

[0145] [Example 4]

[0146] This embodiment provides a computer device, including:

[0147] a memory having a computer program stored thereon,

[0148] A processor can execute the computer program to implement the processing of the online management method for application version production problems described in the above embodiment.

[0149] The terms and expressions used in this specification are for illustration only and are not intended to be limiting. It should be understood by those skilled in the art that various changes may be made to the details of the above embodiments without departing from the basic principles of the disclosed embodiments. Therefore, the scope of protection of the present invention is determined solely by the claims, and in the claims, unless otherwise specified, all terms should be understood in the broadest reasonable sense.

Claims

1. An online management method for application version production problems, characterized in that: The method is applied to a production management and control platform, and the method includes: Receive execution information of a first setting type production work order synchronized by a first system and execution information of a second setting type production work order synchronized by a second system, wherein the first system is used to review the application version before the application version is put into production, and the second system is used to perform automated changes according to the application version, and the first system is configured to synchronize the execution information of the first setting type production work order to the production control platform in real time when the first setting type production work order is detected, and the second system is configured to synchronize the execution information of the second setting type production work order to the production control platform in real time when the second setting type production work order is detected; Generate a production problem sheet according to the execution information of the production work sheet of the first setting type or the execution information of the production work sheet of the second setting type, wherein the production problem sheet includes: application system name, version type, production time, production problem, and related tasks; Sending the production problem sheet to the associated executor of the production problem sheet, so that the associated executor can fill in the solution information of the production problem in the production problem sheet, wherein the associated executor is the executor of the associated task in the production problem sheet or the designated handler of the production problem sheet; Sending the production problem sheet filled with solution information to the application manager of the application system according to the name of the application system for review and confirmation by the application manager; After the application manager reviews and confirms, the production problem sheet is stored in the production problem library; The first set type of production work order of the first system includes: development and operation and maintenance handover process work order and version verification work order; The step of generating a production problem sheet according to the execution information of the production work sheet of the first setting type includes: Detect and obtain return information in the development and operation handover process from the execution information of the development and operation handover process work order synchronized with the first system, wherein the return information includes: application system name, version type, production time, return time, return reason, and associated tasks; Generate a production problem ticket of development and operation handover return type according to the return information; Acquire information about the arrival of the application version at the data center from the execution information of the version check work order synchronized by the first system, wherein the information about the arrival of the application version at the data center includes: application system name, version type, production time, arrival time, and associated tasks; The arrival time is compared with the set arrival time. If the application version does not arrive on time, a production problem ticket of the type of version not arriving on time is generated according to the arrival information.

2. The online management method for application version production problems according to claim 1 is characterized in that: The second set type of production work order of the second system includes: application automation change work order, application version rollback work order, and emergency version online work order; The step of generating a production problem sheet according to the execution information of the production work sheet of the second setting type includes: Detect and obtain error information in the application automation change process from the execution information of the application automation change work order synchronized by the second system, wherein the error information includes: application system name, version type, production time, error time, error reason, and associated tasks; Generate a production problem ticket of the application automation change error type according to the error information; Detect and obtain the rollback information of the application version from the execution information of the application version rollback work order synchronized by the second system, wherein the rollback information includes: application system name, version type, production time, rollback time, rollback reason, and associated tasks; Generate a production problem sheet of application version rollback type according to the rollback information; Acquire emergency version launch information from the execution information of the emergency version launch work order synchronized by the second system, where the launch information includes: application system name, version type, production time, launch time, launch reason, and associated tasks; A production problem sheet of the emergency version launch type is generated according to the launch information.

3. The online management method for application version production problems according to claim 1 is characterized in that: The method further comprises: Acquire a first setting type production work order synchronized with the first system and a second setting type production work order synchronized with the second system; Generate a production task corresponding to the production work order according to the production work order; Detecting the execution information of the production work order at a set time detection point; If the production work order has not been completed when the set time point is reached, a production problem sheet of the production task delayed completion type is generated according to the execution information of the production work order.

4. The online management method for production problems according to claim 1 is characterized in that: The method further comprises: A production problem report is generated according to the production problems in the production problem library so as to analyze the production problems.

5. An online management system for application version production problems, characterized in that: The online management system is applied to the production control platform, and the online management system includes: A receiving module, used to receive execution information of a first setting type production work order synchronized by a first system and execution information of a second setting type production work order synchronized by a second system, wherein the first system is used to review the application version before the application version is put into production, and the second system is used to perform automated changes according to the application version, and the first system is configured to synchronize the execution information of the first setting type production work order to the production control platform in real time when the first setting type production work order is detected, and the second system is configured to synchronize the execution information of the second setting type production work order to the production control platform in real time when the second setting type production work order is detected; A production problem sheet generation module, used to generate a production problem sheet according to the execution information of the production work sheet of the first setting type or the execution information of the production work sheet of the second setting type, wherein the production problem sheet includes: application system name, version type, production time, production problem, and related tasks; A solution filling module is used to send the production problem sheet to the associated executor of the production problem sheet, so that the associated executor can fill in the solution information of the production problem in the production problem sheet, wherein the associated executor is the executor of the associated task in the production problem sheet or the designated handler of the production problem sheet; An audit confirmation module, used to send the production problem sheet filled with solution information to the application manager of the application system according to the name of the application system, for the application manager to review and confirm; A storage module, used for storing the production problem sheet in a production problem library after the application manager has reviewed and confirmed the sheet; The first set type of production work order of the first system includes: development and operation and maintenance handover process work order and version verification work order; The production problem sheet generation module includes: A return information acquisition unit, used to detect and acquire return information in the development and operation handover process from the execution information of the development and operation handover process work order synchronized with the first system, wherein the return information includes: application system name, version type, production time, return time, return reason, and associated tasks; A development and operation and maintenance handover return problem generating unit, used to generate a production problem sheet of a development and operation and maintenance handover return type according to the return information; An arrival information acquisition unit, used to acquire information about the application version arriving at the data center from the execution information of the version check work order synchronized by the first system, wherein the information about the application version arriving at the data center includes: application system name, version type, production time, arrival time, and associated tasks; The version non-arrival problem generating unit is used to compare the arrival time with the set arrival time, and if the application version does not arrive on time, generate a production problem ticket of the version non-arrival type according to the arrival information.

6. The online management system for application version production problems according to claim 5, characterized in that: The second set type of production work order of the second system includes: application automation change work order, application version rollback work order, and emergency version online work order; The production problem sheet generation module includes: An error information acquisition unit, used to detect and acquire error information in the application automation change process from the execution information of the application automation change work order synchronized by the second system, wherein the error information includes: application system name, version type, production time, error time, error reason, and associated tasks; An application automation change error problem generating unit, used to generate a production problem ticket of an application automation change error type according to the error message; A rollback information acquisition unit, used to acquire the rollback information of the application version from the execution information of the application version rollback work order synchronized by the second system, wherein the rollback information includes: application system name, version type, production time, rollback time, rollback reason, and associated tasks; An application version rollback problem generating unit, used to generate a production problem sheet of an application version rollback type according to the rollback information; The emergency version online information acquisition unit is used to acquire the emergency version online information from the execution information of the emergency version online task synchronized by the second system, wherein the online information includes: application system name, version type, production time, online time, online reason, and associated tasks; The emergency version online problem generating unit is used to generate a production problem sheet of the emergency version online type according to the online information.

7. The online management system for application version production problems according to claim 5, characterized in that: The online management system also includes: A production work order acquisition module, used to acquire a production work order of a first setting type synchronized with a first system and a production work order of a second setting type synchronized with a second system; A production task generation module, used to generate a production task corresponding to the production work order according to the production work order; An information detection module, used to detect the execution information of the production work order at a set time detection point; The production task delayed completion problem generation module is used to generate a production problem sheet of the production task delayed completion type according to the execution information of the production work sheet if the production work sheet has not been completed when the set time point is reached.

8. The online management system for production problems according to claim 5, characterized in that: The online management system also includes: The production problem report generation module is used to generate a production problem report according to the production problems in the production problem library so as to analyze the production problems.

9. A computer-readable storage medium having computer instructions stored thereon, characterized in that: The computer instructions can be executed by a processor to implement the online management method for application version production problems described in any one of claims 1-4.

10. A computer device, characterized in that: include: Memory for storing computer programs; A processor is used to execute the computer program to implement the online management method for application version production problems as described in any one of claims 1 to 4.

Images