Deploy, stop, retry and roll back
Start a deployment from Git, stop one that is running, retry one that failed, and roll back to the previous release.
On this page
Before you start
- You are an owner, or your role has the permission for the action: Create Deployments, Stop Deployments, Retry Deployments or Rollback Deployments.
- The site has a repository connected: see Connect a repository.
- Each environment has its own deployments: choose Production or Staging in the site header first.
Deploy
Choose what to deploy
Go to Managed Websites, choose the site, then Deployments under Code & backups. On the Deployments card, leave the box empty to deploy the head of the branch, or enter a branch, tag or commit.
Start the deployment
Choose Deploy beside the box. Deploy in the site header deploys the head of the branch, and asks you to confirm first.
The deployment joins the top of the list as Running. When it reads Succeeded it is the site's Current release.
Stop a running deployment
Stop the deployment
Choose Stop on the Running row, then Stop again to confirm.
The site stays on its current release. While a deployment runs, Deploy and Roll back wait until it finishes.
Retry a failed deployment
Retry the deployment
Choose Retry on the Failed row, then Retry to confirm.
The same commit is built and deployed again. When newer code has been deployed since, the dialog warns that the retry puts an older release live: push a fix and deploy that instead.
Roll back
Roll back the release
On the Current row, choose Roll back to #857 (the button names the previous release), then confirm.
A roll back does not change the database. If the release you are leaving added tables or options, check the site afterwards.
The site points at the previous release straight away: nothing is rebuilt and uploads are untouched. Only the previous release can be rolled back to.
A deployment whose archive was removed after 30 days cannot be retried or rolled back to: deploy the branch or commit again.
Automate this
Deploys the connected branch, or the branch or commit named in ref, and answers the new deployment with status queued.
curl -X POST https://manage.corefinity.com/api/corestack/sites/1042/deployments \
-H "Authorization: Bearer $COREFINITY_TOKEN" \
-H "Accept: application/json" \
-H "Content-Type: application/json" \
-d '{}'Your assistant calls corestack_deployment_trigger.
{
"name": "corestack_deployment_trigger",
"arguments": {
"site_id": 4211,
"ref": "main"
}
}