Enterprise Deployment Guide

Pipeline Architecture

Walk through the enterprise CI/CD workflow from pull request validation to zero-downtime bundle reload.

Edit this page on GitHub

Pipeline Architecture

An enterprise deployment of Rescile treats infrastructure as immutable code.

The CI/CD Workflow

  1. Pull Request: A team proposes a change to an asset CSV or a model TOML in Git.
  2. Validation: CI runs rescile-ce diff to generate an impact analysis of the changes. The PR shows exactly which resources will be added, removed, or modified.
  3. Merge: The PR is approved and merged into the main branch.
  4. Build: The Rescile Importer fetches the new main branch, builds the graph, and packages rescile-bundle.tar.gz.
  5. Publish: The bundle is uploaded to the S3 Registry.
  6. Reload: Webhooks trigger the Rescile Controller and MCP fleets to hot-reload the new bundle from S3 without downtime.

Pull vs Push

The stateless serving fleets pull the artifact from S3 rather than having data pushed directly to them. This ensures horizontal scalability—newly spawned instances in an Auto-Scaling Group instantly pull the latest bundle and become ready to serve traffic.

Enterprise Portal Integration

The Rescile Portal can stream prebuild sessions, allowing users to validate branches locally before committing to the remote Git repository, shifting validation to the very left of the pipeline.