Version management systems, methods, and interfaces
AssigneeMastercard International Incorporated
InventorsMelissa Niswonger, Juan Alejandro Gallegos
Life of this patent
Estimating the term…
Abstract
A version management system can manage a set of application programming interface (API) calls to different software file case systems including a first software file case system and a second software file case system. In response to certain commands and functionality, the version management system obtains from the set of API calls to the different software file case systems, existence request rules corresponding to the first software file case system and the second software file case system so as to perform an existence check. In addition, the version management system enables version records to be set that have a first version number, a first software file case name, a second software file case name, environment name, and phase name.
Claims20
A method, comprising:
- managing, at a version management system, a set of application programming interface (API) calls to different software file case systems including a first software file case system and a second software file case system;
- receiving a version setting request for a version-pair entry, wherein the version-pair entry comprises:
- a first software file case name that is associated with a first software file case generated at the first software file case system and a second software file case name that is associated with a second software file case generated at the second software file case system;
- obtaining, from the set of API calls to the different software file case systems, a first set of existence request rules corresponding to the first software file case system and a second set of existence request rules corresponding to the second software file case system;
- generating a first existence request based on the first set of existence request rules, wherein the first existence request comprises the first software file case name;
- sending the first existence request to the first software file case system;
- receiving, from the corresponding first software file case system, a first positive response, the first positive response indicating that the first software file case exists at the first software file case system;
- generating a second existence request based on the second set of existence request rules, wherein the second existence request comprises the second software file case name;
- sending the second existence request to the second software file case system;
- receiving, from the second corresponding software file case system, a second positive response, the second positive response indicating that the second software file case exists at the second software file case system;
- and
- upon receiving both the first positive response and the second positive response, setting a first version record with a first version number at the version management system, wherein the first version record comprises first version record attributes of the version-pair entry.
A computer-readable storage medium having instructions stored thereon that when executed by a computing system, direct the computing system to:
- manage a set of application programming interface (API) calls to different software file case systems including a first software file case system and a second software file case system;
- create a version-pair entry, wherein instructions to create the version-pair entry direct the computing system to:
- receive a version-pair creation request, the version-pair creation request comprising a first software file case name that is associated with a first software file case generated at the first software file case system and a second software file case name that is associated with a second software file case generated at the second software file case system;
- check that each software file case, including the first software file case and the second software file case, exists;
- and
- create the version-pair entry for the first software file case name and the second software file case name, wherein the version-pair entry indicates that the first software file case is associated with the second software file case;
- receive a version setting request for the version-pair entry;
- obtain, from the set of API calls to the different software file case systems, a first set of existence request rules corresponding to the first software file case system and a second set of existence request rules corresponding to the second software file case system;
- generate a first existence request based on the first set of existence request rules, wherein the first existence request comprises the first software file case name;
- send the first existence request to the first software file case system;
- receive, from the first software file case system, a first positive response, the first positive response indicating that the first software file case exists at the first software file case system;
- generate a second existence request based on the second set of existence request rules, wherein the second existence request comprises the second software file case name;
- send the second existence request to the second software file case system;
- receive, from the second software file case system, a second positive response, the second positive response indicating that the second software file case exists at the second software file case system;
- and
- upon receipt of both the first positive response and the second positive response, set a first version record with a first version number at a version management system, wherein the first version record comprises first version record attributes of the version-pair entry.
Dependencies are inferred from the claim text.