Jump to content

Connect SuperML | Leeroopedia MCP: Equip your AI agents with best practices, code verification, and debugging knowledge. Powered by Leeroo — building Organizational Superintelligence. Contact us at founders@leeroo.com.

Environment:Vllm project Vllm Buildkite

From Leeroopedia


Knowledge Sources
Domains CI_CD, Build_Infrastructure
Last Updated 2026-02-08 00:00 GMT

Overview

Buildkite CI/CD pipeline environment for vLLM's automated testing, release builds, and GPU-accelerated test execution, providing the pipeline orchestration layer that coordinates test runs across NVIDIA and AMD GPU hardware.

Description

This environment defines the Buildkite continuous integration infrastructure used by the vLLM project for GPU-intensive test pipelines that cannot run on GitHub Actions due to hardware requirements. Buildkite pipelines are defined in YAML configuration files (typically in .buildkite/) and executed on self-hosted agents equipped with NVIDIA and AMD GPUs. The pipeline configurations define build steps, Docker image dependencies, environment variables, agent queue targeting (e.g., GPU type, memory capacity), retry policies, and artifact collection. vLLM uses separate pipeline configurations for NVIDIA CUDA testing, AMD ROCm testing, and release builds. The release pipeline handles building Docker images, running the full test suite, and publishing release artifacts to container registries. Test pipelines parallelize test execution across multiple GPU agents to reduce wall-clock time for the full test matrix.

Usage

Pipeline configurations are stored in the repository under .buildkite/ and are triggered automatically on pull requests and merges to the main branch via Buildkite's GitHub webhook integration. Each pipeline step specifies a Docker image, commands to execute, agent queue selectors (to target specific GPU hardware), and timeout limits. Buildkite agents running on GPU-equipped machines poll for work and execute pipeline steps in isolated Docker containers. Pipeline results are reported back to GitHub as commit status checks, which are required by Mergify and branch protection rules before merging.

Requirements

Requirement Value
Buildkite Platform Buildkite SaaS (buildkite.com)
Buildkite Agents Self-hosted agents with GPU hardware
Pipeline Configuration YAML files in .buildkite/ directory
Docker Docker Engine for containerized build steps
NVIDIA Container Toolkit nvidia-docker2 for GPU passthrough to containers
GPU Hardware (NVIDIA) H100, A100, or equivalent for CUDA test pipelines
GPU Hardware (AMD) MI250X, MI300X for ROCm test pipelines
GitHub Integration Buildkite GitHub webhook for PR/push triggers
Artifact Storage Buildkite artifact storage for build outputs

Semantic Links

Page Connections

Double-click a node to navigate. Hold to expand connections.
Principle
Implementation
Heuristic
Environment