CN113656003A - Software package management method and related equipment - Google Patents
Software package management method and related equipment Download PDFInfo
- Publication number
- CN113656003A CN113656003A CN202111006053.0A CN202111006053A CN113656003A CN 113656003 A CN113656003 A CN 113656003A CN 202111006053 A CN202111006053 A CN 202111006053A CN 113656003 A CN113656003 A CN 113656003A
- Authority
- CN
- China
- Prior art keywords
- pipeline processing
- software package
- determining
- target
- reason
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3604—Software analysis for verifying properties of programs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/57—Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
- G06F21/577—Assessing vulnerabilities and evaluating computer system security
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Computer Hardware Design (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Quality & Reliability (AREA)
- Computing Systems (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a software package management method and related equipment, which can determine the reason of pipeline processing failure, determine a target abnormal type matched with the reason of pipeline processing failure, determine an abnormal description text matched with the target abnormal type, determine a technical responsible person identifier corresponding to the target abnormal type, and send the abnormal description text to the target technical responsible person corresponding to the technical responsible person identifier according to a specified information sending mode in the process of pipeline processing aiming at a target software package. The method and the device can determine the reason of the processing failure when the processing failure occurs in the process of the pipeline processing, and inform the corresponding technical responsible person of the corresponding abnormal description text, so that the technical responsible person can timely master the reason of the processing failure and the abnormal type, and the problem of potential fault factors or abnormal conditions is quickly solved, thereby quickly recovering the process of the pipeline processing of the target software package.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a software package management method and related equipment.
Background
With the development of computer technology, software package management technology is continuously improved.
The software package pipeline processing mode can be a core mode of continuous integration and continuous delivery, and can be used for visually presenting the delivery process of the software package. Specifically, the pipeline processing process of the software package can show the whole process from submission, construction, deployment, testing to release of the software package, and tasks related to the software package can be continuously and sequentially executed according to a certain route and task links.
Currently, in the process of software package development, after a software developer writes the code of a software package in a Team Foundation Server (TFS), the software developer needs to perform corresponding pipeline processing on the written software package. After the pipeline process is successfully completed, the software package can be delivered or released to the customer.
However, in the case of a processing failure that may occur during pipeline processing, the prior art cannot perform processing efficiently.
Disclosure of Invention
In view of the above problems, the present invention provides a software package management method and related device for overcoming the above problems or at least partially solving the above problems, and the technical solutions are as follows:
a software package management method, comprising:
in the process of pipeline processing aiming at the target software package, when pipeline processing fails, determining a reason of the pipeline processing failure;
determining a target exception type matched with the pipeline processing failure reason;
determining an anomaly description text matched with the target anomaly type;
determining a technical leader identification corresponding to the target anomaly type;
and sending the abnormal description text to a target technical responsible person corresponding to the technical responsible person identifier according to a specified information sending mode.
Optionally, when pipeline processing fails, determining a reason for the pipeline processing failure includes:
determining a software package detection link in which the pipeline processing fails;
extracting a parameter value of at least one designated parameter corresponding to the software package detection link in a data storage space for recording pipeline processing process parameters, wherein each designated parameter comprises an input parameter and a return value type;
and determining a corresponding pipeline processing failure reason according to the parameter value of each specified parameter.
Optionally, the pipeline processing process includes: compiling and constructing, code quality checking, unit testing, automation testing and/or security vulnerability scanning and checking.
Optionally, the information sending method includes: mail, text messages, and/or social software.
A software package management apparatus comprising: the device comprises a first determining unit, a second determining unit, a third determining unit, a fourth determining unit and a sending unit; wherein:
the first determination unit is configured to perform: in the process of pipeline processing aiming at the target software package, when pipeline processing fails, determining a reason of the pipeline processing failure;
the second determination unit configured to perform: determining a target exception type matched with the pipeline processing failure reason;
the third determination unit is configured to perform: determining an anomaly description text matched with the target anomaly type;
the fourth determination unit configured to perform: determining a technical leader identification corresponding to the target anomaly type;
the transmitting unit is configured to perform: and sending the abnormal description text to a target technical responsible person corresponding to the technical responsible person identifier according to a specified information sending mode.
Optionally, the first determining unit includes: a fifth determining unit, an extracting unit and a sixth determining unit; wherein:
the fifth determination unit configured to perform: determining a software package detection link in which the pipeline processing fails;
the extraction unit configured to perform: extracting a parameter value of at least one designated parameter corresponding to the software package detection link in a data storage space for recording pipeline processing process parameters, wherein each designated parameter comprises an input parameter and a return value type;
the sixth determining unit configured to perform: and determining a corresponding pipeline processing failure reason according to the parameter value of each specified parameter.
Optionally, the pipeline processing process includes: compiling and constructing, code quality checking, unit testing, automation testing and/or security vulnerability scanning and checking.
Optionally, the information sending method includes: mail, text messages, and/or social software.
An electronic device comprising at least one processor, and at least one memory, bus connected with the processor; the processor and the memory complete mutual communication through the bus; the processor is used for calling the program instructions in the memory so as to execute the software package management method.
A computer-readable storage medium on which a program is stored, which when executed by a processor implements the above-described software package management method.
The software package management method and the related device provided by this embodiment may determine, when pipeline processing fails in a pipeline processing process performed on a target software package, a reason for the pipeline processing failure, determine a target exception type matched with the reason for the pipeline processing failure, determine an exception description text matched with the target exception type, determine a technical responsible person identifier corresponding to the target exception type, and send the exception description text to the target technical responsible person corresponding to the technical responsible person identifier according to a specified information sending manner. The method and the device can determine the reason of the processing failure, determine the type of the target exception and inform the corresponding technical responsible person of the corresponding exception description text when the processing failure occurs in the process of the pipeline processing, so that the technical responsible person of the target can master the reason of the processing failure and the type of the exception in time and quickly solve the potential fault factors or exception problems, thereby quickly restoring the process of the pipeline processing of the target software package.
The foregoing description is only an overview of the technical solutions of the present invention, and the following detailed description of the present invention is provided to enable the technical means of the present invention to be more clearly understood, and to enable the above and other objects, features, and advantages of the present invention to be more clearly understood.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a flowchart illustrating a software package management method according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of a software package management apparatus according to an embodiment of the present invention;
fig. 3 shows a schematic structural diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the invention are shown in the drawings, it should be understood that the invention can be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art.
As shown in fig. 1, the present embodiment provides a software package management method, which may include the following steps:
s101, in the process of pipeline processing aiming at a target software package, when pipeline processing fails, determining a reason for the pipeline processing failure;
the target software package may be a software package written by a software developer, or a software package provided by a partner, which is not limited in the present invention.
Specifically, the method and the device can determine the pipeline processing failure when the conditions such as abnormal warning or processing failure prompt occur in the pipeline processing process, and can further determine the reason of the pipeline processing failure.
It should be noted that the pipeline process may be performed in the TFS.
Optionally, the pipeline processing process includes: compiling and constructing, code quality checking, unit testing, automation testing and/or security vulnerability scanning and checking.
Wherein, the compiling and constructing process can be a compiling and constructing process of the target software package. It should be noted that, after the source code of the target software package is written, the source code of the target software package may be compiled to construct the target software package.
The code quality inspection may be a static analysis process performed on the source code quality of the target software package, and may be performed to research and read the source code of the target software package, and check whether an error exists in the source code according to a predefined inspection rule.
The unit test may refer to a process of checking and verifying a minimum testable unit in the target software package. It should be noted that the unit may be a minimum tested function module specified by a technician.
The automatic test may refer to a software automatic test process performed on the target software package, and the target software package may be run under a preset condition to obtain and evaluate a running result. The preset condition may include a normal condition and an abnormal condition.
The security vulnerability scanning inspection is a security detection (penetration attack) behavior which can detect the security vulnerability of the target software package by means of scanning based on a vulnerability database and find available vulnerabilities.
Optionally, the present invention may use an exception cause locating technique adopted in the prior art to determine the reason for the pipeline processing failure.
Optionally, in another software package management method proposed in this embodiment, step S101 may also include the following steps:
determining a software package detection link in which the pipeline processing fails;
extracting a parameter value of at least one designated parameter corresponding to a software package detection link in a data storage space for recording the parameters of the pipeline processing process, wherein each designated parameter comprises an input parameter and a return value type;
and determining the corresponding pipeline processing failure reason according to the parameter value of each designated parameter.
Optionally, the software package detection loop may be one of the above compiling and building, code quality inspection, unit test, automation test and security vulnerability scanning inspection processes.
The data storage space may be a memory or a hard disk, and the specific type of the data storage space is not limited in the present invention.
Specifically, the invention can determine one or more corresponding designated parameters in advance according to different software package detection links. When the target software package is in a certain software package detection link and processing failure occurs in the software package detection link, the method can judge the processing failure reason according to the parameter values by extracting the parameter values of corresponding specified parameters.
S102, determining a target exception type matched with a pipeline processing failure reason;
optionally, the present invention presets the corresponding relationship between different pipeline processing failure reasons and the exception types. It should be noted that the corresponding relationship may be determined by a technician according to historical data and work experience.
Specifically, the method and the device can search the abnormal type corresponding to the reason of the pipeline failure after the reason of the pipeline processing failure is determined, and determine the searched abnormal type as the target abnormal type.
S103, determining an abnormal description text matched with the target abnormal type;
specifically, the invention can preset the abnormal description texts corresponding to different abnormal types. The abnormality description text may describe the abnormality generation cause, development process, adverse effect, processing time limit, and the like of the abnormality type.
Specifically, after the target exception type is determined, the exception description text corresponding to the target exception type is determined.
Optionally, in other software package management methods proposed in this embodiment, the exception description text matched with different pipeline processing failure reasons may also be preset in the present invention, and there is no need to set exception description texts corresponding to different exception types. At this time, the invention can determine the corresponding abnormal description text directly according to the determined pipeline processing failure reason after determining the pipeline processing failure reason.
S104, determining a technical responsible person identifier corresponding to the target abnormal type;
the technical responsible person identifier may be an identifier of the technical responsible person, and may be used to identify the technical responsible person.
Optionally, the technical responsible person identifier may be a name of the technical responsible person, or a job number and a post name of the technical responsible person, and the specific type of the technical responsible person identifier is not limited in the present invention.
Where the technical leader may be a technician who specifies handling of a certain type of exception. It should be noted that the present invention may be pre-assigned by a technical team to a technician responsible for handling different exception types.
Optionally, when a processing failure occurs in the pipeline processing process, the method and the system can send the processing failure to the corresponding technical responsible person in time, prompt the technical responsible person to perform troubleshooting in time, solve a potential or occurred fault, ensure that the target software package can continue to be processed in the pipeline, improve the processing efficiency, and ensure the testing efficiency and the timely delivery of the target software package.
And S105, sending the abnormal description text to a target technical responsible person corresponding to the technical responsible person identifier according to the specified information sending mode.
Optionally, the information sending method may include: mail, text messages, and/or social software.
It will be appreciated that the target technical leader may be a technical leader that specifies the type of handling the target anomaly.
Specifically, after the technical responsible person corresponding to the target abnormal type is determined, the abnormal description text is sent to the relevant electronic equipment (such as a mobile phone, a tablet computer, a working computer and the like) of the target technical responsible person in a specified information sending mode to prompt the target technical responsible person that the processing fails in the pipeline processing process, so that the target technical responsible person can timely master the reason and the abnormal type of the processing failure, the potential fault factor or the abnormal problem is quickly solved, and the pipeline processing process of the target software package can be quickly recovered.
It should be noted that, in the prior art, when a processing failure occurs in a pipeline processing process, the prior art cannot determine a specific processing failure reason, and no matter which detection link or which processing failure reason is, the prior art can send a mail notification to all people of a technical team, but cannot notify a specific technical responsible person, which affects timeliness of exception resolution, and causes a delay in pipeline processing. The method and the device can determine the reason of the processing failure, determine the type of the target exception and inform the corresponding technical responsible person of the corresponding exception description text when the processing failure occurs in the process of the pipeline processing, so that the technical responsible person of the target can master the reason of the processing failure and the type of the exception in time and quickly solve the potential fault factors or exception problems, thereby quickly restoring the process of the pipeline processing of the target software package.
The software package management method provided by this embodiment may determine, when pipeline processing fails in a pipeline processing process performed on a target software package, a reason for the pipeline processing failure, determine a target exception type matched with the reason for the pipeline processing failure, determine an exception description text matched with the target exception type, determine a technical responsible person identifier corresponding to the target exception type, and send the exception description text to the target technical responsible person corresponding to the technical responsible person identifier according to a specified information sending manner. The method and the device can determine the reason of the processing failure, determine the type of the target exception and inform the corresponding technical responsible person of the corresponding exception description text when the processing failure occurs in the process of the pipeline processing, so that the technical responsible person of the target can master the reason of the processing failure and the type of the exception in time and quickly solve the potential fault factors or exception problems, thereby quickly restoring the process of the pipeline processing of the target software package.
Corresponding to the steps shown in fig. 1, as shown in fig. 2, the present embodiment proposes a software package management apparatus, which may include: a first determining unit 101, a second determining unit 102, a third determining unit 103, a fourth determining unit 104, and a transmitting unit 105; wherein:
a first determination unit 101 configured to perform: in the process of pipeline processing aiming at the target software package, when pipeline processing fails, determining a reason of the pipeline processing failure;
the target software package may be a software package written by a software developer, or a software package provided by a partner, which is not limited in the present invention.
Specifically, the method and the device can determine the pipeline processing failure when the conditions such as abnormal warning or processing failure prompt occur in the pipeline processing process, and can further determine the reason of the pipeline processing failure.
Optionally, the pipeline processing process includes: compiling and constructing, code quality checking, unit testing, automation testing and/or security vulnerability scanning and checking.
Optionally, in another software package management apparatus proposed in this embodiment, the first determining unit 101 includes: a fifth determining unit, an extracting unit and a sixth determining unit; wherein:
a fifth determination unit configured to perform: determining a software package detection link in which the pipeline processing fails;
an extraction unit configured to perform: extracting a parameter value of at least one designated parameter corresponding to a software package detection link in a data storage space for recording the parameters of the pipeline processing process, wherein each designated parameter comprises an input parameter and a return value type;
a sixth determination unit configured to perform: and determining the corresponding pipeline processing failure reason according to the parameter value of each designated parameter.
Specifically, the invention can determine one or more corresponding designated parameters in advance according to different software package detection links. When the target software package is in a certain software package detection link and processing failure occurs in the software package detection link, the method can judge the processing failure reason according to the parameter values by extracting the parameter values of corresponding specified parameters.
A second determining unit 102 configured to perform: determining a target exception type matched with a pipeline processing failure reason;
optionally, the present invention presets the corresponding relationship between different pipeline processing failure reasons and the exception types. It should be noted that the corresponding relationship may be determined by a technician according to historical data and work experience.
Specifically, the method and the device can search the abnormal type corresponding to the reason of the pipeline failure after the reason of the pipeline processing failure is determined, and determine the searched abnormal type as the target abnormal type.
A third determining unit 103 configured to perform: determining an abnormal description text matched with the target abnormal type;
specifically, the invention can preset the abnormal description texts corresponding to different abnormal types. The abnormality description text may describe the abnormality generation cause, development process, adverse effect, processing time limit, and the like of the abnormality type.
Specifically, after the target exception type is determined, the exception description text corresponding to the target exception type is determined.
Optionally, in other software package management apparatuses proposed in this embodiment, the present invention may also preset exception description texts matched with different pipeline processing failure reasons, without setting exception description texts corresponding to different exception types. At this time, the invention can determine the corresponding abnormal description text directly according to the determined pipeline processing failure reason after determining the pipeline processing failure reason.
A fourth determination unit 104 configured to perform: determining a technical responsible person identifier corresponding to the target anomaly type;
the technical responsible person identifier may be an identifier of the technical responsible person, and may be used to identify the technical responsible person.
Optionally, the technical responsible person identifier may be a name of the technical responsible person, or a job number and a post name of the technical responsible person, and the specific type of the technical responsible person identifier is not limited in the present invention.
Where the technical leader may be a technician who specifies handling of a certain type of exception. It should be noted that the present invention may be pre-assigned by a technical team to a technician responsible for handling different exception types.
Optionally, when a processing failure occurs in the pipeline processing process, the method and the system can send the processing failure to the corresponding technical responsible person in time, prompt the technical responsible person to perform troubleshooting in time, solve a potential or occurred fault, ensure that the target software package can continue to be processed in the pipeline, improve the processing efficiency, and ensure the testing efficiency and the timely delivery of the target software package.
A transmitting unit 105 configured to perform: and sending the abnormal description text to a target technical responsible person corresponding to the technical responsible person identifier according to a specified information sending mode.
Optionally, the information sending method may include: mail, text messages, and/or social software.
It will be appreciated that the target technical leader may be a technical leader that specifies the type of handling the target anomaly.
Specifically, after the technical responsible person corresponding to the target abnormal type is determined, the abnormal description text is sent to the relevant electronic equipment of the target technical responsible person in an appointed information sending mode to prompt the target technical responsible person that the processing fails in the process of the pipeline processing, so that the target technical responsible person can timely master the reason of the processing failure and the abnormal type, the potential fault factor or the abnormal problem can be rapidly solved, and the process of the pipeline processing of the target software package can be rapidly recovered.
The software package management device provided by the embodiment can determine the reason of the processing failure, determine the type of the target exception and inform the corresponding exception description text to the corresponding technical responsible person when the processing failure occurs in the process of the pipeline processing, so that the technical responsible person can timely master the reason of the processing failure and the type of the exception, the potential fault factor or exception problem can be rapidly solved, and the process of the pipeline processing of the target software package can be rapidly recovered.
The software package management device may include a processor and a memory, where the first determining unit 101, the second determining unit 102, the third determining unit 103, the fourth determining unit 104, the sending unit 105, and the like are stored in the memory as program units, and the processor executes the program units stored in the memory to implement corresponding functions.
The processor comprises a kernel, and the kernel calls the corresponding program unit from the memory. The kernel can be set to be one or more, and the software package management method is realized by adjusting kernel parameters.
An embodiment of the present invention provides a computer-readable storage medium on which a program is stored, which, when executed by a processor, implements the above-described software package management method.
The embodiment of the invention provides a processor, which is used for running a program, wherein the software package management method is executed when the program runs.
As shown in fig. 3, an embodiment of the present invention provides an electronic device 300, where the electronic device 300 includes at least one processor 301, at least one memory 302 connected to the processor 301, and a bus 303; wherein, the processor 301 and the memory 302 complete the communication with each other through the bus 303; the processor 301 is used to call program instructions in the memory 302 to perform the above-described software package management method. The electronic device 300 herein may be a server, a PC, a PAD, a mobile phone, etc.
Embodiments of the present invention further provide a computer program product, which, when executed on an electronic device, is adapted to perform a procedure for initializing the following method steps:
in the process of pipeline processing aiming at the target software package, when pipeline processing fails, determining a reason of the pipeline processing failure;
determining a target exception type matched with a pipeline processing failure reason;
determining an abnormal description text matched with the target abnormal type;
determining a technical responsible person identifier corresponding to the target anomaly type;
and sending the abnormal description text to a target technical responsible person corresponding to the technical responsible person identifier according to a specified information sending mode.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus, electronic devices (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, an electronic device includes one or more processors (CPUs), memory, and a bus. The electronic device may also include input/output interfaces, network interfaces, and the like.
The memory may include volatile memory in a computer readable medium, Random Access Memory (RAM) and/or nonvolatile memory such as Read Only Memory (ROM) or flash memory (flash RAM), and the memory includes at least one memory chip. The memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in the process, method, article, or apparatus that comprises the element.
The above are merely examples of the present application and are not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
Claims (10)
1. A method for software package management, comprising:
in the process of pipeline processing aiming at the target software package, when pipeline processing fails, determining a reason of the pipeline processing failure;
determining a target exception type matched with the pipeline processing failure reason;
determining an anomaly description text matched with the target anomaly type;
determining a technical leader identification corresponding to the target anomaly type;
and sending the abnormal description text to a target technical responsible person corresponding to the technical responsible person identifier according to a specified information sending mode.
2. The software package management method according to claim 1, wherein the determining a reason for pipeline processing failure when pipeline processing failure occurs comprises:
determining a software package detection link in which the pipeline processing fails;
extracting a parameter value of at least one designated parameter corresponding to the software package detection link in a data storage space for recording pipeline processing process parameters, wherein each designated parameter comprises an input parameter and a return value type;
and determining a corresponding pipeline processing failure reason according to the parameter value of each specified parameter.
3. The method of claim 1, wherein the pipeline process comprises: compiling and constructing, code quality checking, unit testing, automation testing and/or security vulnerability scanning and checking.
4. The method of claim 1, wherein the information sending method comprises: mail, text messages, and/or social software.
5. A software package management apparatus, comprising: the device comprises a first determining unit, a second determining unit, a third determining unit, a fourth determining unit and a sending unit; wherein:
the first determination unit is configured to perform: in the process of pipeline processing aiming at the target software package, when pipeline processing fails, determining a reason of the pipeline processing failure;
the second determination unit configured to perform: determining a target exception type matched with the pipeline processing failure reason;
the third determination unit is configured to perform: determining an anomaly description text matched with the target anomaly type;
the fourth determination unit configured to perform: determining a technical leader identification corresponding to the target anomaly type;
the transmitting unit is configured to perform: and sending the abnormal description text to a target technical responsible person corresponding to the technical responsible person identifier according to a specified information sending mode.
6. The package management apparatus according to claim 5, wherein the first determination unit includes: a fifth determining unit, an extracting unit and a sixth determining unit; wherein:
the fifth determination unit configured to perform: determining a software package detection link in which the pipeline processing fails;
the extraction unit configured to perform: extracting a parameter value of at least one designated parameter corresponding to the software package detection link in a data storage space for recording pipeline processing process parameters, wherein each designated parameter comprises an input parameter and a return value type;
the sixth determining unit configured to perform: and determining a corresponding pipeline processing failure reason according to the parameter value of each specified parameter.
7. The package management apparatus according to claim 5, wherein the pipeline processing procedure comprises: compiling and constructing, code quality checking, unit testing, automation testing and/or security vulnerability scanning and checking.
8. The package management apparatus according to claim 5, wherein the information transmission means includes: mail, text messages, and/or social software.
9. An electronic device comprising at least one processor, and at least one memory, bus connected to the processor; the processor and the memory complete mutual communication through the bus; the processor is configured to call program instructions in the memory to perform the software package management method of any one of claims 1 to 4.
10. A computer-readable storage medium on which a program is stored, the program implementing the software package management method according to any one of claims 1 to 4 when executed by a processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111006053.0A CN113656003A (en) | 2021-08-30 | 2021-08-30 | Software package management method and related equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111006053.0A CN113656003A (en) | 2021-08-30 | 2021-08-30 | Software package management method and related equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113656003A true CN113656003A (en) | 2021-11-16 |
Family
ID=78493264
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111006053.0A Pending CN113656003A (en) | 2021-08-30 | 2021-08-30 | Software package management method and related equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113656003A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117591437A (en) * | 2024-01-18 | 2024-02-23 | 杭州罗莱迪思科技股份有限公司 | Automatic detection and test method for Web program abnormality |
-
2021
- 2021-08-30 CN CN202111006053.0A patent/CN113656003A/en active Pending
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117591437A (en) * | 2024-01-18 | 2024-02-23 | 杭州罗莱迪思科技股份有限公司 | Automatic detection and test method for Web program abnormality |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109032824B (en) | Database verification method, database verification device, computer equipment and storage medium | |
| WO2019237118A1 (en) | Business-aware intelligent incident and change management | |
| CN110650036A (en) | Alarm processing method and device and electronic equipment | |
| CN108038039B (en) | Method for recording log and micro-service system | |
| CN113315828B (en) | Traffic recording method and device, traffic recording equipment and storage medium | |
| CN113641526B (en) | Alarm root cause positioning method and device, electronic equipment and computer storage medium | |
| CN113051180A (en) | Test task monitoring method, device, equipment and storage medium | |
| CN113656003A (en) | Software package management method and related equipment | |
| CN107679423A (en) | Partition integrity inspection method and device | |
| CN111767218B (en) | Automatic test method, equipment and storage medium for continuous integration | |
| CN116194894A (en) | Fault localization of native cloud applications | |
| CN111444093B (en) | Method and device for determining quality of project development process and computer equipment | |
| US11790249B1 (en) | Automatically evaluating application architecture through architecture-as-code | |
| CN117076301A (en) | System performance test method and device and electronic equipment | |
| CN114500249B (en) | Root cause positioning method and device | |
| CN116599881A (en) | Cloud platform tenant modeling test method, device, equipment and storage medium | |
| CN111143151B (en) | Service monitoring method and device and electronic equipment | |
| CN112988444B (en) | Processing method, processing device and processing equipment for server cluster fault diagnosis, method for server fault diagnosis and computer-readable storage medium | |
| CN115525568A (en) | Code coverage rate inspection method and device, computer equipment and storage medium | |
| CN115190293A (en) | Dial testing method and device, electronic equipment and computer storage medium | |
| CN112286792A (en) | Interface testing method, device, equipment and storage medium | |
| CN114168108A (en) | Code merging method and device, electronic equipment and computer readable storage medium | |
| CN111414269A (en) | Log alarm method, device, storage medium and equipment | |
| CN115545677B (en) | Online process specification detection method and system based on automatic case execution condition | |
| CN112286791A (en) | Business system testing method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |