Controlling repetitive check-in of intermediate versions of source code from a developer's computer to a source code repository

• US 9,672,031 B2
• Filed: 09/01/2015
• Issued: 06/06/2017
• Est. Priority Date: 09/01/2015
• Status: Active Grant

• Current Assignee: CA, Inc. (d/b/a CA Technologies) (Broadcom, Inc.)
• Original Assignee: CA, Inc. (d/b/a CA Technologies) (Broadcom, Inc.)
• Inventors: Agrawal, Ganesh Prasad
• Primary Examiner(s): Dao, Thuy
• Assistant Examiner(s): Nguyen, Mongbao
• Application Number:
  US14/842,282
• Publication Number:
  US 20170060575A1
• Time in Patent Office: 644 Days
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 8/70 Software maintenance or management
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06F 8/75 Structural analysis for program understanding
• CPC Class Codes: G06F 8/77 Software metrics

Abstract

A repository control computer checks-out source code from a source code repository to a local memory of a developer'"'"'s computer responsive to receiving a developer initiated check-out message. The control computer repetitively checks-in intermediate versions of the source code from the local memory of the developer'"'"'s computer to the source code repository responsive to corresponding occurrences of a condition defined by a rule being satisfied. The control computer checks-in a final version of the source code from the local memory of the developer'"'"'s computer to the source code repository responsive to receiving a developer initiated check-in message.

Claims

1. A computer-implemented method comprising:

performing operations by a processor of a repository control computer;

checking-out source code from a source code repository to a local memory of a developer'"'"'s computer responsive to receiving a developer initiated check-out message;

repetitively checking-in intermediate versions of the source code from the local memory of the developer'"'"'s computer to the source code repository responsive to corresponding occurrences of a condition defined by a rule being satisfied;

checking-in a final version of the source code from the local memory of the developer'"'"'s computer to the source code repository responsive to receiving a developer initiated check-in message;

generating a report containing a metric indicating progress of development of the source code in the local memory of the developer'"'"'s computer, responsive to the checking-in of one of the intermediate versions of the source code from the local memory of the developer'"'"'s computer to the source code repository;

identifying a group of other developers'"'"' computers which are responsible for development of other source codes that are related to the source code, comprising;

checking-in an intermediate version of another source code from a local memory of another developer'"'"'s computer to the source code repository;

determining that the another source code is newly related to the source code based on identifying that the intermediate version of the another source code operationally calls the source code and that a previous intermediate version of the another source code checked-in to the source code repository did not operationally call the source code; and

adding the another developer'"'"'s computer to the group of other developers'"'"' computers based on the determination that the another source code is newly related to the source code; and

communicating the report to the group of other developer'"'"'s computers.

2. The method of claim 1, wherein the repetitively checking-in intermediate versions of the source code from the local memory of the developer'"'"'s computer to the source code repository responsive to corresponding occurrences of a condition defined by a rule being satisfied, comprises:

checking-in a present intermediate version of the source code from the local memory of the developer'"'"'s computer to the source code repository responsive to each occurrence of a threshold elapsed time since a previous intermediate version of the source code was checked-in from the local memory of the developer'"'"'s computer to the source code repository.

3. The method of claim 2, further comprising:

identifying differences between the previous intermediate version of the source code of the developer'"'"'s computer that was checked-in to the source code repository and the present intermediate version of the source code of the developer'"'"'s computer checked-in to the source code repository; and

controlling the threshold elapsed time based on the differences.

4. The method of claim 3, further comprising:

changing the threshold elapsed time based on differences identified in executable portions of the source code of the developer'"'"'s computer and based on differences identified in non-executable portions of the source code of the developer'"'"'s computer, wherein the threshold elapsed time is changed by a greater amount responsive to an amount of the differences identified in the executable portions of the source code of the developer'"'"'s computer and by a lesser amount responsive to an amount of the differences identified in the non-executable portions of the source code of the developer'"'"'s computer.

5. The method of claim 2, further comprising:

identifying a number of developers tracking progress of development of the intermediate versions of the source code of the developer'"'"'s computer checked-in to the source code repository; and

controlling the threshold elapsed time based on the number of developers.

6. The method of claim 2, further comprising:

identifying a number of other source codes that are configured to operationally call the source code of the developer'"'"'s computer; and

controlling the threshold elapsed time based on the number of other source codes.

7. The method of claim 6, further comprising:

identifying a rate of development change of the other source codes that are configured to operationally call the source code of the developer'"'"'s computer; and

controlling the threshold elapsed time based on the number of other source codes and the rate of development change of the other source codes.

8. The method of claim 1, wherein the repetitively checking-in intermediate versions of the source code from the local memory of the developer'"'"'s computer to the source code repository responsive to each occurrence of a condition defined by a rule being satisfied, comprises:

identifying differences between a previous intermediate version of the source code that has been checked-in from the local memory of the developer'"'"'s computer to the source code repository and a present intermediate version of the source code in the local memory of the developer'"'"'s computer; and

checking-in the present intermediate version of the source code from the local memory of the developer'"'"'s computer to the source code repository responsive to the differences that are identified satisfying a threshold difference defined by the rule.

9. The method of claim 1, further comprising:

comparing the one of the intermediate versions of the source code of the developer'"'"'s computer checked-in to the source code repository to a previous one of the intermediate versions of the source code of the developer'"'"'s computer checked-in to the source code repository; and

generating the metric based on the comparison.

10. The method of claim 9, wherein the comparing the one of the intermediate versions of the source code of the developer'"'"'s computer checked-in to the source code repository to a previous one of the intermediate versions of the source code of the developer'"'"'s computer checked-in to the source code repository, comprises:

identifying differences between executable portions of the one of the intermediate versions of the source code of the developer'"'"'s computer and executable portions of the previous one of the intermediate versions of the source code of the developer'"'"'s computer; and

generating the metric based on an amount of the differences.

11. The method of claim 1, further comprising:

counting a number of the intermediate versions of the source code checked-in from the local memory of the developer'"'"'s computer to the source code repository; and

generating the metric based on the number of the intermediate versions.

12. The method of claim 1, further comprising:

communicating the report to a social media server for publishing to the group of other developers'"'"' computers tracking publishing of the reports through the social media server.

13. The method of claim 12, wherein the communicating the report to a social media server for publishing to the group of other developers'"'"' computers tracking publishing of the reports through the social media server, comprises:

generating a keyword based on content of an application programming interface (API) of the one of the intermediate versions of the source code of the developer'"'"'s computer; and

posting the report to the social media server with the keyword for tracking by the group of other developers'"'"' computers.

14. The method of claim 13, wherein the generating a keyword based on content of an application programming interface (API) of the one of the intermediate versions of the source code of the developer'"'"'s computer, comprises:

selecting the keyword from among a plurality of defined keywords which are separately tracked by different groups of developers'"'"' computers, based on a determined functionality of the API of the one of the intermediate versions of the source code.

15. The method of claim 1, wherein the identifying a group of other developers'"'"' computers which are responsible for development of other source codes that are related to the source code, comprises:

checking-in another intermediate version of the another source code from the local memory of the another developer'"'"'s computer to the source code repository;

determining that the another source code has ceased being related to the source code based on identifying that the another intermediate version of the another source code no longer operationally calls the source code; and

removing the another developer'"'"'s computer from the group of other developers'"'"' computers based on the determination that the another source code has ceased being related to the source code.

16. A computer program product, comprising:

a non-transitory computer readable storage medium comprising computer readable program code embodied in the medium that when executed by a processor of a repository control computer causes the processor to perform operations comprising;

checking-out source code from a source code repository to a local memory of a developer'"'"'s computer responsive to receiving a developer initiated check-out message;

repetitively checking-in intermediate versions of the source code from the local memory of the developer'"'"'s computer to the source code repository responsive to corresponding occurrences of a condition defined by a rule being satisfied;

checking-in a final version of the source code from the local memory of the developer'"'"'s computer to the source code repository responsive to receiving a developer initiated check-in message;

generating a report containing a metric indicating progress of development of the source code in the local memory of the developer'"'"'s computer, responsive to the checking-in of one of the intermediate versions of the source code from the local memory of the developer'"'"'s computer to the source code repository;

identifying a group of other developers'"'"' computers which are responsible for development of other source codes that are related to the source code, comprising;

checking-in an intermediate version of another source code from a local memory of another developer'"'"'s computer to the source code repository;

determining that the another source code is newly related to the source code based on identifying that the intermediate version of the another source code operationally calls the source code and that a previous intermediate version of the another source code checked-in to the source code repository did not operationally call the source code; and

adding the another developer'"'"'s computer to the group of other developers'"'"' computers based on the determination that the another source code is newly related to the source code; and

communicating the report to the group of other developer'"'"'s computers.

17. The computer program product of claim 16, wherein:

identifying a group of other developers'"'"' computers which are responsible for development of other source codes that are related to the source code, further comprises;

checking-in another intermediate version of the another source code from the local memory of the another developer'"'"'s computer to the source code repository;

determining that the another source code has ceased being related to the source code based on identifying that the another intermediate version of the another source code no longer operationally calls the source code; and

removing the another developer'"'"'s computer from the group of other developers'"'"' computers based on the determination that the another source code has ceased being related to the source code.