Automated hotfix handling model

A hotfix handling system comprising:

• a computer processor;
• a memory storing instructions that when executed by the computer processor cause the computer processor to perform acts comprising:
• receiving defects submitted to a defect repository, wherein each of the defects is associated with an identifier, a status and a keyword indicating the type of the defect;
• querying the defect repository to obtain a list of cumulative hotfix candidates based on a set of rules and the keyword associated with each of the defects, wherein the list of cumulative hotfix candidates includes one or more defects from the defect repository;
• storing the list of cumulative hotfix candidates in the defect repository;
• approving the list of cumulative hotfix candidates, associating the list of cumulative hotfix candidates to a version;
• receiving and storing check-in data corresponding to the list of cumulative hotfix candidates to a source code repository;
• approving the check-in data, and triggering an automated compiling of at least one build using the check-in data stored in the source code repository, wherein the at least one build is associated with the version;
• upon completion of the build, examining the at least one build;
• triggering an automated testing of the at least one build based on a determination that the at least one build is clean, wherein the automated testing uses test cases mapped to the version associated with the at least one build;
• storing the at least one build in a build repository;
• and
• publishing a cumulative hotfix based on the at least one build stored in the build repository, and sending an automated notification of the cumulative hotfix.

A computer program product comprising a non-transitory computer usable medium having machine readable code embodied therein for:

• receiving defects submitted to a defect repository, wherein each of the defects is associated with an identifier, a status and a keyword indicating the type of the defect;
• querying the defect repository to obtain a list of cumulative hotfix candidates based on a set of rules and the keyword associated with each of the defects, wherein the list of cumulative hotfix candidates includes one or more defects from the defect repository;
• storing the list of cumulative hotfix candidates in the defect repository;
• approving the list of cumulative hotfix candidates, associating the list of cumulative hotfix candidates to a version;
• receiving and storing check-in data corresponding to the list of cumulative hotfix candidates to a source code repository;
• approving the check-in data, and triggering an automated compiling of at least one build using the check-in data stored in the source code repository, wherein the at least one build is associated with the version;
• upon completion of the build, examining the at least one build;
• triggering an automated testing of the at least one build based on a determination that the at least one build is clean, wherein the automated testing uses test cases mapped to the version associated with the at least one build;
• storing the at least one build in a build repository;
• and
• publishing a cumulative hotfix based on the at least one build stored in the build repository, and sending an automated notification of the cumulative hotfix.