Flow supports deploying artifacts to public hosts. Learn how to connect to hosts and deploy them.
Overview
Connect to a new host
On the homepage of Flow, click Global Settings.
On the left-side navigation bar, select Host Group Management.
Select the target host group and click Add New Host.
Select Manually Install Runner. This works for both Alibaba Cloud ECS and non-Alibaba Cloud hosts.
Copy the Runner installation command and execute it on the new host. You need to make sure the host have access to the Internet.

When the following information appears in the host terminal, the connection is established. Refresh the host list page to check that the host is added.
INFO[2025-04-29T13:34:12+08:00] service type linux-systemd, user , realUser root
INFO[2025-04-29T13:34:12+08:00] Aliyun yunxiao runner-v0.3.1-be-d5zh**** service started
INFO[2025-04-29T13:34:12+08:00] Aliyun yunxiao runner-v0.3.1-be-d5zh**** service status running Create a host deployment job
Two methods are available:
Create through a pipeline template
On the Flow homepage, navigate to My Pipelines.
Click Create Pipeline.
Select a pipeline template with a Host Deployment job

Create when building a pipeline
On the Flow homepage, navigate to My Pipelines.
Select a pipeline by clicking its name.
Click Edit.
On the Process Configuration page, click Create Job
In the panel that appears, navigate to Deploy
Select VM Deploy.

Configure a host deployment job
This section takes the deployment of Java sample code as an example to show how to configure a deployment job. Make sure to upload the deploy.sh file to the artifact repository as it is required later for deploying the Java code.
Keep Download Artifacts During Deployment selected. (Selected by default. Do not deselect it.)
Select an naming format of Artifact.
Select an Host Group. (Click New Host Group to create one if no group exists.) Hosts in the host group must have Java runtime environment installed.
Fill in the following items in Deployment Configuration:
Artifact Download Path: The path on your host where the artifacts will be downloaded.
Execute User: The user allowed to execute the commands.
Deploy Script:
# In this example, to deploy the sample code, just extract and execute the package. mkdir -p /home/admin/application tar zxvf /home/admin/app/package.tgz -C /home/admin/application/ sh /home/admin/application/deploy.sh restartdeploy.sh is a shell script that starts a JAR package. Replace it with your own deployment script in practice.
ImportantDuring the deployment, Flow will initiate deployment processes that start with
rdc_deploy_command_. Do not operate on these processes in your deployment script, or the deployment may fail.
Configure the Deployment Strategy. Flow supports staged deployment.
Pause Strategy
FirstBatchPause: The deployment procedure pauses upon the completion of the first batch, waiting for your confirmation to deploy the rest.
No Pause: Upon completion of a batch, the subsequent batch is executed automatically without pausing for your confirmation.
EveryBatchPause: The deployment procedure pauses upon the completion of each batch, waiting for your confirmation to deploy the next one.
Batch Number: The hosts will be deployed in batches based on the specified number. For example, if you have 4 hosts and choose to deploy in 2 batches, each batch will automatically deploy to 2 hosts.

See Environment variables configuration if required in deployment.
Manage host deployment jobs
View deployment details
After configuring the deployment job, run the pipeline to deploy the artifacts to the specified host group. Click Deployment Order Details to view the latest deployment status.

Deployment status | Available operations |
Deploying |
|
To be deployed | No operation is available in this stage. |
Completed |
|
Failed |
|
Skipped |
|
Roll back to a historical deployment
In the Deployment History, Roll Back to the target historical deployment.
Flow will re-run historical deployment script and re-build artifacts based on the history to achieve the rollback.

Deployment artifacts have a 30-day retention period. Rollbacks to deployments older than 30 days are not allowed.