Configuring DevOps Pipelines Across Domains And Thresholds

Abstract

The present invention extends configuring development and operations pipelines across domains. A pipeline manager can form and manage pipelines that span any combination of domains and any combination of: public cloud resources, private cloud resources, user on-premise resources, etc., in accordance with appropriate (cloud andor on-premise) profile information. The pipeline manager can (re)configure a pipeline as appropriate to address alterations to workflows, upgrades to DevOps tools, removal of functionality from a workflow, etc. A pipeline framework enables customers to build no-code pipelines spanning domains for various use cases in a plug and play manner (Software engineering and SDLC pipelines, Salesforce Cl/CD pipelines, AI/ML, SaaS applications, Infrastructure as a code (IaC), etc). The pipeline framework enables users to integrate collaboration tools, notifications, and approval gates offering thresholds at each and every step. In addition, the pipeline framework captures logs and provides a summary via livestream and also upon completion of each pipeline activity and after each pipeline.

What is claimed: 
     
         1 . A DevOps pipeline orchestration method comprising:
 accessing a user specified workflow defining a DevOps pipeline including:
 declaring first policy conditions associated with a first DevOps pipeline stage in a specified domain and designated to run at a first computing location; 
   and
 declaring second policy conditions associated with a second DevOps pipeline stage in another specified domain designated to run at a second computing location; and 
   orchestrating the DevOps pipeline spanning the specified domain and other specified domain including orchestrating DevOps tools along with one or more of: source code, executable images, data, containers, and configuration between DevOps pipeline stages, including:
 configuring the first DevOps pipeline stage at the first computing location; 
 configuring the second DevOps pipeline stage at the second computing location; 
 connecting and chaining first DevOps pipeline stage output to second DevOps pipeline stage input connecting output from the specified domain to input of the other specified domain; 
 executing the first DevOps pipeline stage in the specified domain at the first computing location, including:
 accessing first pipeline stage input data; 
 operating the first DevOps pipeline stage transforming the first pipeline stage input data into first pipeline stage output data; 
 deriving first stage operational data associated with operating the first DevOps pipeline stage; 
 logging the first stage operational data; 
 determining that the first operational data satisfies the first policy conditions; and 
 notifying a party that the first policy conditions are satisfied; 
 
 and 
 receiving approval from the party to transition to a next pipeline stage. 
   
     
     
         2 . The method of  claim 1 , wherein declaring first policy conditions associated with a first DevOps pipeline stage in a specified domain comprises declaring first policy conditions associated with the first DevOps pipeline stage in the specified domain, wherein the specified domain is selected from among: a software development domain, a software engineering domain, a Kubernetes domain, an Infrastructure as a Code (IaC) domain, multilanguage, an Artificial Intelligence (AI)/Machine Learning (ML) domain, a Salesforce (SFDC) domain, a service now domain, a SaaS application domain, a pega domain, a Database (DB) domain, a workaday domain, or a package deployment domain. 
     
     
         3 . The method of  claim 1 , further comprising in response to the approval, executing the second DevOps pipeline stage in the other specified domain at the second computing location, including:
 accessing the first pipeline stage output data;   utilizing at least a portion of the first pipeline stage output data as second pipeline stage input data;   operating the second DevOps pipeline stage transforming the second pipeline stage input data into second pipeline stage output data;   deriving second stage operational data associated with operating the second DevOps pipeline stage;   logging the second stage operational data;   determining whether the second operational data does or does not satisfy the second policy conditions; and   notifying another party of the determination; and   proceeding to a next pipeline activity based on the determination.   
     
     
         4 . The method of  claim 3 , wherein the specified domain and the other specified domain are different domains. 
     
     
         5 . The method of  claim 4 , wherein executing the first DevOps pipeline stage in the specified domain at the first computing location comprises executing the first DevOps pipeline stage in a first cloud;
 wherein executing the second DevOps pipeline stage in the other specified domain at the second computing location comprises executing the second DevOps pipeline stage in a second cloud, the second cloud differing from the first cloud;   wherein orchestrating the DevOps pipeline comprises orchestrating the DevOps pipeline spanning the first cloud and the second cloud; and   wherein connecting and chaining first DevOps pipeline stage output to second DevOps pipeline stage input comprises connecting and chaining computing resources of the first cloud to computing resources of the second cloud.   
     
     
         6 . The method of  claim 4 , wherein executing the first DevOps pipeline stage in the specified domain at the first computing location comprises executing the first DevOps pipeline stage in a cloud;
 wherein executing the second DevOps pipeline stage in the other specified domain at the second computing location comprises executing the second DevOps pipeline stage in user on-premise resources;   wherein orchestrating the DevOps pipeline comprises orchestrating the DevOps pipeline spanning the cloud and the user on-premise resources; and   wherein connecting and chaining first DevOps pipeline stage output to second DevOps pipeline stage input comprises connecting and chaining computing resources of the cloud to the user on-premise resources.   
     
     
         7 . The method of  claim 3 , wherein declaring first policy conditions associated with a first DevOps pipeline stage in a specified domain comprises declaring first policy conditions associated with the first DevOps pipeline stage in the specified domain, wherein the specified domain is selected from among: a software development domain, a software engineering domain, a Kubernetes domain, an Infrastructure as a Code (IaC) domain, multilanguage, an Artificial Intelligence (AI)/Machine Learning (ML) domain, a Salesforce (SFDC) domain, a service now domain, a SaaS application domain, a pega domain, a Database (DB) domain, a workaday domain, or a package deployment domain. 
     
     
         8 . The method of  claim 7 , wherein declaring second policy conditions associated with a second DevOps pipeline stage in another specified domain comprises declaring second policy conditions associated with the second DevOps pipeline stage in the other specified domain, wherein the other specified domain differs from the specified domain and is selected from among: a software development domain, a software engineering domain, a Kubernetes domain, an Infrastructure as a Code (IaC) domain, multilanguage, an Artificial Intelligence (AI)/Machine Learning (ML) domain, a Salesforce (SFDC) domain, a service now domain, a SaaS application domain, a pega domain, a Database (DB) domain, a workaday domain, or a package deployment domain. 
     
     
         9 . The method of  claim 3 , wherein accessing the user specified workflow comprises accessing the user specified workflow declaring a user approval requirement between the first pipeline stage and the second pipeline stage;
 wherein notifying a party that the first policy conditions are satisfied comprises notifying the party in accordance with the user approval requirement; and   wherein receiving approval from the party comprises receiving approval via one of: a messaging system, an electronic mail message, text messaging, or an Information Technology System Management (ITSM) tool.   
     
     
         10 . The method of  claim 3 , wherein the user specified workflow declaring first policy conditions associated with a first DevOps pipeline comprises the user specified workflow declaring one or more of: security conditions, quality conditions, compliance conditions, or custom thresholds associated with the first pipeline stage; and
 wherein determining that the first operational data satisfies the first policy conditions comprises determining that the first operational data satisfies the one or more of: the security conditions, the quality conditions, the compliance conditions, or the custom thresholds.   
     
     
         11 . A system comprising:
 a processor;   system memory coupled to the processor and storing instructions configured to cause the processor to:
 access a user specified workflow defining a DevOps pipeline including:
 declare first policy conditions associated with a first DevOps pipeline stage in a specified domain and designated to run at a first computing location; and 
 declare second policy conditions associated with a second DevOps pipeline stage in another specified domain designated to run at a second computing location; and 
 
 orchestrate the DevOps pipeline spanning the specified domain and the other specified domain including orchestrating DevOps tools along with one or more of: source code, executable images, data, containers, and configuration between DevOps pipeline stages, including:
 configure the first DevOps pipeline stage at the first computing location; 
 configure the second DevOps pipeline stage at the second computing location; 
 connect and chain first DevOps pipeline stage output to second DevOps pipeline stage input connecting output from the specified domain to input of the other specified domain; 
 execute the first DevOps pipeline stage in the specified domain at the first computing location, including:
 access first pipeline stage input data; 
 operate the first DevOps pipeline stage transforming the first pipeline stage input data into first pipeline stage output data; 
 derive first stage operational data associated with operating the first DevOps pipeline stage; 
 log the first stage operational data; 
 determine that the first operational data satisfies the first policy conditions; and 
 notify a party that the first policy conditions are satisfied; and 
 
 receive approval from the party to transition to a next pipeline stage. 
 
   
     
     
         12 . The system of  claim 11 , wherein instructions configured to declare first policy conditions associated with a first DevOps pipeline stage in a specified domain comprises instructions configured to declare the first policy conditions associated with the first DevOps pipeline stage in the specified domain, wherein the specified domain is selected from among: a software development domain, a software engineering domain, a Kubernetes domain, an Infrastructure as a Code (IaC) domain, multilanguage, an Artificial Intelligence (AI)/Machine Learning (ML) domain, a Salesforce (SFDC) domain, a service now domain, a SaaS application domain, a pega domain, a Database (DB) domain, a workaday domain, or a package deployment domain. 
     
     
         13 . The system of  claim 11 , further comprising instructions configured to in response to the approval, execute the second DevOps pipeline stage in the other specified domain at the second computing location, including:
 access the first pipeline stage output data;   utilize at least a portion of the first pipeline stage output data as second pipeline stage input data;   operate the second DevOps pipeline stage transforming the second pipeline stage input data into second pipeline stage output data;   derive second stage operational data associated with operating the second DevOps pipeline stage;   log the second stage operational data;   determine whether the second operational data does or does not satisfy the second policy conditions; and   notify another party of the determination; and   proceed to a next pipeline activity based on the determination.   
     
     
         14 . The system of  claim 13 , wherein the specified domain and the other specified domain are different domains. 
     
     
         15 . The system of  claim 14 , wherein instructions configured to execute the first DevOps pipeline stage in the specified domain at the first computing location comprise instructions configured to execute the first DevOps pipeline stage in a first cloud;
 wherein instructions configured to execute the second DevOps pipeline stage in the other specified domain at the second computing location comprises instructions configured to execute the second DevOps pipeline stage in a second cloud, the second cloud differing from the first cloud;   wherein instructions configured to orchestrate the DevOps pipeline comprises instructions configured to orchestrate the DevOps pipeline spanning the first cloud and the second cloud; and   wherein instructions configured to connect and chain first DevOps pipeline stage output to second DevOps pipeline stage input comprise instructions configured to connect and chain computing resources of the first cloud to computing resources of the second cloud.   
     
     
         16 . The system of  claim 14 , wherein instructions configured to execute the first DevOps pipeline stage in the specified domain at the first computing location comprise instructions configured to execute the first DevOps pipeline stage in a cloud;
 wherein instructions configured to execute the second DevOps pipeline stage in the other specified domain at the second computing location comprise instructions configured to execute the second DevOps pipeline stage in user on-premise resources;   wherein instructions configured to orchestrate the DevOps pipeline comprise instructions configured to orchestrate the DevOps pipeline spanning the cloud and the user on-premise resources; and   wherein instructions configured to connect and chain first DevOps pipeline stage output to second DevOps pipeline stage input comprise instructions configured to connect and chain computing resources of the cloud to the user on-premise resources.   
     
     
         17 . The system of  claim 13 , instructions configured to declare first policy conditions associated with a first DevOps pipeline stage in a specified domain comprise instructions configured to declare first policy conditions associated with the first DevOps pipeline stage in the specified domain, wherein the specified domain is selected from among: a software development domain, a software engineering domain, a Kubernetes domain, an Infrastructure as a Code (IaC) domain, multilanguage, an Artificial Intelligence (AI)/Machine Learning (ML) domain, a Salesforce (SFDC) domain, a service now domain, a SaaS application domain, a pega domain, a Database (DB) domain, a workaday domain, or a package deployment domain. 
     
     
         18 . The system of  claim 17 , wherein instructions configured to declare second policy conditions associated with a second DevOps pipeline stage in another specified domain comprise instructions configured to declare second policy conditions associated with the second DevOps pipeline stage in the other specified domain, wherein the other specified domain differs from the specified domain and is selected from among: a software development domain, a software engineering domain, a Kubernetes domain, an Infrastructure as a Code (IaC) domain, multilanguage, an Artificial Intelligence (AI)/Machine Learning (ML) domain, a Salesforce (SFDC) domain, a service now domain, a SaaS application domain, a pega domain, a Database (DB) domain, a workaday domain, or a package deployment domain. 
     
     
         19 . The system of  claim 13 , wherein instructions configured to access the user specified workflow comprises instructions configured to access the user specified workflow declaring a user approval requirement between the first pipeline stage and the second pipeline stage;
 wherein instructions configured to notify a party that the first policy conditions are satisfied comprise instructions configured to notify the party in accordance with the user approval requirement; and   wherein instructions configured to receive approval from the party comprise instructions configured to receive approval via one of: a messaging system, an electronic mail message, text messaging, or an Information Technology System Management (ITSM) tool.   
     
     
         20 . The system of  claim 13 , wherein instructions configured to declare first policy conditions associated with a first DevOps pipeline comprise instructions configured to declare one or more of: security conditions, quality conditions, compliance conditions, or custom thresholds associated with the first pipeline stage; and
 wherein instructions configured to determine that the first operational data satisfies the first policy conditions comprise instructions configured to determine that the first operational data satisfies the one or more of: the security conditions, the quality conditions, the compliance conditions, or the custom thresholds.