Method and system for evaluating a software artifact based on issue tracking and source control information
First Claim
1. A computer system, comprising:
- a transceiver operable to transmit and receive communications over at least a portion of a network; and
a processor cooperatively operable with the transceiver, and configured so that the processor;
obtains a URL for an issue tracking storage system and a URL for a location of a source code management storage system;
gathers, by communication over the transceiver, (i) from the URL of the issue tracking storage system, issue tracking information stored in the issue tracking storage system, the issue tracking information having a history of issues filed against a plurality of artifacts, and (ii) from the URL of the source code management storage system, source code management information stored in the source code management storage system, the source code management information having a history of code changes committed against another plurality of artifacts;
determines a history of the issue tracking information for a history of issues which are targeted to a single artifact, and determines the source code management information for a history of commits and corresponding source code changes which are committed against the single artifact;
provides an interpretation of the current state of the single artifact based on the history of the issue tracking information targeted to this single artifact and the history from the source code management information committed against the single artifact;
wherein the interpretation of the current state by the processor is an evaluation of the current stability, so that the processor further determines a stability of the single artifact from a periodicity of releases of the single artifact in the source code management information and a volume and severity of issues reported for the single artifact in the issue tracking information, whereinthe single artifact is determined to be stable when the single artifact has regular periodic releases and fewer than a first predetermined number of severe issues, andthe single artifact is determined to be not stable when the single artifact has more than a second predetermined number of severe issues, the second predetermined number being more than the first predetermined number.
2 Assignments
0 Petitions
Accused Products
Abstract
A computer system includes a transceiver and a processor that is cooperatively operable with the transceiver. The processor gathers, over the transceiver, (i) issue tracking information stored in an issue tracking storage system, the issue tracking information having a history of issues filed against a plurality of artifacts, and (ii) source code management information stored in a source code management storage system, the source code management information having a history of code changes committed against another plurality of artifacts. The processor checks a combined history of the issue tracking information and the source code management information for a history of issues filed against an artifact and a history of commits and corresponding source code changes committed against the artifact. The processor provides an interpretation of the current state of the artifact based on the combined history of the issue tracking information and source code management information about the artifact.
-
Citations
18 Claims
-
1. A computer system, comprising:
-
a transceiver operable to transmit and receive communications over at least a portion of a network; and a processor cooperatively operable with the transceiver, and configured so that the processor; obtains a URL for an issue tracking storage system and a URL for a location of a source code management storage system; gathers, by communication over the transceiver, (i) from the URL of the issue tracking storage system, issue tracking information stored in the issue tracking storage system, the issue tracking information having a history of issues filed against a plurality of artifacts, and (ii) from the URL of the source code management storage system, source code management information stored in the source code management storage system, the source code management information having a history of code changes committed against another plurality of artifacts; determines a history of the issue tracking information for a history of issues which are targeted to a single artifact, and determines the source code management information for a history of commits and corresponding source code changes which are committed against the single artifact; provides an interpretation of the current state of the single artifact based on the history of the issue tracking information targeted to this single artifact and the history from the source code management information committed against the single artifact; wherein the interpretation of the current state by the processor is an evaluation of the current stability, so that the processor further determines a stability of the single artifact from a periodicity of releases of the single artifact in the source code management information and a volume and severity of issues reported for the single artifact in the issue tracking information, wherein the single artifact is determined to be stable when the single artifact has regular periodic releases and fewer than a first predetermined number of severe issues, and the single artifact is determined to be not stable when the single artifact has more than a second predetermined number of severe issues, the second predetermined number being more than the first predetermined number. - View Dependent Claims (2, 3, 4, 5, 6)
-
-
7. A computer-implemented method for evaluating a software artifact, comprising:
-
obtaining, by a processor, a URL for an issue tracking storage system and a URL for a location of a source code management storage system; gathering, in the processor by communication over a transceiver, (i) from the URL of the issue tracking storage system, issue tracking information stored in the issue tracking storage system, the issue tracking information having a history of issues filed against a plurality of artifacts, and (ii) from the URL of the source code management storage system, source code management information stored in the source code management storage system, the source code management information having a history of code changes committed against another plurality of artifacts; determining a history of the issue tracking information for a history of issues which are targeted to a single artifact, and determines the source code management information for a history of commits and corresponding source code changes which are committed against the single artifact; providing an interpretation of the current state of the single artifact based on the history of the issue tracking information targeted to the single artifact and the history from source code management information committed against the single artifact; wherein the interpretation of the current state is an evaluation of the current stability further comprising determining a stability of the single artifact from a periodicity of releases of the single artifact in the source code management information and a volume and severity of issues reported for the single artifact in the issue tracking information, wherein the single artifact is determined to be stable when the single artifact has regular periodic releases and fewer than a first predetermined number of severe issues, and the single artifact is determined to be not stable when the single artifact has more than a second predetermined number of severe issues, the second predetermined number being more than the first predetermined number. - View Dependent Claims (8, 9, 10, 11, 12)
-
-
13. A non-transitory computer-readable medium comprising instructions for execution by a computer, the instructions including a computer-implemented method for evaluating a software artifact, the instructions for implementing:
-
obtaining, by a processor, a URL for an issue tracking storage system and a URL for a location of a source code management storage system; gathering, in the processor by communication over a transceiver, (i) from the URL of the issue tracking storage system, issue tracking information stored in the issue tracking storage system, the issue tracking information having a history of issues filed against a plurality of artifacts, and (ii) from the URL of the source code management storage system, source code management information stored in the source code management storage system, the source code management information having a history of code changes committed against another plurality of artifacts; determining a history of the issue tracking information for a history of issues which are relevant to a single artifact, and determining the source code management information for a history of commits and corresponding source code changes which are committed against the single artifact; providing an interpretation of the current state of the single artifact based on the history of the issue tracking information targeted to the single artifact and the history from the source code management information committed against the single artifact; wherein the interpretation of the current state is an evaluation of the current stability further comprising instructions for determining a stability of the single artifact from a periodicity of releases of the single artifact in the source code management information and a volume and severity of issues reported for the single artifact in the issue tracking information, wherein the single artifact is determined to be stable when the single artifact has regular periodic releases and fewer than a first predetermined number of severe issues, and the single artifact is determined to be not stable when the single artifact has more than a second predetermined number of severe issues, the second predetermined number being more than the first predetermined number. - View Dependent Claims (14, 15, 16, 17, 18)
-
Specification