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
  • Duplicate release pipelines
  • Update release pipelines
  • Update default release pipelines
  • Update other release pipelines
  • Set a default release pipeline
ReleasesRelease pipelines

Managing release pipelines

Was this page helpful?
Previous

Deleting 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.

This topic explains how to duplicate and manage release pipelines.

Duplicate release pipelines

As an alternative to creating a new pipeline, you can duplicate an existing one and edit it to make it unique. This may be faster if you wish to create multiple similar release pipelines.

To duplicate an existing release pipeline:

  1. Navigate to Release assistant. The default release pipeline and its releases appear.
  2. Click the release pipeline name, and select Manage release pipelines. The release pipeline list appears.
  3. Find the release pipeline you wish to duplicate. Select its three-dot overflow menu.
  4. Choose Duplicate. The new release pipeline opens in a new tab. You can identify it because it has the same name as the original release pipeline with (copy) appended to the end.
  5. Modify the new release pipeline as needed.

The release pipeline "Duplicate" option.

The release pipeline "Duplicate" option.

After you create a release pipeline, you can edit any of its information, except for the release pipeline key, until you add releases to it. After you add releases to a release pipeline, you can only edit the pipeline name, description, tags, and phase names. This ensures that all flags are going through the same standardized release process.

Update release pipelines

You can update both the default release pipeline other release pipelines that are not the default.

Update default release pipelines

To update the default release pipeline:

  1. Navigate to Release assistant. The default release pipeline and its releases appear.
  2. Click the release pipeline name, and select Edit release pipeline.
  3. Modify the release pipeline as needed.
  • If there are no releases, you can edit the name, description, tags, phase names, phases, and audiences.
  • If there are releases in the pipeline, you can edit the name, description, and tags.
  1. Click Save release pipeline.

Update other release pipelines

To update a release pipeline that is not the default:

  1. Navigate to Release assistant. The default release pipeline and its releases appear.
  2. Click the release pipeline name, and select Manage release pipelines. The release pipeline list appears.
  3. Find the release pipeline you wish to duplicate. Select its three-dot overflow menu and choose Edit.
  4. Modify the release pipeline as needed.
  • If there are no releases, you can edit the name, description, tags, phase names, phases, and audiences.
  • If there are releases in the pipeline, you can edit the name, description, and tags.
  1. Click Save release pipeline.

Set a default release pipeline

The first release pipeline you create automatically becomes your project’s default release pipeline. If you have more than one pipeline, you can change the default.

To change a default release pipeline:

  1. Navigate to Release assistant. The default release pipeline and its releases appear.
  2. Click the release pipeline name, and select Manage release pipelines. The release pipeline list appears.
  3. Find the release pipeline you wish to make the default release pipeline for this project. Select its three-dot overflow menu.
  4. Choose Make default.

A release pipeline's overflow menu with the "Make default" option called out.

A release pipeline's overflow menu with the "Make default" option called out.

You can also use the REST API: Update a release pipeline