CI/CD
Deploy from automated workflows using Git integration or the Easel CLI.
Easel can deploy automatically from Git or explicitly from a CI system with the CLI.
Choose a deployment model
Use Git deployments when repository events should be the source of truth. Use CLI deploy when another system controls release orchestration, generated source, or prebuilt output.
Avoid configuring both paths to deploy the same commit unintentionally.
Authentication
Authenticate non-interactive jobs with EASEL_TOKEN or --token. See
CLI authentication.
Do not print the token or include it in build artifacts.
Preview deployment
Link the project, then create a Preview deployment:
Production deployment
Create a Production deployment explicitly and promote it according to the project's release policy:
Do not assume a Production build is already receiving production traffic when auto-assignment is disabled. See Production releases.
Deployment checks
Before promotion, run checks against the immutable deployment URL:
- Health and smoke tests
- Authentication flows
- Critical API routes
- Cache and header validation
- Database connectivity
- Browser tests
Concurrency and cancellation
Cancel superseded builds where supported. Serialize production promotion to avoid an older workflow assigning traffic after a newer workflow.
Monorepos
Use changed-path detection carefully and include shared packages, lockfiles, and root configuration in each application's dependency set. See Monorepos.