Software configuration control wherein containers are associated with physical storage of software application versions in a software production landscape

• US 8,776,020 B2
• Filed: 12/11/2008
• Issued: 07/08/2014
• Est. Priority Date: 12/11/2008
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Kramer, Wolfram, Krueger, Uwe
• Primary Examiner(s): Rampuria, Satish
• Application Number:
  US12/332,626
• Publication Number:
  US 20100153917A1
• Time in Patent Office: 2,035 Days
• Field of Search: 717/109, 717121-167, 709/208, 709/218, 709/232, 709/244, 711/160, 711/163, 711/201
• US Class Current: 717/121
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

According to some embodiments, a source version of a software product may be established in connection with a software production landscape. A first container, representing a first uniquely addressable physical location in the software production landscape, may then be associated with the source version. An executable derivative version of the software product may be built from the source version, and a second container, representing a second uniquely addressable physical location in the software production landscape, may be associated with the executable derivative version. Software configuration information may then be automatically provided to a user based at least in part on a relationship between the first and second containers at a given point in time.

Claims

1. A method associated with a software production landscape, comprising:

establishing a source version of a software product;

associating a first container, representing a first uniquely addressable physical location in the software production landscape, with the source version;

building an executable derivative version of the software product from the source version;

associating a second container, representing a second uniquely addressable physical location in the software production landscape, with the executable derivative version; and

automatically providing, to a user, software configuration information based at least in part on a relationship between the first and second containers at a given point in time;

wherein the source version is a first portion of source code created at a first development branch,

the method further comprising;

creating a second portion of source code at a second development branch; and

associating a third container, representing a third uniquely addressable physical location in the software production landscape, with the second portion of source code;

wherein the building an executable derivative version of the software product from the source version comprises;

building the executable derivative version of the software product from the first portion of source code that is associated with the first container and the second portion of source code that is associated with the third container;

the method further comprising;

installing the executable derivative version of the software product in a testing environment;

associating a fourth container, representing a fourth uniquely addressable physical location in the software production landscape, with the executable derivative version installed in the testing environment;

receiving, via a graphical user interface, input indicating selection of the fourth container that represents the fourth uniquely addressable physical location in the software production landscape and is associated with the executable derivative version installed in the testing environment; and

after receiving the input indicating the selection of the fourth container that represents the fourth uniquely addressable physical location in the software production landscape and is associated with the executable derivative version installed in the testing environment, receiving, via the graphical user interface, input indicating a request for information about prior versions or containers that were associated with the fourth container that represents the fourth uniquely addressable physical location in the software production landscape and is associated with the executable derivative version installed in the testing environment;

wherein the automatically providing, to a user, software configuration information based at least in part on a relationship between the first and second containers at a given point in time comprises;

after receiving the input indicating a request for information about prior versions or containers that were associated with the fourth container that;

represents the fourth uniquely addressable physical location in the software production landscape and is associated with the executable derivative version installed in the testing environment, automatically providing information to the user to help the user find appropriate source code at an appropriate development branch.

2. The method of claim 1, wherein at least one of the containers comprises a directory within a software configuration management tool that hosts snapshots of the software product.

3. The method of claim 1, wherein at least one of the containers comprises a label defined in a software configuration management tool.

4. The method of claim 1, wherein at least one of the containers comprises a directory within a software configuration management tool along with a time stamp.

5. The method of claim 1, wherein at least one of the containers comprises a centrally accessible directory into which a build server places the executable derivative version.

6. The method of claim 1, wherein at least one of the containers comprises a directory into which a previously generated derivative version is copied.

7. The method of claim 1, wherein at least one of the containers comprises a runtime environment where a generated derivate version is executed.

8. The method of claim 1, further comprising:

deploying the executable derivative version to a run-time environment of a customer, wherein another container, representing another uniquely addressable physical location in the software production landscape, is associated with the deployed executable derivative version in the run-time environment.

9. The method of claim 1, further comprising:

providing, via the graphical user interface and based on the selected fourth container, information associated with a container other than the fourth container.

10. The method of claim 1, wherein the second container includes a sequence of snapshots including different executable derivative versions.

11. The method of claim 10, wherein a transformation provides read access to a first snapshot in an input container and produces a second snapshot in an output container.

12. The method of claim 11, wherein the transformation comprises a transport such that the second snapshot is identical to the first snapshot.

13. The method of claim 1, wherein said building the executable derivative version of the software product is associated with integration of multiple elements from development branches.

14. An apparatus, comprising:

an integration branch that includes hardware and is to establish a source version of a software product, wherein a first container, representing a first uniquely addressable physical location in a software production landscape, is associated with the source version;

a derivative storage element that includes hardware and is to receive an executable derivative version of the software product built from the source version, wherein a second container, representing a second uniquely addressable physical location in the software production landscape, is associated with the executable derivative version; and

an application server that includes hardware and is to automatically provide, to a user, software configuration information based at least in part on a relationship between the first and second containers at a given point in time;

wherein the source version is a first portion of source code created at a first development branch,

wherein the source code further comprises a second portion created at a second development branch;

wherein a third container, representing a third uniquely addressable physical location in the software production landscape, is associated with the second portion of source code;

wherein the executable derivative version of the software product built from the source version comprises an executable derivative version of the software product built from the first portion of source code associated with the first container and the second portion of source code associated with the third container;

wherein the executable derivative version of the software product is installed in a testing environment;

wherein a fourth container, representing a fourth uniquely addressable physical location in the software production landscape, is associated with the executable derivative version installed in the testing environment;

the apparatus further comprising;

a graphical user interface to receive input indicating selection of the fourth container that represents the fourth uniquely addressable physical location in the software production landscape and is associated with the executable derivative version installed in the testing environment;

the graphical user interface further to receive, after receiving the input indicating the selection of the fourth container that represents the fourth uniquely addressable physical location in the software production landscape and is associated with the executable derivative version installed in the testing environment, input indicating a request for information about prior versions or containers that were associated with the fourth container that represents the fourth uniquely addressable physical location in the software production landscape and is associated with the executable derivative version installed in the testing environment;

wherein the automatically provide, to a user, software configuration information based at least in part on a relationship between the first and second containers at a given point in time comprises;

after receiving the input indicating a request for information about prior versions or containers that were associated with the fourth container that;

represents the fourth uniquely addressable physical location in the software production landscape and is associated with the executable derivative version installed in the testing environment, automatically provide information to the user to help the user find appropriate source code at an appropriate development branch.

15. The apparatus of claim 14, further comprising a process log tool core to facilitate an exchange of information with the user.

16. A non transitory computer-readable medium storing processor-executable process steps that, when executed by a processor, perform a method, wherein the method comprises:

establishing a source version of a software product;

associating a first container, representing a first uniquely addressable physical location in a software production landscape, with the source version;

building an executable derivative version of the software product from the source version;

associating a second container, representing a second uniquely addressable physical location in the software production landscape, with the executable derivative version; and

automatically providing, to a user, software configuration information based at least in part on a relationship between the first and second containers at a given point in time;

wherein the source version is a first portion of source code created at a first development branch,

the method further comprising;

creating a second portion of source code at a second development branch; and

associating a third container, representing a third uniquely addressable physical location in the software production landscape, with the second portion of source code;

wherein the building an executable derivative version of the software product from the source version comprises;

building the executable derivative version of the software product from the first portion of source code that is associated with the first container and the second portion of source code that is associated with the third container;

the method further comprising;

installing the executable derivative version of the software product in a testing environment;

associating a fourth container, representing a fourth uniquely addressable physical location in the software production landscape, with the executable derivative version installed in the testing environment;

receiving, via a graphical user interface, input indicating selection of the fourth container that represents the fourth uniquely addressable physical location in the software production landscape and is associated with the executable derivative version installed in the testing environment; and

after receiving the input indicating the selection of the fourth container that represents the fourth uniquely addressable physical location in the software production landscape and is associated with the executable derivative version installed in the testing environment, receiving, via the graphical user interface, input indicating a request for information about prior versions or containers that were associated with the fourth container that represents the fourth uniquely addressable physical location in the software production landscape and is associated with the executable derivative version installed in the testing environment;

wherein the automatically providing, to a user, software configuration information based at least in part on a relationship between the first and second containers at a given point in time comprises;

after receiving the input indicating a request for information about prior versions or containers that were associated with the fourth container that;

represents the fourth uniquely addressable physical location in the software production landscape and is associated with the executable derivative version installed in the testing environment, automatically providing information to the user to help the user find appropriate source code at an appropriate development branch.

17. The non transitory computer-readable medium of claim 16, wherein at least one of the containers comprises a directory within a software configuration management tool that hosts snapshots of the software product.

18. The non transitory computer-readable medium of claim 16, wherein at least one of the containers comprises a label defined in a software configuration management tool.

19. The non transitory computer-readable medium of claim 16, wherein at least one of the containers comprises a directory within a software configuration management tool along with a time stamp.

20. The non transitory computer-readable medium of claim 16, wherein at least one of the containers comprises a centrally accessible directory into which a build server places the executable derivative version.