Systems and methods for managing software development environments

• US 10,083,027 B2
• Filed: 03/12/2014
• Issued: 09/25/2018
• 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.
• Primary Examiner(s): Zhen, Li B
• Assistant Examiner(s): KABIR, MOHAMMAD H
• Application Number:
  US14/206,443
• Publication Number:
  US 20140282400A1
• Time in Patent Office: 1,658 Days
• 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 at least one 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 respective executable branched development environment associated with a respective set of source code revisions and a respective set of environment configurations, wherein generating the respective executable branched development environment includes establishing the respective source code revisions and the respective set of environment configurations with a specified revision of the at least one application'"'"'s source code and configuration;

manage a plurality of respective codeline branches with instantiations of a plurality of respective executable branched development environments;

clone a respective executable branched development environment on compute resources to mirror at least a portion of an existing production platform that supports the executable branched development environment, wherein the executable branched development environment is configured to accept modification to the at least one application'"'"'s source code and configuration; and

automatically qualify modifications to the at least one application'"'"'s source code and configuration based on qualifying the executable branched development environment and the modifications to the at least one application'"'"'s source code and configuration, wherein to qualify the modifications the at least one processor is further configured to automatically test the modifications to the at least one application'"'"'s source code and configuration within the executable branched development environment responsive to submission or automatic detection of the modifications made in the executable branched development environment.

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

store, automatically, cloned executable branched development environments; and

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

3. The system according to claim 2, wherein the archive component is further configured to transition respective cloned executable branched 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 executable branched development environment code.

6. The system according to claim 5, wherein the monitoring component is configured to analyze executing environments periodically to detect changes in the executable branched development environment code and 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 responsive to identifying a failed test during the current test execution.

8. The system according to claim 1, further comprising an analysis component configured to determine configuration differences between an external environment and a cloned executable branched 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 executable branched development environment.

10. The system according to claim 9, wherein the analysis component is configured to determine differences in the external environment and the cloned executable branched development 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 executable branched development environment with the external environment.

12. The system according to claim 1, further comprising an interactive component configured to expose a cloned executable branched 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 executable branched development environment to testing requests.

14. The system of claim 1, wherein the at least one processor is further configured to maintain virtual machine instances of compiled versions of the codeline branches and respective executable branched development environments to manage the respective codeline branches and the respective executable branched development environments.

15. The system of claim 1, wherein the at least one processor is further configured to reject the modifications to the at least one application'"'"'s source code and configuration responsive to failed qualification and accept the modifications to the at least one application'"'"'s source code and configuration responsive to passed qualification.

16. 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 respective executable branched development environment associated with a respective set of source code revisions and a respective set of environment configurations, wherein generating the respective executable branched development environment includes establishing the respective source code revisions and the respective set of environment configurations with a specified revision of the at least one application'"'"'s source code and configuration;

managing, by the computer system, respective codeline branches with respective executable branched development environments;

cloning, by the computer system, the respective executable branched development environment on compute resources to mirror at least a portion of an existing production platform that supports the executable branched development environment, wherein the executable branched development environment is configured to accept modification to the at least one application'"'"'s source code and configuration; and

automatically qualifying, by the computer system, modifications to the at least one application'"'"'s source code and configuration based on qualifying the executable branched development environment and the modifications to the at least one application'"'"'s source code and configuration, wherein qualifying includes automatically testing the modifications to the at least one application'"'"'s source code and configuration within the executable branched development environment responsive to submission or automatic detection of the modifications made in the executable branched development environment.

17. The method according to claim 16, wherein the method further comprises storing, automatically, cloned executable branched development environments.

18. The method according to claim 17, wherein storing, automatically, the cloned executable branched development environments includes storing, automatically, any dependencies for the cloned executable branched development environment.

19. The method according to claim 18, wherein the method further comprises transitioning respective cloned executable branched development environments between active and idle states.

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

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

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