home / skills / tencentblueking / bk-ci / managing-devops-pipeline

managing-devops-pipeline skill

safe

This skill helps you manage BlueKing pipelines by querying histories, obtaining start parameters, viewing statuses, and safely triggering builds with user

npx playbooks add skill tencentblueking/bk-ci --skill managing-devops-pipeline

Review the files below or copy the command above to add this skill to your agents.

Files (6)

SKILL.md

2.6 KB

---
name: managing-devops-pipeline
description: 管理蓝盾流水线的构建操作，包括查询构建历史、获取启动参数、查看构建状态、启动构建。当用户提及流水线、构建、部署、CI/CD、蓝盾或需要触发构建任务时使用。
---

# 蓝盾流水线管理

通过 MCP 工具 `devops-prod-pipeline` 管理蓝盾流水线构建。

## 核心概念

- **projectId**：项目英文名（如 `myproject`）
- **pipelineId**：流水线 ID，以 `p-` 开头（如 `p-abc123`）
- **buildId**：构建 ID，以 `b-` 开头（如 `b-xyz789`）

## 重要规则

**启动构建前必须获得用户确认**：在调用 `v4_user_build_start` 之前，必须向用户展示完整的构建入参并获得明确确认。未经用户确认，禁止执行构建操作。

## 常用工作流

### 1. 启动构建

```
步骤 1：获取启动参数 → devops-prod-pipeline:v4_user_build_startInfo
步骤 2：向用户展示构建参数，等待用户确认 ⚠️ 必须执行
步骤 3：用户确认后启动构建 → devops-prod-pipeline:v4_user_build_start
步骤 4：查看状态 → devops-prod-pipeline:v4_user_build_status
```

**步骤 2 确认模板**：
```
即将启动构建，请确认以下参数：
- 项目：{projectId}
- 流水线：{pipelineId}
- 构建参数：
  {列出所有 body_param 的 key-value}

是否确认启动？
```

### 2. 查询构建历史

使用 `devops-prod-pipeline:v4_user_build_list` 获取历史记录。

## 常用流水线

用户配置的常用流水线，参阅 [config.json](config.json)

**URL 解析规则**：从 `https://xxxxxx/console/pipeline/{projectId}/{pipelineId}` 提取：
- `projectId`：`/pipeline/` 后的第一段
- `pipelineId`：以 `p-` 开头的最后一段

## 工具参考

**获取构建历史**：参阅 [reference/build-list.md](reference/build-list.md)
**获取启动参数**：参阅 [reference/build-startinfo.md](reference/build-startinfo.md)
**查看构建状态**：参阅 [reference/build-status.md](reference/build-status.md)
**启动构建**：参阅 [reference/build-start.md](reference/build-start.md)

## 快速示例

### 查询最近构建

```json
{
  "path_param": { "projectId": "your-project" },
  "query_param": { "pipelineId": "p-xxx", "page": 1, "pageSize": 10 }
}
```

### 启动一次构建

```json
{
  "path_param": { "projectId": "your-project" },
  "query_param": { "pipelineId": "p-xxx" },
  "body_param": { "branch": "master" }
}
```

## 构建状态枚举

| 状态 | 说明 |
|------|------|
| SUCCEED | 成功 |
| FAILED | 失败 |
| CANCELED | 已取消 |
| RUNNING | 运行中 |
| QUEUE | 排队中 |
| STAGE_SUCCESS | 阶段成功 |

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

FAQ

Must I get user confirmation before starting a build?

Yes. The skill requires displaying all start parameters and receiving explicit user confirmation before invoking the build start API.

How do I extract projectId and pipelineId from a pipeline URL?

From URLs like https://.../console/pipeline/{projectId}/{pipelineId}: projectId is the segment after /pipeline/, pipelineId is the last segment starting with 'p-'.