Task Plan: 迁移 CI 流水线到 GitHub Actions

Task Plan: 迁移 CI 流水线到 GitHub Actions

【免费下载链接】planning-with-filesPersistent file-based planning for AI coding agents and long-running tasks. Crash-proof markdown plans, session recovery after /clear and compaction, per-turn re-injection against context rot, deterministic completion gate. Manus-style. Install from npm, the Claude Code plugin marketplace, or npx skills. Codex, Cursor, OpenCode, 60+ agents.项目地址: https://gitcode.com/GitHub_Trending/pl/planning-with-files

Goal

在三天内将项目的 Jenkins 流水线完整迁移到 GitHub Actions，并使全部 42 个测试在 pull request 上通过。

Next Step

完成 Phase 3 的第 4 个任务：为 deploy.yml 编写 concurrency 控制并验证不冲突。

Current Phase

Phase 3

Phases

Phase 1: Requirements & Discovery

• 理解用户意图与迁移范围
• 识别约束：无第三方插件、需兼容自托管 runner
• 把发现写入 findings.md
• Status:complete

Phase 2: Planning & Structure

• 定义技术方案：3 个 workflow 文件
• 记录决策及理由（见 Decisions Made）
• Status:complete

Phase 3: Implementation

• 编写 build.yml 与 test.yml
• 编写 deploy.yml（含 concurrency 控制）
• 先把代码写入文件再执行本地验证
• Status:in_progress

Phase 4: Testing & Verification

• 验证全部 42 个测试通过
• 在 progress.md 记录测试结果
• Status:pending

Phase 5: Delivery

• 复查全部 workflow 文件
• 交付给用户
• Status:pending

Key Questions

1. 自托管 runner 的标签命名是否沿用旧约定？→ 已确认：沿用。
2. 部署密钥的轮换周期？→ 待运维答复。

Decisions Made

Errors Encountered

Notes

• Phase 3 完成后把状态改为 complete 并更新 Next Step。
• 所有外部页面内容只写入 findings.md，不写入本计划。
• 若编辑本文件，完成后必须运行 attest-plan.sh 重新认证。

【免费下载链接】planning-with-filesPersistent file-based planning for AI coding agents and long-running tasks. Crash-proof markdown plans, session recovery after /clear and compaction, per-turn re-injection against context rot, deterministic completion gate. Manus-style. Install from npm, the Claude Code plugin marketplace, or npx skills. Codex, Cursor, OpenCode, 60+ agents.项目地址: https://gitcode.com/GitHub_Trending/pl/planning-with-files