Skip to main content

​
Prepare the release

From your local project directory, target an existing running workspace. If it is inactive, start it explicitly with rig workspace start --workspace my-project and wait until it is running before submitting the release. Incremental deployment and activation stop with a warning instead of starting it or queuing the action for later. Then prepare the release:
With incremental deployment, --sync-only prepares a managed release and leaves it ready for explicit activation. It does not merely copy files over the running app. Wait for preparation to finish and identify the ready release ID.

​
Review preparation logs

Check dependency installation, build output, and the intended application set. A ready release has not yet passed the running service’s activation health check.

​
Activate and verify

Activation briefly restarts affected applications and checks them. Verify the returned release state and each app’s health. Do not use a failed or already superseded release as though it were ready; inspect history and stage again if necessary. To restore a retained release after an unsuccessful change, follow app rollback. Image deployment uses different staging semantics; do not combine incremental staging with --bluegreen, --promote, --build-only, or --reimage.