Release pipeline migration guide

Overview

This guide describes how to migrate from legacy release pipelines to fully automated release pipelines.

To learn more, read Release pipelines.

About release pipelines with automation

In May 2024 LaunchDarkly introduced release pipelines with automation.

With release pipelines with automation, you can now:

• specify audiences to roll out to in each phase
• roll out either immediately, or with a guarded progressive rollout
• require an approval to begin rollouts in each phase

This is a significant transition from the way legacy pipelines are used. With this change, you will no longer need to manually progress a flag through a release pipeline.

Upgrade to release pipelines with automation

If you are using a legacy release pipeline and want to upgrade, you will need to complete two steps:

1. Create and configure a new release pipeline with automation. To learn how, read Creating release pipelines.
2. Complete or remove outstanding releases on your legacy pipeline. To learn how, read Remove flags from release pipelines.

Close out legacy pipelines

After you have created your new automated pipeline, if you still have flags in legacy pipelines, you can either:

• Complete the flags' progression through the legacy pipeline before the end of June.
• Move the flags to a new automated pipeline. To learn how, read Move flags between release pipelines.
• Cancel the legacy release. To learn how, read Remove flags from release pipelines.

As of May 21, 2024:

• You can no longer add new flags to legacy pipelines.
• You can no longer edit legacy pipelines.
• You can no longer change your default release pipeline to a legacy pipeline.
  • If you have a legacy pipeline as your default release pipeline, you can continue to use it as your default. When you create your first new automated pipeline, it will become the default.
• You can duplicate your existing pipeline to turn it into an automated pipeline. To learn how, read Duplicate release pipelines.