Stage and deploy a change
A change reaches your sites in two steps: stage, then deploy. Staging needs the Stage permission and deploying needs Deploy; see who can stage and deploy.
1. Save your changes
Section titled “1. Save your changes”Make your edits on their own screens and save them. Each save changes the draft only.
2. Stage the draft
Section titled “2. Stage the draft”Open Delivery › Deployments › Versions. The Preview band above the log shows what is staged:
- the version number it will get, for example
#48; - who staged it and how long ago;
- each changed record;
- how many warnings the gate found, if any.
EdgeKit stages automatically about 30 seconds after the last saved change, or after at most 5 minutes while changes keep arriving. An automatic stage shows staged by Automatic staging.
To stage now, select Stage the draft, or Re-stage the draft when a preview already exists. The result appears below the band:
| Message | What happened |
|---|---|
| Staged. n behavioural, n presentational, n added, n removed. | The preview was replaced with the current draft. |
| Staged. Nothing has changed since the last deployment. | The preview matches the live version. |
| The gate refused this draft. Nothing was staged. | One or more checks failed. Each failure is listed with where it was found. Any earlier preview stays as it was. |
Fix every listed failure in the draft and stage again.
3. Review the preview
Section titled “3. Review the preview”Read every change in the band, including changes other people made: the deploy ships all of them. Hover over a
change to see its kind (feature, product, site and so on), what happened to it (new, removed, or its version move
such as v3 → v4) and whether it is behavioural or presentational only. A presentational-only change keeps its
number, such as v3 → v3.
The gate only checks that the draft is well formed. It does not tell you how many users get a different outcome. For each behavioural change, work out who it affects before you deploy.
4. Deploy
Section titled “4. Deploy”Select Deploy #48 (the button names the preview’s version). The console answers Deployment #48 is live., the preview band empties, and the new version is marked Live in the log.
The button is disabled when:
- your role does not have the Deploy permission;
- the band says a deployment landed since — stage again. Another version reached the log after this preview was staged, so the preview no longer shows what would change. Select Re-stage the draft and review again.
When a deploy is refused
Section titled “When a deploy is refused”| Message | Cause | What to do |
|---|---|---|
| Nothing is staged. Stage the draft first. | There is no preview. | Stage the draft. |
| This was staged against deployment n and the tenant is now on m. Stage again. | A version was added after this preview was staged. | Stage again and review the new preview. |
| Another deployment landed while this one was being written. Stage again. | Two deploys ran at the same moment and the other one won. | Stage again and review the new preview. |
| The tenant did not answer. Nothing was changed. | EdgeKit could not reach your organization’s data. | Try again. Nothing was deployed. |