For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Sign inTry it free
DocsGuidesSDKsIntegrationsAPI docsTutorialsFlagship blog
DocsGuidesSDKsIntegrationsAPI docsTutorialsFlagship blog
  • Get started
    • Overview
    • Onboarding
    • Get started
    • Launch Insights
    • LaunchDarkly architecture
    • LaunchDarkly vocabulary
  • AgentControl
    • AgentControl
    • Manage AgentControl
  • Feature flags
    • Create flags
    • Target with flags
    • Flag templates
    • Manage flags
    • Code references
    • Contexts
    • Segments
  • Releases
    • Releasing features with LaunchDarkly
    • Release policies
    • Percentage rollouts
    • Progressive rollouts
    • Guarded rollouts
    • Feature monitoring
    • Release pipelines
      • Creating release pipelines
      • Adding and removing flags from release pipelines
      • Managing release pipelines
      • Deleting release pipelines
    • Engineering insights
    • Release management tools
    • Applications and app versions
    • Change history
    • Restoring previous flag versions
  • Observability
    • Observability
    • Session replay
    • Error monitoring
    • Logs
    • Traces
    • Observability metrics
    • Product analytics events
    • LLM observability
    • Alerts
    • Dashboards
    • Service map
    • Vega for auto-remediation
    • Observability MCP server
    • Search specification
    • Observability settings
    • Observability integrations
  • Experimentation
    • Experimentation
    • Experiment metric types
    • Experiment configuration
    • Managing experiments
    • Analyzing experiments
    • Multi-armed bandits
    • Holdouts
  • Metrics and events
    • Metrics in LaunchDarkly
    • Creating metrics
    • Metric groups
    • Events
    • Autogenerated metrics
  • Warehouse native
    • Warehouse native metrics
    • Setting up external warehouses
    • Creating experiments using warehouse native metrics
  • Infrastructure
    • Connect apps and services to LaunchDarkly
    • LaunchDarkly in China and Pakistan
    • LaunchDarkly in the European Union (EU)
    • LaunchDarkly in federal environments
    • Public IP list
  • Your account
    • Projects
    • Views
    • Environments
    • Tags
    • Teams
    • Members
    • Roles
    • Account security
    • Feature previews
    • Billing and usage
    • Changelog
Sign inTry it free
LogoLogo
On this page
  • Overview
  • Release strategies
  • View release pipelines
Releases

Release pipelines

Was this page helpful?
Previous

Creating release pipelines

Next
Built with
Release pipelines are in beta

Release pipelines are in beta, and are available only to certain customers with an Enterprise or Guardian plan. Aspects of this feature may change without notice or become deprecated in favor of other release management features.

Overview

This topic explains how you can use LaunchDarkly’s release assistant capabilities, including release pipelines, to standardize and automate the release process for your feature flags. Release pipelines let you move flags through a series of phases, rolling out flags to selected environments and audiences following automated steps. This combination of release pipelines and automated steps is called Release assistant in the LaunchDarkly user interface.

Release strategies

You can set up one or more release strategies for each phase, determining:

  • The environment to roll out to
  • The audience to roll out to within the environment, including either everyone, or only selected segments
  • Whether approvals are required
  • Whether to release immediately, or use a guarded rollout to roll out gradually and prevent regressions

When you add a flag to a release pipeline, LaunchDarkly automatically performs the actions you set up as the flag moves through each phase.

Automated releases is available for boolean flags only

JSON, string, and number flags cannot be added to a release pipeline.

View release pipelines

Expand Release in the left navigation, then click Release assistant to view the default release pipeline within a project:

The default release pipeline. This one is named "Primary release pipeline."

The default release pipeline. This one is named "Primary release pipeline."

Each project can have up to 20 release pipelines.

Click the dropdown menu with the release pipeline name and choose Manage release pipelines to view the list of release pipelines within a project:

The "Release pipelines" list.

The "Release pipelines" list.

You can also use the REST API: Get all release pipelines, Get release pipeline by key

When a flag is included in a release pipeline, you can view each phase in the pipeline in the flag’s right sidebar.

To see the steps required for each phase, click the expand arrows for the phase:

An expanded phase in a release pipeline in a flag's sidebar with the expand arrows called out.

An expanded phase in a release pipeline in a flag's sidebar with the expand arrows called out.

You can also use the REST API: Get release for flag

Release pipelines are one of several options that LaunchDarkly provides to help you release features to production safely and gradually. To learn more about options for releasing features gradually and safely, read Releasing features with LaunchDarkly.

To learn how to create, manage, and delete release pipelines, read the topics in this category:

  • Creating release pipelines
  • Adding and removing flags from release pipelines
  • Managing release pipelines
  • Deleting release pipelines