managing-devops-pipeline_skill

Overview

This skill manages BlueKing (蓝盾) DevOps pipeline build operations: query build history, fetch start parameters, view build status, and trigger builds. It targets pipelines identified by projectId, pipelineId (p-...), and buildId (b-...), and is intended for CI/CD, deployment, and build orchestration tasks.

How this skill works

The skill calls MCP endpoints to list builds, retrieve build start parameters, check build status, and start builds. Before any start operation it displays the full start parameters to the user and requires explicit confirmation. It parses pipeline URLs to extract projectId and pipelineId and returns standardized status enums (SUCCEED, FAILED, CANCELED, RUNNING, QUEUE, STAGE_SUCCESS).

When to use it

• When you need to list recent or historical builds for a pipeline
• When preparing to trigger a build and you must review/confirm parameters
• When you need to poll or check the status of a running build
• When automating CI/CD steps that require programmatic start/stop/status checks
• When extracting projectId and pipelineId from BlueKing pipeline URLs

Best practices

• Always present the full body_param key-value list and get explicit user confirmation before calling the start API
• Validate projectId and pipelineId format (pipelineId starts with 'p-') before requests
• Use paginated listing for build history (page, pageSize) to avoid large responses
• Map returned status enums to clear UI states and alerts for RUNNING, FAILED, SUCCEED, etc.
• Log buildId and timestamps for audit and correlation with deployment records

Example use cases

• Fetch the last 10 builds for project 'your-project' and pipeline 'p-xxx' to display a history view
• Retrieve start parameters for a pipeline, show them to the operator, and start the build after confirmation
• Poll a build by buildId to update a dashboard until it reaches SUCCEED or FAILED
• Trigger a branch-specific build by sending body_param {"branch":"master"} after approval
• Extract projectId and pipelineId from a BlueKing console URL to populate request parameters