Continuous deployment

• US 9,542,175 B2
• Filed: 06/23/2006
• Issued: 01/10/2017
• Est. Priority Date: 06/24/2005
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Tseitlin, Ariel D., Kearns, Daniel
• Primary Examiner(s): Puente, Emerson
• Assistant Examiner(s): KRETZMER, ERIKA A
• Application Number:
  US11/426,250
• Publication Number:
  US 20070250574A1
• Time in Patent Office: 3,854 Days
• Field of Search: 717168-178, 719/330
• US Class Current: 1/1
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06F 9/54 Interprogram communication
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: H04L 67/133 Protocols for remote procedure calls [RPC]

Abstract

A method is provided. The method stores a first version of an artifact in a first environment. Further, the method stores a second version of the artifact in the first environment. In addition, the second version of the artifact is distinct from the first version of the artifact. The method also deploys the first version of the artifact and the second version of the artifact to a second environment so that the first artifact and the second artifact can be run simultaneously in the second environment. The second environment is distinct from the first environment.

Claims

1. A method comprising:

generating a first module by packaging a first set of code for a first version of a service associated with a first application that executes in a first environment;

deploying the first module to the first environment from a second environment, wherein the first environment and the second environment are distinct, and

the first module comprises a first module interface that is configured to access the first module in the first environment and in the second environment;

generating a second module by packaging a second set of code for a second version of the service associated with a second application that executes in the second environment; and

deploying the second module to the first environment from the second environment, wherein

the second module comprises

a second module interface that is distinct from the first module interface and is configured to access the second module in the first environment and in the second environment,

the first module and the second module are distinct,

the first application and the second application are distinct,

and

the deploying the first module and the second module to the first environment permits the first module and the second module to operate simultaneously in the first environment to provide the first version of the service associated with the first application and the second version of the service associated with the second application,

wherein,

a first copy of the first version of the service is stored on a first server,

a second copy of the first version of the service is stored on a second server,

a first copy of the second version of the service is stored on the first server,

a second copy of the second version of the service is stored on the second server,

the first module interface has access to both the first server and the second server, and

the second module interface has access to both the first server and the second server.

2. The method of claim 1, wherein

the second module comprises additional data not present in the first module, and

any additional material of a future version of the service is added to the second module.

3. The method of claim 1, further comprising:

deploying a first artifact for the first module, wherein

the first artifact comprises a first component of the first module; and

deploying a second artifact for the second module, wherein

the second artifact comprises a second component of the second module, and

the first and second artifacts are configured to operate simultaneously in the first environment.

4. The method of claim 3, wherein

the first artifact and the second artifact are each one of a business object, a business service, a business rule, a business event, a business process, or a module interface.

5. The method of claim 4, wherein

the first and second artifacts publish public and stable application programming interfaces (APIs) for the first module interface and the second module interface respectively, and

the public and stable APIs only permit additive changes for future versions of the service.

6. The method of claim 3, further comprising:

storing, in a repository, a first set of metadata for the first module and a second set of metadata for the second module, wherein

the repository is accessible to the first environment.

7. The method of claim 6, wherein the deploying the first module and the second module further comprises:

providing the first module and the second module to the first environment, and

installing the first module and the second module in the first environment, wherein

the first module comprises the first set of metadata,

the second module comprises the second set of metadata,

the first and second sets of metadata comprise configuration information for the first environment, and

the configuration information is configured to facilitate operation of the first and second modules in the first environment.

8. The method of claim 7, further comprising:

deploying a first version of the first artifact to the first environment, wherein

the first version of the first artifact is stored in the repository, and

the first version of the first artifact comprises

the first set of metadata configured to be used by the first version of the service;

deploying a second version of the second artifact to the first environment, wherein

the second version of the second artifact is stored in the repository,

the second version of the second artifact comprises the second set of metadata configured to be used by the first version of the service, and

the first set of metadata is distinct from the second set of metadata; and

retrieving the first and second sets of metadata from the repository, wherein

the first version of the service is configured to use the first and second sets of metadata to identify a schema that is compatible for use with the first version of the service.

9. The method of claim 6, wherein

the first set of metadata indicates a first version number of the first version of the service and the first application, and

the second set of metadata indicates a second version number of the second version of the service and the second application.

10. The method of claim 3, further comprising:

deploying a third module to a third environment, wherein

the third module comprises a third version of the service,

modifications made to the first module in the first environment triggers additional modifications made to the third module in the third environment, and

the additional modifications are made to the third module by deploying the first artifact to the third environment for the third module.

11. The method of claim 1, wherein

the first module is configured to be utilized in the first environment by a first user, at the same time that the second module is utilized in the first environment by a second user,

the second module is deployed after the first module, and

the second module is deployed while the first module is executing in the first environment.

12. The method of claim 11, wherein

the deploying the second module does not result in the first user of the first module experiencing downtime.

13. The method of claim 1, wherein

the first application comprises a first entry point for execution, and

the second application comprises a second entry point for execution.

14. The method of claim 1, wherein

the packaging of the first set of code to generate the first module comprises customizing the first set of code for a first computing platform of the first environment,

the packaging of the second set of code to generate the second module comprises customizing the second set of code for a second computing platform of the second environment, and

the first and the second computing platforms comprise disparate hardware and software components or characteristics.

15. The method of claim 1, wherein

the first set of code is compiled and linked in the second environment,

the packaging to produce the first module is performed in the second environment,

the second set of code is compiled and linked in the second environment, and

the packaging to produce the second module is performed in the second environment.

16. The method of claim 1, wherein

if the first version of the service is replaced by the second version of the service on the first server, the first user can still access the first version of the service on the second server through the first module interface.

17. The method of claim 1, wherein

the service is an application service.

18. A non-transitory machine readable medium comprising a set of instructions, which, when executed, perform a method comprising:

generating a first module by packaging a first set of code for a first version of a service associated with a first application that executes in a first environment;

deploying the first module to the first environment from a second environment, wherein

the first environment and the second environment are distinct, and

the first module comprises

a first module interface that is configured to access the first module in the first environment and in the second environment;

generating a second module by packaging a second set of code for a second version of the service associated with a second application that executes in the second environment; and

deploying the second module to the first environment from the second environment, wherein

the second module comprises

a second module interface that is distinct from the first module interface and is configured to access the second module in the first environment and in the second environment,

the first module and the second module are distinct,

the first application and the second application are incompatible, and

the deploying the first module and the second module to the first environment permits the first module and the second module to operate simultaneously in the first environment to provide the first version of the service associated with the first application and the second version of the service associated with the second application, wherein

a first copy of the first version of the service is stored on a first server,

a second copy of the first version of the service is stored on a second server,

a first copy of the second version of the service is stored on the first server,

a second copy of the second version of the service is stored on the second server,

the first module interface has access to both the first server and the second server, and

the second module interface has access to both the first server and the second server.

19. The non-transitory machine readable medium of claim 18, wherein the method further comprises:

providing simultaneous access to a first user of the first module and a second user of the second module.

20. The non-transitory machine readable medium of claim 19, wherein the method further comprises:

assigning the first user to the second module, wherein the first user previously utilized the first module.

21. The non-transitory machine readable medium of claim 18, wherein the second module comprises:

additional data not present in the first module.

22. The non-transitory machine readable medium of claim 18, wherein the method further comprises:

providing the first module and the second module with access to the same set of resources.

23. The non-transitory machine readable medium of claim 18, wherein the method further comprises:

installing the second module without interrupting operation of the first module, wherein

the second module is deployed after the first module.

24. The non-transitory machine readable medium of claim 18, wherein

the first and the second versions of the service are services of an enterprise application.

25. A system comprising:

a processor; and

a memory coupled to the processor, the memory storing instructions executable by the processor to;

generate a first module by packaging a first set of code for a first version of a service associated with a first application that executes in a first environment,

deploy the first module to the first environment from a second environment, wherein

the first environment and the second environment are distinct, and

the first module comprises

a first module interface that is configured to access the first module in the first environment and in the second environment,

generate a second module by packaging a second set of code for a second version of the service associated with a second application that executes in the second environment, and

deploy the second module to the first environment from the second environment, wherein

the second module comprises

a second module interface that is distinct from the first module interface and is configured to access the second module in the first environment and in the second environment,

the first module and the second module are distinct,

the first application and the second application are distinct, and

the deploying the first module and the second module to the first environment permits the first module and the second module to operate simultaneously in the first environment to provide the first version of the service associated with the first application and the second version of the service associated with the second application, wherein

a first copy of the first version of the service is stored on a first server,

a second copy of the first version of the service is stored on a second server,

a first copy of the second version of the service is stored on the first server,

a second copy of the second version of the service is stored on the second server,

the first module interface has access to both the first server and the second server, and

the second module interface has access to both the first server and the second server.

26. The system of claim 25, wherein

compatibility is established between the first module interface of the first module and the second module interface of the second module, and

the compatibility supports multiple releases of the service in the first environment.