---
title: 'Continuous integration'
description: 'Run the CLI without interactive login and verify schema deployment.'
---

# Continuous integration

Use a secret-backed token in a trusted CI environment. Pin the CLI and application dependency versions through your package manager and lockfile.

```bash
flexkit --token "$FLEXKIT_TOKEN" --local-config ./flexkit.config.ts deploy
```

Store `FLEXKIT_TOKEN` in the CI secret store. Do not print it or enable shell tracing around credential-bearing commands. The [global options](/docs/cli/global-options) reference describes accepted CLI authentication and configuration selection.

## Pipeline order

1. Install locked dependencies.
2. Validate and build the application configuration and examples.
3. Check the intended project selection and migration/export requirements.
4. Deploy the schema and fail the job when deployment fails.
5. Deploy the application and its server environment.
6. Run a bounded read and verify tool discovery where applicable.

Separate development and production credentials. A successful application build does not establish that the target project schema was deployed. Avoid concurrent schema deployments to the same project from unrelated jobs.

See [deployment](/docs/deployment) and [schema migrations](/docs/schema/deployment-and-migrations).


---

[View full sitemap](/docs/sitemap.md)