Methods and systems that share resources among multiple, interdependent release pipelines
The current document is directed to automated application-release-management facilities that, in a described implementation, coordinate continuous development and release of cloud-computing applications. The application-release-management process is specified, in the described implementation, by application-release-management pipelines, each pipeline comprising one or more stages, with each stage comprising one or more tasks. The currently described methods and systems allow resources to be shared among multiple, interdependent release pipelines and allow access to shared resources to be controlled.
1. An automated-application-release-management subsystem within workflow-based cloud-management system installed within a cloud-computing facility having multiple servers, data-storage devices, and one or more internal networks, the automated-application-release-management subsystem comprising:
a dashboard user interface;
an automated-application-release-management-controller component of the automated-application-release-management subsystem that controls execution of application-release pipelines having multiple stages, each stage having tasks; and
an automated-application-release-management-interface component of the automated-application-release-management subsystem through which a cloud-computing facility administrator or manager selects a set of plugged-in modules and subsystems for each of one or more stages of an application-release pipeline.
2. The system of claim 1 , further comprising a management controller that controls execution of application-release pipelines.
3. The system of claim 1 , wherein the application-release pipelines are interdependent.
4. The system of claim 1 , wherein execution of the tasks generate a releasable version of an application.
5. The system of claim 4 , wherein the tasks comprise one or more of the following: initialization tasks, deployment tasks, run-tests tasks, gating-rule tasks, and finalize tasks.
6. The system of claim 3 , further comprising multiple resources, including: entry points for executables, including applications and routines; machine resources, including virtual machines and vApps; and parameters output by release pipelines.
7. The system of claim 1 wherein the management controller provides parameter values as inputs for task execution and receives output parameters from tasks following completion of their execution, and wherein the tasks cannot exchange parameter values among themselves during execution of an application-release pipeline, and wherein the tasks and the plurality of stages have predefined input and output parameters.
8. A method carried out in an automated-application-release-management subsystem within a cloud-computing facility having multiple servers, data-storage devices, and one or more internal networks, the method comprising:
providing a user interface that enables a user to build and launch an application-release pipeline, the application-release pipeline comprising a plurality of stages, each of the plurality of stages having tasks;
receiving, by the user interface, defined tasks within each of the plurality of stages of the application-release pipeline; and
launching the built application-release pipeline.
9. The method of claim 8 , further comprising enabling the user to select a set of plugged-in modules and subsystems for each of the plurality of stages of the application-release pipeline.
10. The method of claim 8 , wherein application-release pipelines are interdependent.
11. The method of claim 8 , wherein execution of the tasks generate a releasable version of an application.
12. The method of claim 11 wherein the tasks comprise one or more of the following: initialization tasks, deployment tasks, run-tests tasks, gating-rule tasks, and finalize tasks.
13. The method of claim 3 , further comprising, receiving, from the user, a selection of multiple resources for the application-release pipeline, the multiple resources comprising: entrypoints for executables, including applications and routines; machine resources, including virtual machines and vApps; and parameters output by release pipelines.
14. The method of claim 1 , wherein the tasks cannot exchange parameter values among themselves during execution of an application-release pipeline, and wherein the tasks and the plurality of stages have predefined input and output parameters.
15. One or more non-transitory computer-readable media having computer-executable instructions that, when executed by one or more processors, cause the one or more processors to perform operations comprising:
providing a user interface that enables a user to build and launch an application-release pipeline, the application-release pipeline comprising a plurality of stages, each of the plurality of stages having tasks;
receiving, by the user interface, defined tasks within each of the plurality of stages of the application-release pipeline;
enabling the user to select a set of plugged-in modules and subsystems for each of the plurality of stages of the application-release pipeline
launching the built application-release pipeline.
16. The one or more non-transitory computer-readable media of claim 15 , wherein the computer-executable instructions further cause the one or more processors to perform operations comprising receiving, from the user, specifications for each of the plurality of stages for the application-release pipeline.
17. The one or more non-transitory computer-readable media of claim 15 , wherein application-release pipelines are interdependent.
18. The one or more non-transitory computer-readable media of claim 15 , wherein execution of the tasks generate a releasable version of an application.
19. The one or more non-transitory computer-readable media of claim 18 , wherein the tasks comprise one or more of the following: initialization tasks, deployment tasks, run-tests tasks, gating-rule tasks, and finalize tasks.
20. The one or more non-transitory computer-readable media of claim 15 , wherein the computer-executable instructions further cause the one or more processors to perform operations comprising receiving, from the user, a selection of multiple resources for the application-release pipeline.