dispatch-module-architecture

Build task dispatch in BK-CI allocates, queues, and monitors jobs across Docker, third-party agents, and Kubernetes using a modular API, service, and DAO layer. It defines core enums like PipelineTaskStatus and JobQuotaVmType to manage scheduling.

To add a new scheduling strategy, review the dispatch module architecture to identify integration points and data models. The Skill codifies the module structure and data access patterns needed to extend agent selection and resource allocation.

The dispatch subsystem structure separates concerns into API, service, and DAO layers. This modular design ensures correct scheduling by defining core concepts like task status, VM types, and queueing mechanisms for build tasks.

Yes, BK-CI dispatch supports third-party agents alongside Docker and Kubernetes. The architecture documents how tasks are allocated and monitored across these different dispatch types to ensure reliable and scalable execution.

Core concepts for build task queues in BK-CI include task status tracking, VM quota types, and queueing mechanisms. These elements are codified within the dispatch subsystem to ensure correct resource allocation and agent selection.

BK-CI separates dispatch logic into API, service, and DAO layers to ensure scalable and reliable task scheduling. This structure clarifies data access patterns and isolates scheduling strategies from underlying resource allocation mechanisms.