Intelligent management of software deployment based on code change

Patent metadata

Field	Value
Publication number	US-12093676-B2
Application number	US-202217575765-A
Country	US
Kind code	B2
Filing date	Jan 14, 2022
Priority date	Jan 14, 2022
Publication date	Sep 17, 2024
Grant date	Sep 17, 2024

Abstract

Automated management of software code change and deployment in an information processing system is disclosed. In one example, a method comprises the following steps. The method obtains one or more parameters specifying a software deployment following at least one code change to a set of one or more software programs. The method distinguishes first portions of the set of one or more software programs that are affected by the at least one code change from second portions of the set of one or more software programs that are unaffected by the at least one code change. The method generates at least one deployment script for causing deployment of the first portions of the set of one or more software programs without causing deployment of the second portions of the set of one or more software programs.

First claim

What is claimed is:

1. An apparatus comprising:
at least one processing device comprising a processor coupled to a memory, the at least one processing device, when executing program code, operates as a software deployment management engine configured to:
obtain one or more developer-defined parameters specifying a software deployment following at least one code change to a set of one or more software programs, the one or more developer-defined parameters specifying, for the set of one or more software programs, a target deployment and a type of deployment;
distinguish first portions of the set of one or more software programs that are affected by the at least one code change from second portions of the set of one or more software programs that are unaffected by the at least one code change;
generate one or more configuration files based on the one or more developer-defined parameters;
determine whether one or more dependency relationships associated with the at least one code change exist by detecting dependencies between the one or more configuration files and the set of one or more software programs based on commit data; and
generate at least one deployment script for causing deployment of the first portions of the set of one or more software programs without causing deployment of the second portions of the set of one or more software programs based at least in part on the detected dependencies.

2. The apparatus of claim 1 , wherein the software deployment management engine is further configured to cause performance of a code scanning process for processing the first portions of the set of one or more software programs to detect any vulnerabilities therein.

3. The apparatus of claim 2 , wherein the software deployment management engine is further configured to utilize a machine learning model to decide whether a result of the code scanning process is submitted for approval by an approver or is automatically approved.

4. The apparatus of claim 3 , wherein the software deployment management engine is further configured to train the machine learning model based on historical approval data.

5. The apparatus of claim 4 , wherein the software deployment management engine is further configured to train the machine learning model based on historical approval data using a binary classification algorithm.

6. The apparatus of claim 5 , wherein the software deployment management engine is further configured to utilize the trained machine learning model to pass or fail the at least one deployment script.

7. The apparatus of claim 6 , wherein the software deployment management engine is further configured to pass or fail the at least one deployment script based on a severity of any vulnerability detected.

8. The apparatus of claim 7 , wherein the software deployment management engine is further configured to pass or fail the at least one deployment script based on an error threshold.

9. The apparatus of claim 1 , wherein a current commit is compared to a previous commit to identify which portions of the set of one or more software programs are the first portions and which are the second portions.

10. A method comprising:
obtaining, via a software deployment management engine, one or more developer-defined parameters specifying a software deployment following at least one code change to a set of one or more software programs, the one or more developer-defined parameters specifying, for the set of one or more software programs, a target deployment and a type of deployment;
distinguishing, via the software deployment management engine, first portions of the set of one or more software programs that are affected by the at least one code change from second portions of the set of one or more software programs that are unaffected by the at least one code change;
generating one or more configuration files based on the one or more developer-defined parameters;
determining whether one or more dependency relationships associated with the at least one code change exist by detecting dependencies between the one or more configuration files and the set of one or more software programs based on commit data; and
generating, via the software deployment management engine, at least one deployment script for causing deployment of the first portions of the set of one or more software programs without causing deployment of the second portions of the set of one or more software programs based at least in part on the detected dependencies.

11. The method of claim 10 , further comprising causing performance of a code scanning process for processing the first portions of the set of one or more software programs to detect any vulnerabilities therein.

12. The method of claim 11 , further comprising utilizing a machine learning model to decide whether a result of the code scanning process is submitted for approval by an approver or is automatically approved.

13. The method of claim 12 , further comprising training the machine learning model based on historical approval data.

14. The method of claim 13 , further comprising training the machine learning model based on historical approval data using a binary classification algorithm.

15. The method of claim 14 , further comprising utilizing the trained machine learning model to pass or fail the at least one deployment script.

16. The method of claim 15 , further comprising passing or failing the at least one deployment script based on a severity of any vulnerability detected.

17. The method of claim 16 , further comprising passing or failing the at least one deployment script based on an error threshold.

18. The method of claim 10 , wherein a current commit is compared to a previous commit to identify which portions of the set of one or more software programs are the first portions and which are the second portions.

19. A computer program product comprising a non-transitory processor-readable storage medium having stored therein program code of one or more software programs, wherein the program code when executed by at least one processing device cause the at least one processing device to operate as a software deployment management engine configured to:
obtain one or more developer-defined parameters specifying a software deployment following at least one code change to a set of one or more software programs, the one or more developer-defined parameters specifying, for the set of one or more software programs, a target deployment and a type of deployment;
distinguish first portions of the set of one or more software programs that are affected by the at least one code change from second portions of the set of one or more software programs that are unaffected by the at least one code change;
generate one or more configuration files based on the one or more developer-defined parameters;
determine whether one or more dependency relationships associated with the at least one code change exist by detecting dependencies between the one or more configuration files and the set of one or more software programs based on commit data; and
generate at least one deployment script for causing deployment of the first portions of the set of one or more software programs without causing deployment of the second portions of the set of one or more software programs based at least in part on the detected dependencies.

20. The computer program product of claim 19 , wherein a current commit is compared to a previous commit to identify which portions of the set of one or more software programs are the first portions and which ar

Assignees

• Dell Products Lp

Inventors

• Basu Rangan
• Gosain Rohit
• Panikkar Shibi
• Kumar Anup

Classifications

• G06F21/577 Primary

  Assessing vulnerabilities and evaluating computer system security · CPC title

• G06N5/022

  Knowledge engineering; Knowledge acquisition · CPC title

• G06F2221/033

  Test or assess software · CPC title

• G06F8/65 Primary

  Updates (security arrangements therefor G06F21/57) · CPC title

• G06F8/60

  Software deployment · CPC title