A/B Deployment Manually
Last updated
Last updated
A/B deployment is an update process whereby you deploy new versions of your game servers alongside your already existing game servers.
We have a with 1 ApplicationBuild in its .
This chapter assumes you already have created a new for your updated software.
create a new GameDeploymentTemplate with the new ApplicationBuild ID.
create the new Fleet (based on the old one).
start sending the first updated clients to the game servers running the new build in the new Fleet (e.g. a group of testers).
if there is something wrong, downgrade those clients and send everyone back to the old build in the old Fleet. You can remove the new Fleet if you want to destroy all the game servers running the new build.
if all went well, update all your clients and send those to the game servers running the new build.
eventually all clients are migrated. The old Fleet can be removed.
We need to get the Fleet object so that we can create a new one, based on this old one.
Before we create the new Fleet, first create a new GameDeploymentTemplate with your new ApplicationBuild ID, which can be used in the new Fleet.
Now we can create the new Fleet based on the old Fleet, with the new GameDeploymentTemplate.
New game servers will be deployed now, for this new Fleet and you can start sending your first clients to them.
If you spot errors with the new game servers, you could revert the creation of the new Fleet and GameDeploymentTemplate. Or you can leave them to use for later with a new build containing any fixes.
When everything is going well with the new game servers and once all clients have migrated to the new version, remove the old fleet.
If you do not know your Fleet ID yet, you can look it up by using .
If you do not know your new ApplicationBuild ID yet, you can look it up by using .
Set the new Fleet's property to 2 (Automatic scaling enabled) to have the platform start deploying new game servers for it.