Software configuration control wherein containers are associated with physical storage of software application versions in a software production landscape
First Claim
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 Assignments
0 Petitions
Accused Products
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.
-
Citations
20 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. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13)
-
-
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. - View Dependent Claims (15)
-
-
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. - View Dependent Claims (17, 18, 19, 20)
-
Specification