You can deploy the same project again, and you can deploy a different version of it. In both cases you use the deploy flow from the projects catalog. Refer to Deploying a Project for the full deploy flow.
Every deploy action creates a new deployment. The Control Hub does not update a running deployment in place, so deploying a project again does not overwrite an existing deployment. Instead, you get an additional, separately named deployment that you monitor and manage on its own.
Deploying a Different Version
To deploy another version of a project, select the project in the catalog. Open the version selector in the project header and select the version you want. Then use the Deploy option. Select the environment and a deployment name, then click Deploy in the dialog.
The version you pick in the header is the version that is deployed. Refer to Inspecting the Project Details for more information on the version selector.
Redeploying a Project
If you want to deploy the same project but, for example, in another environment or under a different name, repeat the deploy flow for the same version.
A deployment name must be unique within an environment. If a deployment with the proposed name already exists in the selected environment, the Control Hub appends a number, for example myproject-2. Keep the suggested name or enter a name of your choice.
Checking Existing Deployments
Before you deploy a project again, check where it already runs so you do not create a deployment you do not need.
The Deployments tab on the project detail page lists the existing deployments of the project, with their environment, version, and status, so you can see where it already runs before you deploy it again:
Refer to Inspecting the Project Details for more details on the Deployments tab, and to Working With the Deployments View for more information where to manage your deployments.