pipeline-variable-management

Pipeline variables across BK-CI builds are managed by aligning backend BuildFormProperty and YAML Variable models via VariableTransfer, handling creation, initialization, propagation, and querying across stages and sub-pipelines.

The pipeline variable lifecycle in BK-CI covers creation, initialization, dynamic updates, storage, and querying across stages and jobs, preventing configuration drift and runtime errors.

Extending pipeline variable fields requires adding new attributes and ensuring front-end back-end synchronization by referencing BuildFormProperty and Variable models to maintain alignment.

Yes, cross-pipeline variable propagation flows values from triggers to tasks across parent and child pipelines, supporting manual, API, and webhook triggers.

Pipeline variables cause configuration drift and runtime errors when their creation, initialization, propagation, and extension across stages and sub-pipelines lack alignment between backend BuildFormProperty and YAML Variable models.

Debugging pipeline variables across stages involves consulting lifecycle documentation to understand how variables are defined, initialized, stored, and transmitted, ensuring proper cross-stage propagation.