mcpField
A
artifactory-module-architecture

artifactory-module-architecture

github.com/tencentbluekingCloud & DevOps2.5k48 installsUpdated 1d ago
Repository

About artifactory-module-architecture

Artifactory Module Architecture is a Skill for investigating artifact storage and access issues, aimed at development and operations work involving build outputs, file metadata, and storage backends. It distinguishes metadata, tasks, and backend storage, and guides checks of BkRepo, disk implementations, and post-processing paths.

Key features

  1. 01Explains artifact storage models and paths
  2. 02Guides investigation of BkRepo and disk backends
  3. 03Separates file metadata, tasks, and storage
  4. 04Covers build artifact archiving and downloads
  5. 05Checks how async processing affects artifact visibility

Use cases

  1. 01Investigate uploads that succeed but yield missing files
  2. 02Identify the active storage backend
  3. 03Check report or custom-directory path issues
  4. 04Trace artifact processing after a build completes

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/tencentblueking/bk-ci --skill artifactory-module-architecture

After installing, type/artifactory-module-architecturein Claude Code to confirm it loaded.

Bundled filesreference/1-artifact-storage.mdreference/2-bkrepo-task-extension.md

Details

From the project README

Artifactory 模块架构

适用场景

  • 上传、下载、归档构建产物
  • 管理文件元数据、文件任务和下载令牌
  • 切换或排查 BkRepo / 磁盘存储后端
  • 处理报告文件、自定义目录和流水线产物路径
  • 排查构建完成后的制品后处理

不适用场景

  • 只是商店组件发布问题，不涉及制品存储
  • 只是普通文件路径拼接，不涉及制品语义和存储后端
  • 只是流水线执行问题，不涉及产物归档或下载

快速指导

  1. 先判断问题属于哪条主线：
    • 存储模型与路径：看 reference/1-artifact-storage.md
    • BkRepo、任务与扩展：看 reference/2-bkrepo-task-extension.md
  2. Artifactory 负责“文件和制品如何被存储与访问”，不是执行引擎本身。
  3. 如果问题表现为上传成功但文件找不到，先区分是：
    • 元数据没落库
    • 后端没存成功
    • 路径规则错了
    • 下载令牌或权限错了
  4. 存储后端切换或双实现问题，优先确认实际走的是 BkRepo 还是本地磁盘实现。

高信号规则

  • PROJECT_CODE / PROJECT_ID 通常仍按项目英文标识理解
  • 文件元数据、文件任务和真实后端存储不是同一层
  • BkRepo 与 Disk 是两套后端实现，排查时要先确认命中的实现类
  • 构建完成后的异步处理也会影响制品最终可见性

关键陷阱

  • 只看文件存储后端，不看元数据和任务状态
  • 路径规则变了却没同步影响下载、报告或自定义目录逻辑
  • 只验证上传接口成功，不验证后续查询、下载和清理链路
  • 把商店归档和普通流水线制品归档混成同一问题

延伸阅读

  • 存储基础：reference/1-artifact-storage.md
  • BkRepo 与任务：reference/2-bkrepo-task-extension.md
  • 涉及项目语义时：再看 project-module-architecture
  • 涉及商店归档时：再看 store-module-architecture

Comments

Markdown supported