Pipeline execution relies on a build cluster to complete compilation and packaging. Flow provides a default build cluster to initiate CI/CD. It also allows enterprises to set up self-hosted custom clusters.
Default build cluster of Alibaba Cloud DevOps
On the homepage of Flow, navigate to , and you will see the default build cluster -Singapore build cluster.
Each build job is placed on a container. The container will be reclaimed when the job is completed.
The image of the build environment is configurable. You can use official common images or your own image.
The build environment allows you to configure the specifications with the following options: SMALL_1C2G, MEDIUM_2C4G, LARGE_4C8G, XLARGE_8C16G.
If dependent services have enabled whitelists, add the following Flow build machine IP addresses to the whitelist:
Flow service public IP addresses |
|
Public IP addresses of Flow Singapore build cluster |
|
Self-hosted build cluster
Flow supports self-hosted build clusters. Alibaba Cloud ECS or other self-owned hosts can be integrated into the build cluster. And Flow uses containerized building. That means pipeline jobs are placed randomly to instances of the build cluster, and are being executed.
Preparation before integrating an instance to a build cluster
Ensure that the instance meets the following requirements:
Can access the public network (to install Runner and get callbacks from it; download pipeline build job dependency and get callbacks.)
Operating system architecture:
Linux
Distributions: CentOS 6+ or later, Ubuntu 16.04+ or later, Alibaba Cloud Linux 2/3.
Architecture: Linux/amd64, Linux/arm64.
Recommended configuration: 4 cores 8G and above.
Build environment: Default VM Environment.
Windows
Versions: Windows 2012, Windows 2016, Windows 2019, Windows 2022.
Architecture: Windows/amd64 architecture.
Build environment: Default VM Environment.
macOS
Versions: macOS Sonoma(14.0), macOS Ventura(13.0), macOS Monterey(12.0).
Architecture: macOS/amd64, macOS/arm64.
Build environment: Default VM Environment.
Create a self-hosted build cluster
On the homepage of Flow, navigate to .
Fill in the form.
Click OK to create a new build cluster.
Integrate an instance to the build cluster
On the homepage of Flow, navigate to
Find the target build cluster, and click to enter the details page.
Click Connect to a new node.
Integrate a Linux instance
Install Runner to integrate a Linux instance:
Copy Runner installation commands on the page and execute it on the instance to be connected.
When Runner is installed, the instance will be automatically integrated to the current cluster. Refresh the host list to check.
Integrate a Windows instance
Install Runner to integrate a Windows instance:
Open PowerShellCopy.
Execute Runner installation commands with admin role on the instance to be integrated.
When Runner is installed, the instance will be automatically integrated to the current cluster. Refresh the host list to check.
Integrate a macOS instance
Execute Runner installation commands on the instance to be integrated.
When Runner is installed, the instance will be automatically integrated to the current cluster. Refresh the host list to check.
Manage the build cluster
Go to , find the target build cluster and click to go to the details page. You can:
View the details of the build cluster. A list displays instance ID, IP, hostname, operating system/architecture, usage, Runner status, and installation progress in this page.
Reinstall Runner: If the Runner malfunctions, reinstall it.
Remove instance: Unbinds the instance from the build cluster. Will not delete the actual instance or uninstall the Runner on it.
Manage the build cluster: Change its name, tags, etc.
Delete the build cluster: Unbinds instances and deletes the data of the build cluster. Will not delete actual instances or uninstall Runners.
Use the self-hosted build cluster
Enter the target pipeline editing page and select the self-hosted build cluster created by the enterprise. When the pipeline runs, jobs will be randomly placed to an instance and the corresponding container environment will be prepared for job execution. The build duration and concurrent jobs of the self-hosted build cluster are not counted in the enterprise build quota.
When using a self-hosted build cluster's build environment, during job execution, the pipeline job build environment is placed to the user. And the user can customize the job execution script.