> ## Documentation Index
> Fetch the complete documentation index at: https://docs.paradime.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Migrate Turbo CI from --target flags to a CI environment

> Move your Turbo CI schedule from appending --target ci on every command to a dedicated CI environment with its own connection, and clean up your commands.

Before Paradime supported multiple Bolt [environments](/products/settings/connections/index#create-and-manage-environments), a workspace had a single Bolt connection. Turbo CI runs selected the `ci` warehouse target by appending `--target ci` to every dbt™ command in the schedule.

With environments, the Turbo CI schedule runs in a **dedicated CI environment** whose connection already uses the `ci` target. The environment carries the connection and target, so your commands stay clean and there is nothing to forget when you add a new command to the schedule.

**Before**

```yaml theme={"system"}
schedules:
  - name: turbo ci run
    slug: turbo-ci-run-t1u2v3
    environment: production
    commands:
      - dbt build --select state:modified+ --target ci
```

**After**

```yaml theme={"system"}
schedules:
  - name: turbo ci run
    slug: turbo-ci-run-t1u2v3
    environment: tagging-iguana-qhhi5i   # your CI environment's slug
    commands:
      - dbt build --select state:modified+
```

## Step 1: Create the CI environment

1. Go to **Settings > Environments** and open the **Bolt** section.
2. Click **Create environment** and name it, for example, `ci`.

The new environment appears below your default environment with its own slug shown next to the name. You will need this slug for YAML-defined schedules.

## Step 2: Add a connection with the ci target

1. On the new environment, click **Add connection**.
2. Use the same warehouse and credentials as your existing Bolt connection (or dedicated CI credentials if you have them).
3. Set the **target name** to `ci` and keep the default schema you used with the old `--target ci` setup.

Setting the target to `ci` matters: your `generate_schema_name.sql` macro keys on `target.name == 'ci'` to build into the temporary `paradime_turbo_ci_pr_` schema. The macro needs no changes. See [Configure a custom schema for CI runs](/products/bolt/ci-cd/turbo-ci/index#configure-a-custom-schema-for-ci-runs).

## Step 3: Point the Turbo CI schedule at the environment

* **UI-managed schedules**: open the schedule, go to [Schedule settings](/products/bolt/creating-schedules/schedule-settings), and set **Environment** to the CI environment.
* **YAML-managed schedules**: set `environment:` to the CI environment's slug in `paradime_schedules.yml`. The slug is shown next to the environment name in **Settings > Environments**.

## Step 4: Remove --target ci from the commands

Delete the `--target ci` flag from every command in the schedule. The environment's connection now supplies the target, so `dbt build --select state:modified+ --target ci` becomes `dbt build --select state:modified+`.

## Step 5: Verify with a test pull request

1. Open a small test pull request so your CI provider triggers the Turbo CI schedule.
2. In the run details, confirm the run used the CI environment and that models built into a `paradime_turbo_ci_pr_` prefixed schema.
3. Merge or close the test PR.

<Info>
  Migrate incrementally if you prefer: `--target ci` keeps working as before, and a command-level `--target` flag simply overrides the connection's target. Move the schedule to the CI environment first, confirm a green run, then strip the flags.
</Info>

The same pattern applies beyond CI: any schedule that appends `--target` flags to select a different warehouse target (for example a staging build) can instead run in its own environment with a dedicated connection.

## Related

* [Turbo CI setup](/products/bolt/ci-cd/turbo-ci/index) for the full CI configuration, including the schema macro and provider pipelines
* [Create and manage environments](/products/settings/connections/index#create-and-manage-environments) for environment lifecycle and per-environment connections
* [Configuration reference](/products/bolt/creating-schedules/schedules-as-code/configuration-reference#base-configuration) for the `environment` field in YAML schedules


## Related topics

- [Turbo CI for dbt™ pull requests](/products/bolt/ci-cd/turbo-ci/index.md)
- [Turbo CI with Snowflake shared databases](/products/bolt/ci-cd/turbo-ci/snowflake-shared-databases.md)
- [Migrate dbt™ jobs from GitHub Actions to Paradime Bolt](/guides/migrations/migrating-dbt-tm-jobs-from-github-actions-to-paradime-bolt.md)
- [Turbo CI Schema Cleanup macro for dbt™](/products/bolt/ci-cd/turbo-ci/paradime-turbo-ci-schema-cleanup.md)
- [Migration Playbook](/guides/migrations/dbt-cloud-tm-importer/migration-from-dbt-cloud-playbook.md)