Creating and Managing Release Pipelines

A Release Pipeline must be defined before it can be used by feature gates or dynamic configs during the rollout process.

Creating a New Pipeline

To create a new Release Pipeline:

1. Log into the Statsig console
2. Navigate to Settings > Feature Management
3. Under Release Pipelines, click the Create button
4. Enter a descriptive name for your pipeline
5. Click Create to proceed to the configuration page

Configuring Phases

Each pipeline consists of one or more phases, with each phase representing a distinct release target.

Adding Phases

For each phase in your pipeline:

1. Add one or more release rules
2. Select a required Environment for the rule
3. Optionally add custom field conditions for more precise targeting

Setting Phase Transitions

Control how your phases progress with these transition options:

Transition Type	Description
Require Review	Requires manual approval from an authorized user before starting the phase
Time Interval	Automatically proceeds to the next phase after a specified duration (in minutes)

Note: You can combine both options in a single phase. When both are used, the time interval will only begin counting down after the required approval is given.

Managing Existing Pipelines

Updating a Pipeline

To modify an existing pipeline:

1. Click on the pipeline name from the list
2. Make your desired edits to any section
3. Click Save to apply your changes

Important: Pipelines with active rollouts currently in progress cannot be modified until those rollouts complete or are aborted.

Viewing References

To see which feature gates and dynamic configs are currently using a specific Release Pipeline:

1. Locate the pipeline in the list view
2. Click on the number displayed in the References column

This will show all features and configs that are currently attached to this pipeline.

Opting Out Environments from Release Pipelines

By default, all environments will trigger Release Pipelines when changes are made. However, you can configure specific environments to be exempt from this behavior.

When an environment is opted out from Release Pipelines:

• Changes made exclusively to that environment will not trigger a Release Pipeline
• This allows for quick environment-specific adjustments without initiating the full release process

How to Opt Out an Environment

To exclude an environment from triggering Release Pipelines:

1. Navigate to Settings in the Statsig console
2. Under Keys & Environments, select Environments
3. Click on the environment you wish to opt out
4. Unselect the Pipeline-required Environment option
5. Click Save to apply your changes