SYSTEMS AND METHODS FOR MANAGING SOFTWARE DEVELOPMENT ENVIRONMENTS

• US 20140282400A1
• Filed: 03/12/2014
• Published: 09/18/2014
• Est. Priority Date: 03/14/2013
• Status: Active Grant

• Current Assignee: Solano Labs, Inc..
• Original Assignee: Solano Labs, Inc..
• Inventors: Moorthi, Jay, Josephson, William K.
• Granted Patent: US 10,083,027 B2
• Time in Patent Office: Days
• US Class Current: 717/122
• CPC Class Codes: G06F 2009/45562 Creating, deleting, cloning virtual machine instances
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects

Abstract

Systems and methods for branched development environments enable construction of development and deployment environments for use at various stages of software development and delivery. Various embodiments are configured to deliver these constructed environments to reproduce faithfully the state of an application at a given revision of the application'"'"'s source or configuration. The branched development system can be configured to use the constructed environments to offer a variety of novel results and benefits that simplify the development, test, deployment, and debugging tasks commonly associated with software throughout its lifecycle.

Claims

1. A system for managing development environments, the system comprising:

at least one processor operatively connected to a memory, the processor when executing is configured to;

define a plurality of source code revisions associated with at least one application;

define a plurality of environment configurations, including data dependencies for the at least one application;

generate a development environment, wherein generating the development environment includes establishing a respective source code revision and a respective set of environment configurations with a specified revision of the at least one application'"'"'s source code and configuration;

cloning the development environment on compute resources, wherein the development environment is configured to accept modification to the at least one application'"'"'s source code or configuration; and

qualify modifications to the at least one application'"'"'s source code or configuration based on qualifying the development environment and the modifications to the at least one application'"'"'s source code or configuration.

2. The system according to claim 1, further comprising an archive component configured to:

store, automatically, cloned development environments; and

store, automatically, any dependencies for the cloned development environments.

3. The system according to claim 2, wherein the archive component is further configured to transition respective cloned development environments between active and idle states.

4. The system according to claim 1, further comprising a security component configured to:

de-provision environments and any dependencies; and

generate non-repudiable guarantees for auditing the de-provisioning action.

5. The system according to claim 1, further comprising a monitoring component configured to detect automatically changes in the development environment code or configuration.

6. The system according to claim 5, wherein the monitoring component is configured to analyze executing environments periodically to detect changes in the development environment code or configuration.

7. The system according to claim 1, further comprising a qualification component configured to:

instantiate historical development environments; and

execute current test executions against a plurality of historical development environments.

8. The system according to claim 1, further comprising an analysis component configured to determine configuration differences between an external environment and a cloned development environment.

9. The system according to claim 8, wherein the analysis component is configured to execute qualification scripts to determine differences in the external environment and the cloned environment.

10. The system according to claim 9, wherein the analysis component is configured to determine differences in the external environment and the cloned environment responsive to different results returned from the qualification scripts.

11. The system according to claim 8, wherein the analysis component is configured to synchronize configuration of the cloned environment with the external environment.

12. The system according to claim 1, further comprising an interactive component configured to expose a cloned development environment to execution requests from external systems.

13. The system according to claim 12, wherein the interactive component is configured to expose the cloned development environment to testing requests.

15. The method according to claim 1, wherein the method further comprises storing, automatically, cloned development environments.

16. The method according to claim 19, wherein storing, automatically, the cloned development environments includes storing, automatically, any dependencies for the cloned development environment.

17. The method according to claim 20, wherein the method further comprises transitioning respective cloned development environments between active and idle states.

19. The method according to claim 1, wherein the method further comprises de-provisioning environments and any dependencies, and generating non-repudiable guarantees for auditing the de-provisioning action.

20. The method according to claim 1, wherein the method further comprises destroying environments and any dependencies, and generating non-repudiable guarantees for auditing the destruction action.

14. A computer implemented method for managing development environments, the method comprising:

defining, by a computer system, a plurality of source code revisions associated with at least one application;

defining, by the computer system, a plurality of environment configurations, including data dependencies for the at least one application, generating, by the computer system, a development environment, wherein generating the development environment includes establishing a respective source code revision and a respective set of environment configurations with a specified revision of the at least one application'"'"'s source code and configuration,

cloning, by the computer system, the development environment on compute resources, wherein the development environment is configured to accept modification to the at least one application'"'"'s source code or configuration, and

qualifying, by the computer system, modifications to the at least one application'"'"'s source code or configuration based on qualifying the development environment and the modifications to the at least one application'"'"'s source code or configuration.

18. The method according to claim 21, wherein the respective cloned development environment is associated with cloud compute resources executing the respective cloned development environment in the active state and wherein the respective cloned development environment is de-provisioned responsive to the transition to the idle state.