ReaperCI Documentation

ReaperCI documentation

Deployment comparison

ReaperCI can compare any two deployments from the same repository. The result uses the immutable release inputs captured when each deployment was requested, so later runtime drift does not rewrite release history.

The comparison covers:

  • commit and source ref;
  • environment, server target, and deployment strategy;
  • image, container, Compose path, and Docker run arguments;
  • health-check URL, timing, failure threshold, and automatic rollback policy.

Open Deploys > Compare deployments, choose the target and baseline, and review the changed fields before approving a promotion or confirming a rollback.

The same read-only operation is available to automation:

reaperci deploys compare 18 --base 17
  • REST: GET /api/v1/deployments/18/compare/17
  • MCP: reaperci_deployment_compare with targetId and baseId

Cross-repository comparisons are rejected because they can present unrelated services as if one were a release of the other. Deployment credentials and environment secret values are never included in the comparison response.