Code-change and developer rating in an automated-application-release-management subsystem
US-2019227793-A1 · Jul 25, 2019 · US
US10901876B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10901876-B2 |
| Application number | US-201916689804-A |
| Country | US |
| Kind code | B2 |
| Filing date | Nov 20, 2019 |
| Priority date | Oct 9, 2018 |
| Publication date | Jan 26, 2021 |
| Grant date | Jan 26, 2021 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A method, system and computer program product for detecting potential failures in a continuous delivery pipeline. A machine learning model is created to predict whether changed portion of codes under development at various stages of the continuous delivery pipeline will result in a pipeline failure. After creating the machine learning model, log file(s) may be received that were generated by development tool(s) concerning a changed portion of code under development at a particular stage of the continuous delivery pipeline. The machine learning model provides relationship information between the log file(s) and the changed portion of code. A message is then generated and displayed based on this relationship information, where the message may provide a prediction or a recommendation concerning potential failures in the continuous delivery pipeline. In this manner, the potential failures in the continuous delivery pipeline may be prevented without requiring context switching.
Opening claim text (preview).
The invention claimed is: 1. A computer program product for detecting potential failures in a continuous delivery pipeline, the computer program product comprising one or more computer readable storage mediums having program code embodied therewith, the program code comprising the programming instructions for: creating a machine learning model to predict whether changed portions of code under development at various stages of said continuous delivery pipeline will result in a pipeline failure; receiving a changed portion of code under development at a particular stage of said continuous delivery pipeline; receiving one or more log files generated by one or more development tools involving said changed portion of code under development at said particular stage of said continuous delivery pipeline; receiving relationship information between entries in said one or more log files and said changed portion of code under development at said particular stage of continuous delivery pipeline from said machine learning model, wherein said relationship information comprises information pertaining to the behavior of said changed portion of code in connection with said particular stage of continuous delivery pipeline; and generating and displaying a message based on said received relationship information, wherein said message comprises a prediction or a recommendation concerning potential failures in said continuous delivery pipeline. 2. The computer program product as recited in claim 1 , wherein the program code further comprises the programming instructions for: receiving a list of development tools used in association with stages of said continuous delivery pipeline; monitoring web browsing performed by a plurality of users in producing software; and identifying at least one development tool used in association with said continuous delivery pipeline that is not included in said received list of development tools based on said monitoring of said web browsing performed by said plurality of users in producing software. 3. The computer program product as recited in claim 2 , wherein said stages of said continuous delivery pipeline comprise code, build, test and deploy. 4. The computer program product as recited in claim 2 , wherein the program code further comprises the programming instructions for: adding said identified at least one development tool to said list of development tools to form an updated list of development tools. 5. The computer program product as recited in claim 4 , wherein the program code further comprises the programming instructions for: receiving log files generated by one or more development tools listed in said updated list of development tools involving code under development at various stages of said continuous delivery pipeline. 6. The computer program product as recited in claim 5 , wherein the program code further comprises the programming instructions for: creating said machine learning model using said received log files. 7. The computer program product as recited in claim 1 , wherein said change to said portion of code under development is received at a first stage of said continuous delivery pipeline, wherein a log entry in a log file of said one or more log files is received at a second stage, wherein said first stage precedes said second stage. 8. The computer program product as recited in claim 1 , wherein said message is one of the following: a prediction of whether said changed portion of code will pass a quality test at a following stage, a prediction of whether a module of software will fail to run at a following stage, a prediction of whether a module of software will perform incorrectly at a following stage, and a recommendation to one of a plurality of users to change a different portion of code at a following stage, wherein said different portion of code being code other than said changed portion of code under development. 9. The computer program product as recited in claim 1 , wherein said changed portion of code under development comprises one of the following: an infrastructure code, an application code and a framework code. 10. The computer program product as recited in claim 1 , wherein said message is generated in one of the following environments: an integrated development environment and a text editor. 11. A system, comprising: a memory for storing a computer program for detecting potential failures in a continuous delivery pipeline; and a processor connected to the memory, wherein the processor is configured to execute the program instructions of the computer program comprising: creating a machine learning model to predict whether changed portions of code under development at various stages of said continuous delivery pipeline will result in a pipeline failure; receiving a changed portion of code under development at a particular stage of said continuous delivery pipeline; receiving one or more log files generated by one or more development tools involving said changed portion of code under development at said particular stage of said continuous delivery pipeline; receiving relationship information between entries in said one or more log files and said changed portion of code under development at said particular stage of continuous delivery pipeline from said machine learning model, wherein said relationship information comprises information pertaining to the behavior of said changed portion of code in connection with said particular stage of continuous delivery pipeline; and generating and displaying a message based on said received relationship information, wherein said message comprises a prediction or a recommendation concerning potential failures in said continuous delivery pipeline. 12. The system as recited in claim 11 , wherein the program instructions of the computer program further comprise: receiving a list of development tools used in association with stages of said continuous delivery pipeline; monitoring web browsing performed by a plurality of users in producing software; and identifying at least one development tool used in association with said continuous delivery pipeline that is not included in said received list of development tools based on said monitoring of said web browsing performed by said plurality of users in producing software. 13. The system as recited in claim 12 , wherein said stages of said continuous delivery pipeline comprise code, build, test and deploy. 14. The system as recited in claim 12 , wherein the program instructions of the computer program further comprise: adding said identified at least one development tool to said list of development tools to form an updated list of development tools. 15. The system as recited in claim 14 , wherein the program instructions of the computer program further comprise: receiving log files generated by one or more development tools listed in said updated list of development tools involving code under development at various stages of said continuous delivery pipeline. 16. The system as recited in claim 15 , wherein the program instructions of the computer program further comprise: creating said machine learning model using said received log files. 17. The system as recited in claim 11 , wherein said change to said portion of code under development is received at a first stage of said continuous delivery pipeline, wherein a log entry in a log file of said one or more log files is received at a second stage, wherein said first stage precedes said second stage. 18. The system as recited in claim 11 , wherein said mes
Environments for analysis, debugging or testing of software · CPC title
Software metrics · CPC title
Round-trip engineering · CPC title
Software deployment · CPC title
Reliability or availability analysis · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.