Grouping and isolating software changes to increase build quality

Patent metadata

Field	Value
Publication number	US-10545847-B2
Application number	US-201615265873-A
Country	US
Kind code	B2
Filing date	Sep 15, 2016
Priority date	Sep 15, 2016
Publication date	Jan 28, 2020
Grant date	Jan 28, 2020

Abstract

A method for assessing a quality of a plurality of changes to a plurality of source code is provided. The method may include receiving the plurality of source code for a software product, whereby the received plurality of source code includes the plurality of changes. The method may also include identifying at least one property associated with each of the plurality of changes within the received plurality of source code. The method may further include determining a confidence level for each of the plurality of changes based on the at least one identified property associated with each of the plurality of changes and a plurality of historical software build data. The method may also include assigning each of the plurality of changes to a build group based on the determined confidence level. The method may further include executing the build group in a software build.

First claim

What is claimed is:

1. A processor-implemented method for assessing a quality of a plurality of changes to a plurality of source code, the method comprising:
receiving, by a processor, the plurality of source code for a software product, wherein the received plurality of source code includes the plurality of changes;
identifying a plurality of properties associated with each of the plurality of changes within the received plurality of source code;
determining a confidence level for each of the plurality of changes based on the plurality of identified properties associated with each of the plurality of changes and a plurality of historical software build data;
grouping together each of the plurality of changes to one of a plurality of build groups based on the determined confidence level, identified properties known to have a positive influence on a build quality, identified properties known to have a negative impact on the build quality, and environment inputs, wherein assigning each of the plurality of changes to the build group includes isolating a change within the plurality of changes where the determined confidence level for the change falls below a user preconfigured isolation threshold, wherein the environmental inputs comprise a number of current changes and a build duration, wherein the positive influence and negative impact on the build quality is determined based on historical software build data of properties similar to the identified properties;
executing, simultaneously, a validation test of each build group of changes in a software build;
in response to a validation test of a build group failing, isolating each source code change into individual build groups; and
executing a validation test of each individual build group.

2. The method of claim 1 , wherein assigning each of the plurality of changes further comprises:
assigning each of the plurality of changes to the build group based on a plurality of preconfigured rules.

3. The method of claim 1 , wherein the plurality of properties comprises a change size, a change author, a reviewer name, a change type, a check-in date, a check-in time, and a plurality of parts of the received plurality of source code affected by the plurality of changes.

4. The method of claim 1 , wherein the plurality of historical software build data is selected from a group consisting of a plurality of previous changes and a plurality of properties associated with the plurality of previous changes.

5. The method of claim 1 , further comprising:
recording each of the plurality of changes, the plurality of properties, and the determined confidence level in a data repository to be included with the plurality of historical software build data.

6. The method of claim 1 , wherein assigning each of the plurality of changes to the build group includes grouping together at least one change within the plurality of changes where the determined confidence level for each at least one change satisfies a user preconfigured grouping threshold.

7. A computer system for assessing a quality of a plurality of changes to a plurality of source code, the computer system comprising:
one or more processors, one or more computer-readable memories, one or more computer-readable tangible storage medium, and program instructions stored on at least one of the one or more tangible storage medium for execution by at least one of the one or more processors via at least one of the one or more memories, wherein the computer system is capable of performing a method comprising:
receiving the plurality of source code for a software product, wherein the received plurality of source code includes the plurality of changes;
identifying a plurality of properties associated with each of the plurality of changes within the received plurality of source code;
determining a confidence level for each of the plurality of changes based on the plurality of identified properties associated with each of the plurality of changes and a plurality of historical software build data;
grouping together each of the plurality of changes to one of a plurality of build groups based on the determined confidence level, identified properties known to have a positive influence on a build quality, identified properties known to have a negative impact on the build quality, and environment inputs, wherein assigning each of the plurality of changes to the build group includes isolating a change within the plurality of changes where the determined confidence level for the change falls below a user preconfigured isolation threshold, wherein the environmental inputs comprise a number of current changes and a build duration, wherein the positive influence and negative impact on the build quality is determined based on historical software build data of properties similar to the identified properties;
executing, simultaneously, a validation test of each build group of changes in a software build;
in response to a validation test of a build group failing, isolating each source code change into individual build groups; and
executing a validation test of each individual build group.

8. The computer system of claim 7 , wherein assigning each of the plurality of changes further comprises:
assigning each of the plurality of changes to the build group based on a plurality of preconfigured rules.

9. The computer system of claim 7 , wherein the plurality of properties comprises a change size, a change author, a reviewer name, a change type, a check-in date, a check-in time, and a plurality of parts of the received plurality of source code affected by the plurality of changes.

10. The computer system of claim 7 , wherein the plurality of historical software build data is selected from a group consisting of a plurality of previous changes and a plurality of properties associated with the plurality of previous changes.

11. The computer system of claim 7 , further comprising:
recording each of the plurality of changes, the plurality of properties, and the determined confidence level in a data repository to be included with the plurality of historical software build data.

12. The computer system of claim 7 , wherein assigning each of the plurality of changes to the build group includes grouping together at least one change within the plurality of changes where the determined confidence level for each at least one change satisfies a user preconfigured grouping threshold.

13. A computer program product for assessing a quality of a plurality of changes to a plurality of source code, the computer program product comprising:
one or more computer-readable storage medium and program instructions stored on at least one of the one or more storage medium, the program instructions executable by a processor, the program instructions comprising:
program instructions to receive the plurality of source code for a software product, wherein the received plurality of source code includes the plurality of changes;
program instructions to identify a plurality of properties associated with each of the plurality of changes within the received plurality of source code;
program instructions to determine a confidence level for each of the plurality of changes based on the plurality of identified properties associated with each of the plurality of changes and a plurality of historical software build data;
program instructions to group together each of the plurality of changes to one of a plurality of build groups based on the determined confidence level, identified properties known to have a positive influence on a build quality, identified properties known to have a negative impact on the build quality, and environ

Assignees

• IBM

Inventors

• Broadbent Peter R
• Janssen Roy
• Pisters Ramon L H
• Tange Leendert P

Classifications

• G06F11/3604 Primary

  Analysis of software for verifying properties of programs (testing of software G06F11/3668) · CPC title

• G06F11/36 Primary

  Prevention of errors by analysis, debugging or testing of software · CPC title