managing-devops-pipeline

BlueKing Pipeline Management

Applicable Scenarios

• Query pipeline build history
• Get startup parameters and prepare to trigger a build
• View build status and recent execution results
• Parse from an existing pipeline link projectId and pipelineId

Not Applicable Scenarios

• Modify pipeline definitions, templates, or plugin logic
• Discuss pipeline architecture implementation
• Directly initiate build operations with side effects without user confirmation

Quick Guide

1. This skill focuses on "how to safely operate existing pipeline builds", not a pipeline design guide.
2. Before use, confirm three identifiers:
   • projectId: project English name
   • pipelineId: starts with p- pipeline ID
   • buildId: starts with b- build ID
3. The shortest path to trigger a build is: first get the startup parameters, then show the user the complete input parameters and obtain confirmation, and only then actually start it.
4. Query-type operations can usually be read directly; startup-type operations must clearly distinguish between "viewing parameters" and "executing the trigger".
5. Specific tool calls and example payloads are not placed in the main file; enter the corresponding reference/。
6. If the question has shifted to the pipeline model, templates, or execution chain, switch to the corresponding module skill.

High-Signal Rules

• All build startup operations with side effects must first obtain explicit user confirmation
• The main skill is only responsible for telling the model "when to query, when to ask, and when it can start"
• projectId、pipelineId、buildId is the most basic operation context, none can be missing
• When parsing identifiers through a URL, first confirm that the link is indeed a pipeline details page

Key Pitfalls

• Mistaking "getting startup parameters" for "already allowed to start a build"
• Directly triggering a build without showing the complete input parameters
• Cramming example payloads and memorized details into the main file, causing context redundancy

Further Reading

• Get build history:reference/build-list.md
• Get startup parameters:reference/build-startinfo.md
• View build status:reference/build-status.md
• Start build:reference/build-start.md
• If you are modifying pipeline definitions: see also process-module-architecture