This topic describes how to view build resource usage and details for Alibaba Cloud DevOps Flow.
Prerequisites
To view resource usage and details, an organization owner must grant you the Resource Usage permission:
-
On the Flow homepage, the organization owner clicks Global Settings.
-
Navigate to , find the role that requires the permission, select the Resource Usage checkbox, and save the changes.
Resource usage
On the Flow homepage, click Resource Usage. On this page, you can view the number of build concurrent jobs, resource quotas, and usage information for your organization. (For detailed subscription information, go to the organization's page. For more information, see Subscription Information.)
-
Build concurrent jobs
-
The number of build concurrent jobs refers to the total number of tasks running simultaneously across all pipelines in your organization. Only tasks that use a public build cluster are counted. This count excludes tasks that use a private build cluster.
-
When your organization reaches its limit for concurrent jobs, new jobs are queued until earlier jobs finish or are canceled. To enable elastic scaling for concurrent jobs, you can activate pay-as-you-go or purchase the Advanced Edition.
-
-
Build core minutes
-
Build core minutes are the sum of core minutes consumed by all pipeline tasks in your organization. This includes Flow pipeline tasks, Codeup code scan tasks, and AppStack tasks. Only tasks that use a public build cluster contribute to this calculation; tasks that use a private build cluster are excluded.
-
The unit for build resources is the core minute. The formula is: build core minutes = Build duration (minutes) × Number of CPU cores × Cluster coefficient. The cluster coefficient is 1 for clusters in the China (Beijing) and China (Hangzhou) regions, 2 for the China (Hong Kong) region, and 0.8 for a hosted VPC. Alibaba Cloud DevOps uses this coefficient to standardize unit prices, as build costs vary by region.
-
If your organization exceeds its monthly quota for build core minutes, new pipeline tasks will fail. To get unlimited resources, you can activate pay-as-you-go.
On the Resource Usage page, the left-side panel displays the current number of concurrent jobs, the maximum concurrent job limit, and your monthly build core minute usage compared to your available quota. If you exceed the quota, the progress bar turns red and displays a warning icon. The main area contains the Build Usage Statistics chart and the Build Usage Details table. The chart displays daily usage (bar chart) and cumulative monthly usage (line chart), and can be filtered by pipeline, unit, or month. The details table includes columns such as Pipeline ID, Pipeline Name, Run Record, Task, Build Duration, Build Cluster, Coefficient, and Number of CPU Cores. Use this data to verify the core minute calculation.
-
Build usage statistics
Open the Flow homepage and click Resource Usage to view the build usage statistics. You can view the monthly build resource consumption of the current organization by calendar month.
-
Horizontal axis: Date, in days.
-
Vertical axis: Build resource usage. You can view daily usage and cumulative monthly usage. Usage can be measured in core minutes or minutes.

Build usage details
Open the Flow homepage and click Resource Usage. On this page, you can view the Build Usage Details for all pipeline tasks in your organization.
-
You can view details for each task, including build duration, build cluster, coefficient, number of CPU cores, build core seconds, task start time, and task end time. Key details for each task include:
-
Build duration: The total runtime of a pipeline task.
-
Build cluster: The cluster where the pipeline task ran. Supported clusters include
cn-beijing(China (Beijing)),cn-hangzhou(China (Hangzhou)), andcn-hongkong(China (Hong Kong)). -
Coefficient: The cluster coefficient is 1 for clusters in the China (Beijing) and China (Hangzhou) regions, 2 for the China (Hong Kong) region, and 0.8 for a hosted VPC. Alibaba Cloud DevOps uses this coefficient to standardize unit prices because build costs vary by region.
-
CPU cores: The number of CPU cores in the task's build environment.
-
Build core seconds: Calculated as: Build core seconds = Build duration (seconds) × Number of CPU cores × Coefficient. Resource usage is billed in build core minutes and calculated as: Build core minutes = Build core seconds / 60.
-
-
You can export the build detail data for custom analysis.