VERSION NUMBERING IN SINGLE DEVELOPMENT AND TEST ENVIRONMENT

• US 20130174124A1
• Filed: 12/29/2011
• Published: 07/04/2013
• Est. Priority Date: 12/29/2011
• Status: Abandoned Application

• Current Assignee: Unisys Corporation
• Original Assignee: Unisys Corporation
• Inventors: Watters, Christina, Johnson, Peter
• Application Number:
  US13/339,906
• Publication Number:
  US 20130174124A1
• Time in Patent Office: Days
• US Class Current: 717/122
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

System and method for version string generation for artifacts in a repository is disclosed. A first source code management server manages first source code versions in a first repository and assigns a first source code version string to each first source code version. A first artifact repository comprises a first artifact built based on one of the first source code versions. A product manager generates a first artifact version string for the first artifact based on the first source code version string of the first source code version used to build the first artifact.

Claims

1. A system for version string generation for artifacts in a repository comprising:

a first source code management server that manages first source code versions in a first repository and assigns a first source code version string to each first source code version;

a first artifact repository that comprises a first artifact built based on one of the first source code versions; and

a build manager that generates a first artifact version string for the first artifact based on the first source code version string of the first source code version used to build the first artifact and based on a tag word.

2. The system according to claim 1, wherein the build manager is adapted to generate the first artifact version string by concatenating a predetermined product version string with the first source code version string.

3. The system according to claim 2, wherein the build manager is adapted to generate the first artifact version number by concatenating a delimiter between the predetermined product version number and the first source code version number.

4. The system according to claim 2, wherein the build manager is adapted to generate the first artifact version number by placing the predetermined product version string before the first source code version number.

5. The system according to claim 1, the system further comprising:

a second source code management server that manages second source code versions in a second repository and assigns a second source code version number to each second source code version;

the artifact built further based on one of the second source code versions; and

the build manager generates the first artifact version number to the first artifact further based on the second source code version number of the second source code version used to build the first artifact.

6. The system according to claim 1, the system further comprising:

a second artifact repository that comprises a second artifact with a second artifact version number;

the first artifact built further based on the second artifact; and

the build manager generates the first artifact version number for the first artifact further based on the second artifact version number of the second artifact used to build the first artifact.

7. The system according to claim 6, wherein the build manager is adapted to generate the first artifact version string by concatenating a predetermined product version string with the first source code version string and the second artifact version string.

8. A method for version string generation for artifacts in a repository comprising:

a first source code management server assigning a first source code version string to each first source code version committed to a first source code repository;

a build manager building a first artifact based on one of the first source code versions; and

the build manager generating a first artifact version string for the first artifact based on the first source code version string of the first source code version used to build the first artifact and based on a tag word.

9. The method according to claim 8, the build manager generating the first artifact version string by concatenating a predetermined product version string with the first source code version string.

10. The method according to claim 9, the build manager generating the first artifact version string by concatenating a period between the predetermined product version string and the first source code version string.

11. The method according to claim 9, the build manager generating the first artifact version string by placing the predetermined product version string before the first source code version string.

12. The method according to claim 8, further comprising:

a second source code management server assigning a second source code version string to each second source code version committed to a second repository;

the build manager building the first artifact further based on one of the second source code versions; and

the build manager generating the first artifact version string for the first artifact further based on the second source code version string of the second source code version used to build the first artifact.

13. The method according to claim 8, further comprising:

a second artifact repository storing a second artifact with a second artifact version string;

the build manager further building the first artifact from the second artifact; and

the build manager generating the first artifact version string for the first artifact further based on the second artifact version string.

14. The method according to claim 13, the build manager generating the first artifact version string by concatenating a predetermined product version string with the first source code version string and the second artifact version string.

15. A machine-readable tangible and non-transitory medium with information recorded thereon, wherein the information, when read by a machine, causes the machine to perform the following steps:

assign, by a first source code management server, a first source code version string to each first source code version committed to a first source code repository;

build, by a build manager, first artifacts from a one of the first source code versions; and

generate, by the build manager, a first artifact version string for the first artifact based on the first source code version string of the first source code version used to build the first artifact and based on a tag word.

16. The machine-readable medium according to claim 15, the build manager generating the first artifact version string by concatenating a predetermined product version string with the first source code version string.

17. The machine-readable medium according to claim 16, the build manager generating the first artifact version string by concatenating a period between the predetermined product version string and the first source code version string.

18. The machine-readable medium according to claim 16, the build manager generating the first artifact version string by placing the predetermined product version string before the first source code version string.

19. The machine-readable medium according to claim 15, wherein the information further causes the machine to perform the following steps:

assign, by a second source code management server, a second source code version string to each second source code version committed to a second repository;

build, by the build manager, the first artifact further based on one of the second source code versions; and

generate, by the build manager, the first artifact version string for the first artifact further based on the second source code version string of the second source code version used to build the first artifact.

20. The machine-readable medium according to claim 15, wherein the information further causes the machine to perform the following steps:

store, by a second artifact repository, a second artifact with a second artifact version string;

build, by the build manager, the first artifact further based on the second artifact; and

generate, by the build manager, the first artifact version string for the first artifact further based on the second artifact version string.