MultiConnectMultiConnectDocs Website home
MultiConnectCloud › Server Deployments

6. Update and redeploy

Open your deployment from the dashboard: open your project, then the deployment.

  1. Click Update. The same steps as creation open, filled in with the current settings. Mode, Game servers, Platform and the master regions are locked.
  2. Change what you need.
  3. On the Build step choose Keep current build or Upload new build. For Master–Worker, choose for Master build and Worker build.
  4. Leave Rollback on failure ticked unless you want a failed update left in place to inspect.
  5. Click Submit.
You chose What happens
Keep current build everywhere, settings only Settings are saved. If a changed setting needs new containers, the current build is redeployed with them
Upload new build The new build and any setting changes roll out together

Master–Worker builds move together. A redeploy always replaces masters and workers at the same time, so if you upload a new build, upload both the master build and the worker build.

How a redeploy runs

  1. A new generation of containers starts next to the current one.
  2. The platform waits until every new container is healthy. The current generation keeps serving the whole time.
  3. New players go to the new generation.
  4. The old generation is marked as retiring. It keeps serving the players already on it for the Grace Period, then it is removed. See Section 8.

The operation's progress shows on the deployment page: Provisioning, Awaiting healthy, Switching, Draining, then Completed. Rolled back means the new containers never became healthy, and the previous generation is still serving. Only one operation runs at a time, so Update, Scale and Delete are unavailable until it finishes.

To redeploy from a terminal or CI instead, use the MultiConnect CLI. See the CLI Guide.