Abstract: The present invention extends configuring development and operations pipelines using drag and drop techniques. Through user interface gestures, users can form and manage pipelines that span any combination of: public cloud resources, private cloud resources, user on-premise resources, etc., in accordance with appropriate (cloud and/or on-premise) profile information. The user interface facilitates pipeline (re)configuration as appropriate to address alterations to workflows, upgrades to DevOps tools, removal of functionality from a workflow, etc. The user interface enables customers to build no-code pipelines for various use cases in a drag and drop manner. Users can 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.

Abstract: The present invention extends to methods, systems, and computer program products for deriving unified insights ad logs from DevOps Cl/CD tools and pipeline data. In general, a data transformer facilitates data normalization and serialization converting raw data across multiple DevOps tools and stores the data into a Data Lake in accordance with a customized schema. A continuous orchestrator sequences, aggregates and contextualizes the logs, providing an intuitive way of troubleshooting issues across a DevOps environment, historical data for compliance and audit purposes, and a build manifest for root cause analysis. The continuous orchestrator also processes the logs and leverages a KPI framework, providing intelligent dashboards across 90+ KPI's and a plurality of different dimensions (Planning, Development/pipelines, security, quality, operations, productivity and source code) to help customers make smart decisions and do more with less.

Abstract: The present invention extends to methods, systems, and computer program products for tool registry for automating DevOps toolchains. Submission of a DevOps tool, authentication information, and tool configuration data is received from a user. Subsequently, the DevOps tool is selected for inclusion in a DevOps job. The DevOps tool including the authentication information and tool configuration data is automatically accessed from the tool registry. The DevOps tool is configured in accordance with the accessed authentication information and accessed tool configuration data as part of the DevOps job and for interaction with the one or more other DevOps tools. The DevOps job is deployed.

Abstract: The present invention extends to methods, systems, and computer program products for deriving unified insights ad logs from DevOps CI/CD tools and pipeline data. In general, a data transformer facilitates data normalization and serialization converting raw data across multiple DevOps tools and stores the data into a Data Lake in accordance with a customized schema. A continuous orchestrator sequences, aggregates and contextualizes the logs, providing an intuitive way of troubleshooting issues across a DevOps environment, historical data for compliance and audit purposes, and a build manifest for root cause analysis. The continuous orchestrator also processes the logs and leverages a KPI framework, providing intelligent dashboards across 90+ KPI's and a plurality of different dimensions (Planning, Development/pipelines, security, quality, operations, productivity and source code) to help customers make smart decisions and do more with less.

Abstract: The present invention extends to methods, systems, and computer program products for upgrading DevOps tools in DevOps toolchains. An upgraded version of a DevOps platform tool is detected. A snapshot of an existing tool image corresponding to a current version of the DevOps platform tool is taken. Cloud service provider profile information, existing tool profile information corresponding to the existing tool image, and replacement tool profile information corresponding to replacement tool image are accessed. A DevOps platform is upgraded including deploying a replacement tool image corresponding to the upgraded version in accordance with the cloud service provider profile information, the existing tool profile information, the replacement tool profile information, and a DevOps platform category. When the upgrade is complete, the existing tool image is removed and the DevOps platform pointed to the replacement tool image. The snapshot is retained in accordance with rollback settings.

Abstract: The present invention extends to methods, systems, and computer program products for replacing DevOps tools in DevOps toolchains. A user selection of a replacement DevOps platform tool associated with a DevOps platform category is received. Configuration information for the DevOps platform, including cloud service provider profile information and existing tool profile information is accessed. The existing tool is removed from the DevOps platform in accordance with the existing tool profile information, the DevOps platform category, and the service provider profile information. A replacement tool and replacement tool profile information are accessed. The replacement tool is deployed to the DevOps platform in accordance with the replacement tool profile information, the DevOps platform category, and the cloud service provider profile information.

Abstract: The present invention extends to methods, systems, and computer program products for removing DevOps tools from DevOps toolchains. A user selection requesting DevOps tool deletion is received. A snapshot of a tool image corresponding to the DevOps tool is taken. Cloud service provider profile information and tool profile information corresponding to the tool image are accessed. The DevOps tool is deleted from a DevOps platform, including removing the tool image, in accordance with the cloud service provider profile information and the tool profile information. A tool registry is updated to indicate removal of the tool image from the DevOps platform. The snapshot is stored and retained in accordance with a time period specified in rollback settings.

Abstract: The present invention extends to methods, systems, and computer program products for automating DevOps toolchains. A user registers with a platform provider through a user interface that provides a unified self-service portal. Subsequently, the user can login to a platform configuration system to access a user landing page and/or dashboard. The user can select DevOps platform tools to be installed and enter configuration information. When the user is satisfied with selected DevOps platform tools and entered configuration, the user can select a “confirm” user-interface control (e.g., a button). In response, the selected DevOps tools are installed (with a relatively high level of automation) as DevOps platform. The user can also change DevOps platforms through the user interface (also with a relatively high level of automation), including migrating, deleting, and upgrading DevOps tools.