Deployment Actions

Various actions can be taken on Deployments from within the Service -> Deployments tab and clicking on the three dots at the end of a previous deployment.

Redeploy

A successful, failed, or crashed deployment can be re-deployed by clicking the three dots at the end of a previous deployment.

This will create an new deployment with the exact same code and build/deploy configuration.

Note: To trigger a deployment from the latest commit, go to settings tab and click Deploy Changes button. This will deploy the latest commit from the Default branch in GitHub.

Currently, there is no way to force a deploy from a branch other than the Default without connecting it in your service settings.

Build and Redeploy

This option goes beyond simply redeploying your application—it rebuilds everything from the ground up. Unlike a regular Redeploy, which just reuses the last successful build and deploys it again with the same configuration, Build and Redeploy ensures that your dependencies, configurations, and environment variables are freshly processed, reducing the chances of running into outdated or mismatched components.

Rollback

Rollback to previous deployments if mistakes were made. To perform a rollback, click the three dots at the end of a previous deployment, you will then be asked to confirm your rollback.

A deployment rollback will revert to the previously successful deployment. Both the Docker image and custom variables are restored during the rollback process.

Stop Deployment

Users can Deployments in progress by clicking the three dots at the end of the deployment tab and select Abort deployment. This will stop the deployment in progress.

Restart a FAILED Deployment

When a Deployment is FAILED, it is no longer running because the underlying process exited with a non-zero exit code - if your deployment exits successfully (exit code 0), the status will remain Success.

CloudStation automatically restarts crashed Deployments up to 10 times (depending on your Restart Policy). After this limit is reached, your deployment status is changed to FAILED and notifying webhooks & emails are sent to the project's members.

Restart a FAILED Deployment by visiting your project and clicking on the "Restart" button that appears in-line on the Deployment:

Restarting a crashed Deployment restores the exact image containing the code & configuration of the original build. Once the Deployment is back online, its status will change back to Success.

You can also click within a deployment and using the Command Palette restart a deployment at any state.

Pausing and Activating Your Application

You can pause and resume your application based on its current state. If your application have Application Active status, you have the option to Pause Application it, which temporarily suspends all running services without deleting any data or configurations. This can be useful for reducing resource consumption or temporarily disabling an application without fully redeploying it later.

Similarly, if your application is in the Application Paused state, you can Activate it again, restoring all services and making the application fully operational. This allows for a seamless transition between paused and active states without losing any progress or settings.