VERSION CONTROL FOR CUSTOMIZED APPLICATIONS

• US 20170168801A1
• Filed: 12/14/2015
• Published: 06/15/2017
• Est. Priority Date: 12/14/2015
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Eberlein, Peter, Driesen, Volker
• Granted Patent: US 9,740,476 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]

Abstract

A customer'"'"'s VCS is set up to store files associated with an application having application versions. The customer'"'"'s VCS includes a set of branches defined correspondingly to a set of systems of a customer change management landscape. A first branch comprises files of a first version of the application. A second version of the application is populated into the first branch. Existing customizations, modifications, and created runtime authoring objects during design time and runtime of the first version of the application are applied over the second version. The changes are submitted into the customer'"'"'s VCS and an updated version is generated in the first branch. The updated version is transported to a second branch through merging the first branch and the second branch. When a request for deployment is received, a reference to the second branch pointing to the updated version of the application is provided.

Claims

1. A computer implemented method to deliver customizations of applications for deployment through a customer'"'"'s version control system (VCS), the method comprising:

populating a first branch from a set of branches in the customer'"'"'s VCS with a second version of an application, wherein the first branch comprises files of a first version of the application;

customizing the second version of the application in the first branch to generate an updated version of the application, wherein customizing is associated with existing configurations and runtime authoring objects generated for a deployed first version of the application;

transporting the updated version of the application to a second branch from the set of branches through merging the first branch and the second branch, wherein the updated version comprises at least one modification to the files of the first version; and

in response to a request for deployment, providing a reference of the second branch for deployment of the updated version of the application on a runtime infrastructure of a corresponding system to the second branch, selected from a set of systems.

2. The method of claim 1, further comprising:

downloading the first version of the application from a vendor'"'"'s VCS to the customer'"'"'s VCS;

populating the first branch in the customer'"'"'s VCS with the files comprised in the downloaded first version of the application; and

downloading the second version of the application from the vendor'"'"'s VCS.

3. The method of claim 2, further comprising:

creating the set of branches in the customer'"'"'s VCS to correspond to the set of systems defined for the customer change management landscape; and

establishing a connection between the customer'"'"'s VCS and the vendor'"'"'s VCS.

4. The method of claim 1, wherein the set of branches are defined based on an integration complexity of a customer system landscape defining one or more applications to be deployed in the set of systems defined for a customer change management landscape.

5. The method of claim 1, wherein customizing the second version of the application in the first branch comprises:

applying existing customizations and modification on the second version of the application to generate a third version of the application in the first branch; and

updating the third version of the application with the runtime authoring objects to generate the updated version of the application, wherein the runtime authoring objects are received from the deployed first version of the application in a corresponding system to the first branch.

6. The method of claim 5, further comprising:

synchronizing files of the updated version of the application in the second branch with a file system of the corresponding system to the second branch.

7. The method of claim 5, further comprising:

customizing at least one file from the files of the updated version of the application to generate a customized updated version of the application in the second branch.

8. The method of claim 7, further comprising:

re-synchronizing the second branch with the file system of the corresponding system to the second branch through downloading the at least one customized file from the files of the updated version.

9. The method of claim 8, further comprising:

deploying the files of the updated version of the application on the runtime infrastructure of the corresponding system to the second branch through the provided reference.

10. The method of claim 9, wherein deploying the files of the updated version of the application further comprises:

fetching metadata included in the files of the updated version; and

based on the fetched metadata, a deploy service, invoking the files of the updated version through a sub-reference from the second branch defined based on the provided reference to the second branch.

11. A computer system for deliver customizations of applications for deployment through a customer'"'"'s version control system (VCS), comprising:

a processor;

a memory in association with the processor storing instructions to;

populate to a first branch from a set of branches in the customer'"'"'s VCS with a second version of an application, wherein the first branch comprises files of a first version of the application;

customize the second version of the application in the first branch to generate an updated version of the application, wherein customizing is associated with existing configurations and runtime authoring objects generated for a deployed first version of the application;

transport the updated version of the application to a second branch from the set of branches through merging the first branch and the second branch, wherein the updated version comprises at least one modification to the files of the first version; and

in response to a request for deployment, provide a reference of the second branch for deployment of the updated version of the application on a runtime infrastructure of a corresponding system from a set of systems to the second branch, wherein the set of systems are defined for a customer change management landscape.

12. The system of claim 11, further comprising instructions to:

download the first version of the application from a vendor'"'"'s VCS to the customer'"'"'s VCS;

populate the first branch in the customer'"'"'s VCS with the files comprised in the downloaded first version of the application; and

download the second version of the application from the vendor'"'"'s VCS.

13. The system of claim 12, further comprising instructions to:

create the set of branches in the customer'"'"'s VCS to correspond to the set of systems defined for the customer change management landscape; and

establish a connection between the customer'"'"'s VCS and the vendor'"'"'s VCS.

14. The system of claim 11, wherein the instructions to customize the second version of the application in the first branch, further comprises instructions to:

apply existing customizations and modification on the second version of the application to generate a third version of the application in the first branch; and

update the third version of the application with the runtime authoring objects to generate the updated version of the application, wherein the runtime authoring objects are received from the deployed first version of the application in a corresponding system to the first branch from the customer change management landscape.

15. The system of claim 14, further comprising instructions to:

synchronize files of the updated version of the application in the second branch with a file system of the corresponding system to the second branch from the set of systems;

customize at least one file from the files of the updated version of the application to generate a customized updated version of the application in the second branch; and

re-synchronize the second branch with the file system of the corresponding system to the second branch through downloading the at least one customized file from the files of the updated version.

16. The system of claim 15, further comprising instructions to:

fetching metadata included in the files of the updated version;

based on the fetched metadata, a deploy service, invoking the files of the updated version through a sub-reference to the second branch defined based on the provided reference to the second branch; and

deploy the files of the updated version of the application on the runtime infrastructure of the corresponding system to the second branch via the sub-reference.

17. A non-transitory computer-readable medium storing instructions, which when executed cause a computer system to:

populate to a first branch from a set of branches in the customer'"'"'s VCS with a second version of an application, wherein the first branch comprises files of a first version of the application;

apply defined customizations and modification for the first version of the application on the second version of the application to generate a third version of the application in the first branch;

update the third version of the application with runtime authoring objects to generate an updated version of the application, wherein the runtime authoring objects are received from a deployed first version of the application in a corresponding system to the first branch from the customer change management landscape;

transport the updated version of the application to a second branch from the set of branches through merging the first branch and the second branch, wherein the updated version comprises at least one modification to the files of the first version; and

in response to a request for deployment, provide a reference of the second branch for deployment of the updated version of the application on a runtime infrastructure of a corresponding system to the second branch, wherein the corresponding system is selected from a set of systems.

18. The computer-readable medium of claim 17, further storing instructions to:

download the first version of the application from a vendor'"'"'s VCS to the customer'"'"'s VCS;

populate the first branch in the customer'"'"'s VCS with the files comprised in the downloaded first version of the application; and

download the second version of the application from the vendor'"'"'s VCS.

19. The computer-readable medium of claim 17, further storing instructions to:

synchronize files of the updated version of the application in the second branch with a file system of the corresponding system from the set of systems to the second branch, wherein the set of systems are defined in relation to a customer change management landscape;

customize at least one file from the files of the updated version of the application to generate a customized updated version of the application in the second branch; and

re-synchronize the second branch with the file system of the corresponding system to the second branch through downloading the at least one customized file from the files of the updated version.

20. The computer-readable medium of claim 19, further storing instructions to:

fetching metadata included in the files of the updated version;

based on the fetched metadata, a deploy service, invoking the files of the updated version through a sub-reference to the second branch defined based on the provided reference to the second branch; and

deploy the files of the updated version of the application on the runtime infrastructure of the corresponding system to the second branch via the sub-reference.