erda-cicd

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

ERDA CI/CD

ERDA CI/CD

This skill focuses on the real
erda-cli
command surface for pipeline and delivery workflows, not just static YAML editing.
Do not assume repository-level shared files are present when this skill is installed. Start from the skill-local references and scripts first.
This skill is backed by command knowledge and working assets:
  • prerequisites and fallback rules:
    references/prerequisites.md
  • command guidance:
    references/cli-capabilities.md
  • diagnostic playbook:
    references/diagnostics.md
  • reusable templates:
    assets/templates/basic-pipeline.yml
    ,
    assets/templates/build-release-deploy.yml
  • deterministic prerequisite check:
    scripts/doctor.sh
  • validation prompts: see
    references/cli-capabilities.md
本Skill聚焦于用于流水线和交付工作流的真实
erda-cli
命令体系,而非仅静态YAML编辑。
安装本Skill时,请勿假设仓库级共享文件已存在。请优先从Skill本地的参考资料和脚本开始操作。
本Skill依托命令知识和可用资源构建:
  • 前置条件与降级规则:
    references/prerequisites.md
  • 命令指南:
    references/cli-capabilities.md
  • 诊断手册:
    references/diagnostics.md
  • 可复用模板:
    assets/templates/basic-pipeline.yml
    assets/templates/build-release-deploy.yml
  • 确定性前置检查:
    scripts/doctor.sh
  • 验证提示:详见
    references/cli-capabilities.md

Use This Skill For

适用场景

  • running ERDA pipelines through
    erda-cli
  • checking pipeline status, history, and logs
  • diagnosing failed or stuck CI/CD flows
  • explaining how pipeline and delivery commands fit together
  • reviewing pipeline-oriented workflow assumptions when they affect execution
  • diagnosing failed or stuck pipelines
  • identifying missing branch, workspace, application, or task context
  • 通过
    erda-cli
    运行ERDA流水线
  • 检查流水线状态、历史记录与日志
  • 诊断失败或停滞的CI/CD流程
  • 解释流水线与交付命令的协同方式
  • 回顾影响执行的流水线导向工作流假设
  • 诊断失败或停滞的流水线
  • 识别缺失的分支、工作区、应用或任务上下文

Workflow

工作流程

  1. Verify CLI availability with the skill-local doctor script or direct probing from
    references/prerequisites.md
    .
  2. Identify the repository context, branch, workspace, org, project, and application.
  3. Before
    pipeline run
    , check
    git status --short
    .
  4. If the workspace is dirty, stop. Treat this as a hard prerequisite failure and require the user to commit the intended changes first.
  5. Only use a temporary clean clone as a secondary troubleshooting or reproduction technique, not as the default path for running new pipeline content.
  6. In a temporary clean clone, verify
    git remote -v
    and
    .erda.d/config
    or equivalent project context before running the pipeline.
  7. Use the minimal diagnostic sequence from
    references/diagnostics.md
    :
    whoami
    ,
    pipeline history
    , then
    erda-cli -V pipeline run ...
    .
  8. Separate context discovery failure, permission failure, and pipeline execution failure.
  9. When giving commands, prefer exact subcommands and flags over abstract descriptions.
  1. 使用Skill本地的doctor脚本或直接参考
    references/prerequisites.md
    中的方法验证CLI可用性。
  2. 识别仓库上下文、分支、工作区、组织、项目与应用。
  3. 在执行
    pipeline run
    前,检查
    git status --short
  4. 如果工作区未清理(存在未提交更改),则停止操作。将此视为硬性前置条件失败,要求用户先提交预期的更改。
  5. 仅将临时干净克隆作为次要的故障排查或复现手段,而非运行新流水线内容的默认方式。
  6. 在临时干净克隆中,运行流水线前需验证
    git remote -v
    以及
    .erda.d/config
    或等效的项目上下文。
  7. 使用
    references/diagnostics.md
    中的最小诊断序列:
    whoami
    pipeline history
    ,然后执行
    erda-cli -V pipeline run ...
  8. 区分上下文发现失败、权限失败与流水线执行失败。
  9. 给出命令时,优先使用精确的子命令和标志,而非抽象描述。

Review Priorities

检查重点

  • wrong branch or workspace assumptions
  • missing pipeline context such as pipeline ID, task name, or application binding
  • missing repository context such as
    .erda.d/config
    or correct
    origin
  • confusion between run creation, status inspection, history inspection, and log inspection
  • attempts to run pipelines from uncommitted workspace content
  • read permission versus run permission mismatches
  • delivery failures that are actually earlier build failures
  • commands that skip authentication or repository cleanliness requirements
  • 错误的分支或工作区假设
  • 缺失的流水线上下文,如流水线ID、任务名称或应用绑定
  • 缺失的仓库上下文,如
    .erda.d/config
    或正确的
    origin
  • 对流水线创建、状态检查、历史查看与日志查看的混淆
  • 尝试从未提交的工作区内容中运行流水线
  • 读取权限与运行权限不匹配
  • 实际为早期构建失败导致的交付失败
  • 跳过认证或仓库清理要求的命令

References

参考资料

  • Prerequisites and fallback:
    references/prerequisites.md
  • Command guidance:
    references/cli-capabilities.md
  • Diagnostics:
    references/diagnostics.md
  • Templates:
    assets/templates/basic-pipeline.yml
    ,
    assets/templates/build-release-deploy.yml
  • 前置条件与降级规则:
    references/prerequisites.md
  • 命令指南:
    references/cli-capabilities.md
  • 诊断手册:
    references/diagnostics.md
  • 模板:
    assets/templates/basic-pipeline.yml
    assets/templates/build-release-deploy.yml