It is possible to maintain multiple versions of a deployment. All versions in a deployment share the same in- and output parameters such that they can be used interchangeably, but the deployed code package, programming language, memory allocation and other settings can differ.
Each version of a deployment is available, meaning that you can make requests to any version of a deployment at any point in time.
Creating a new version of an existing deployment¶
When using the WebApp, a first version is automatically created while creating the deployment. You are able to to add more deployment versions at a later time using UbiOps' deployment versioning system.
In the left navigation bar, click on Deployments. Select the deployment to which you want to add a new version.
Then, click on the Create version button in the versions pane at the top left. The version creation form will appear.
Fill in the version name and the programming language. Please note that the programming language cannot be changed after creating the version. Click on the Upload code button to upload the ZIP file for the new version. The required structure of the ZIP file can be found here.
Other configuration parameters are optional, such as for example the memory allocation. These can be set in the Advanced parameters. As with deployments, you can assign labels to versions to easily filter them later on.
Finally, click on the Create button to create the new version.
Revisions and Building¶
UbiOps maintains a full history of the ZIP packages uploaded to a version, which allows tracking the code that was deployed at any point in time. In the WebApp, navigate to Revisions to see the history of packages.
Each uploaded package triggers a building process, which prepares the deployment code for requests. For more information, click on the expansion button to see the builds of a revision, along with the status and a description of what triggered the build.