# Create and Manage Release Pipelines

## Creating a new pipeline

To create a new Release Pipeline:

1. Log into the [Statsig console](https://console.statsig.com)
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

{% figure %}
![Create release pipeline interface](https://docs.statsig.com/images/release-pipeline/create.png)
{% /figure %}

## 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

{% figure %}
![Phase configuration](https://docs.statsig.com/images/release-pipeline/phases.png)
{% /figure %}

### 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 you use both, the time interval only begins counting down after someone gives the required approval.
:::

{% figure %}
![Phase transition conditions](https://docs.statsig.com/images/release-pipeline/condition.png)
{% /figure %}

## Managing existing pipelines

### Updating a pipeline

To modify an existing pipeline:

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

**Important:** You can't modify pipelines with active rollouts in progress until those rollouts complete or you stop them.

### Viewing pipeline references

There are two ways to see which feature gates and dynamic configs are currently using a pipeline:

1. Project Settings

   * Navigate to Project Settings
   * Click on the Feature Management menu in the left-rail
   * Navigate to Release Pipelines section
   * Click on the **References** column against each Release Pipeline
   * This shows all feature gates and dynamic configs currently attached to a specific pipeline

   {% figure %}
   ![Reference](https://docs.statsig.com/images/release-pipeline/reference.png)
   {% /figure %}

2. Feature Gates / Dynamic Configs Page

   * Navigate to Feature Gates / Dynamic Config list view
   * Filter by 'Release Pipeline' current status
   * This shows all feature gates and dynamic configs with an ongoing release pipeline

   {% figure %}
   ![Feature gates and dynamic configs with release pipeline status](https://docs.statsig.com/images/release-pipeline/create-and-manage/23a3199f-4710-40ed-9bd3-14d2ae5edb49.png)
   {% /figure %}

## Opting out environments from Release Pipelines

By default, all environments trigger Release Pipelines when you make changes. You can configure specific environments to be exempt from this behavior.

When you opt an environment out from Release Pipelines:

* Changes you make exclusively to that environment don't trigger a Release Pipeline.
* Opting an environment out allows quick environment-specific adjustments without starting 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 want to opt out
4. Unselect the **Pipeline-required Environment** option
5. Click **Save** to apply your changes

{% figure %}
![Environment opt-out setting](https://docs.statsig.com/images/release-pipeline/environment-opt-out.png)
{% /figure %}