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
  • Add flags to release pipelines
  • Begin phases
  • Move flags between release pipelines
  • Remove flags from release pipelines
ReleasesRelease pipelines

Adding and removing flags from release pipelines

Was this page helpful?
Previous

Managing 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 to add, remove, and move flags between existing release pipelines.

After you have created a release pipeline, you are redirected to the releases view to add your first flags to the pipeline. You can add only boolean flags to release pipelines.

Add flags to release pipelines

To add a flag to a release pipeline:

  1. From the flags list, navigate to the boolean flag you want to add to a release pipeline.
  2. Click Start release in the right sidebar. If there is more than one release available, select the release you want to add the flag to.

The "Start release" option.

The "Start release" option.

The release appears in the right sidebar.

You can also use the REST API: Create a new release for flag

Begin phases

After you have set up the automation for each of your phases, you can begin a phase for an individual flag. This activates the automation within that phase for that flag.

To begin a phase for a flag:

  1. From the flag’s right sidebar, find the phase you want to begin.
  2. Click the start arrow for the phase. A “Start phase” dialog appears
  3. Click Start.

Release pipelines run the following automated steps when you start the phase for a flag:

  • If the phase includes an approval, starting the phase sends an approval request to toggle the flag on. When the approval request is approved and applied, then LaunchDarkly automatically toggles the flag.
  • If the phase includes a guarded rollout, starting the phase automatically begins the monitoring process for the traffic allocation and duration specified in the phase.

When the phase is complete, the next phase in the release pipeline is marked as “Ready to start.”

A release pipeline's phases in a flag's sidebar.

A release pipeline's phases in a flag's sidebar.

When you’re ready for the flag to move through the next phase, click the start arrow for that phase.

Each time a flag begins or completes a phase, anyone following the flag receives an email notification and, if you have the Slack integration configured, a Slack notification.

You can also use the REST API: Update phase status for release

Move flags between release pipelines

If a flag is already assigned to a release pipeline, you can move it to another pipeline.

To move a flag:

  1. From the flag’s right sidebar, click the three-dot overflow menu for the release.
  2. Hover over Move to pipeline and select the release you want to move the flag to.
  3. Enter the name or key of the release to confirm.
  4. Click Move.

Remove flags from release pipelines

To remove a flag from a release pipeline, navigate to the flag’s right sidebar, click the three-dot overflow menu for the release, and then click Cancel release.

You can also use the REST API: Delete a release for flag