Continuous Delivery Pipeline

Introduction

The Continuous Delivery Pipeline has undergone a significant redesign to empower users with enhanced control and visibility over their deployment processes. This revamped feature now offers two distinct views: Environment View and Environment Group View, each tailored to provide comprehensive insights into the latest deployments across all continuous deployment phases, accompanied by detailed build and deployment history information to meet the specific needs of Release Managers, Environment Managers, Test Managers, and Delivery Teams.

When testers or product owners deploy new features at scale, the Continuous Delivery Pipeline allows them to:

  • Monitor Deployment Progress: Track the deployment progress of new features across various environments in real-time.
  • Ensure Consistency: Ensure consistency in the deployment process across different environments, from development to production.
  • Access Deployment History: Access detailed deployment history to review past deployments and identify any issues or discrepancies.
  • Gain Visibility: Gain visibility into source code changes, build versions, and deployment status to ensure transparency and accountability.
  • Facilitate Collaboration: Facilitate collaboration between development, testing, and operations teams by providing a centralized platform for managing deployment activities.

Pre-requisite

You must have the ‘View Continuous Delivery Pipeline’ user permission.

Environment > Continuous Delivery Pipeline

Access Continuous Delivery Pipeline

Navigate to Environment > Continuous Delivery Pipeline and select Environment view or Environment Group view from the drop-down.

View Options

Environment view

The Environment View presents a comprehensive pipeline overview of all environments associated with each system. Users can effortlessly track the latest build versions deployed to each environment, filter environments and subsystems based on specific criteria, and delve into detailed deployment histories.

Key Features:

  • Cascading filter options for System, Subsystem, and Environments
  • Display of Environments grouped by their ‘Used for Phase’ value
  • Detailed information for each Environment
  • Access to filtered Subsystems and deployed Builds

 Last Deployment Details

The top area in each Environment panel contains details about latest deployments on this Environment:

  • Last X Days Deployments
  • Active Subsystems
  • Inactive Subsystems
  • Build (most recent deployment)
  • Last Deployment details (System, Build, Date, History)

Environment Group view

The Environment Group View offers users a holistic perspective of the continuous delivery pipeline organized by environment groups. Users can easily monitor the current build details for each environment within a group, filter environments by system, explore comprehensive group, environment, and build details, and drill down into subsystem instances for deeper insights.

Key Features:

  • Cascading filter options for Environment Group and System
  • Display of Environment Groups grouped by their ‘Used for Phase’ value
  • Comprehensive information for each Environment Group
  • Access to filtered Environments and deployed Builds

Last Deployment Details

The top area in each Environment Group panel contains details about latest deployments on this Environment Group:

  • Last X Days Deployments
  • Environment (Environment with the most recent deployment)
  • Active Subsystems
  • Inactive Subsystems
  • Last Deployment details (Environment, System, Build, Date, History)

Builds data on the page

If Builds are enabled

If Builds feature is enabled in Customization > Build > Build Setup, then Continuous Delivery Pipeline will display Build #, Build Tag and Build Status instead of the Environment Component’s Summary Version Number.

See Manage Builds for more details.

If Builds are disabled

If Builds feature is disabled in Customization > Build > Build Setup, then Continuous Delivery Pipeline will display Environment Component’s Summary Version Number instead of the Build data.

See Manage Technical Specs and Configuration for more details.

Related Articles

Contents

Be the first to find out about new features. Subscribe to the Release Notes email.

Was this article helpful?

Thanks for your answer!