fix(ci): 迁移Validate/Frontend job到ci-l2 runner,解决ci-check环境Docker端口映射失效 #616

Merged
auto-approve-bot merged 1 commits from fix/ci-validate-runner into develop 2026-07-19 22:20:53 +08:00
Owner

问题

ci-check runner的Docker-in-Docker端口映射存在问题:容器内部pg_isready显示healthy,但宿主侧通过映射端口TCP连接始终失败(60秒超时),导致Validate Code Quality的Alembic迁移验证持续失败。

根因

ci-checkci-l2是不同的runner环境,ci-check的DinD网络/端口映射配置有问题。Integration Tests使用ci-l2 runner,TCP连通性检查一次通过,验证了ci-l2环境正常。

修复

将以下4个job从ci-check统一迁移到ci-l2 runner:

  • check-frontend-only
  • Validate Code Quality And Tests
  • Frontend Lint
  • Frontend Unit Tests

统一运行环境,消除runner差异导致的偶发/必现失败。

## 问题 `ci-check` runner的Docker-in-Docker端口映射存在问题:容器内部`pg_isready`显示healthy,但宿主侧通过映射端口TCP连接始终失败(60秒超时),导致Validate Code Quality的Alembic迁移验证持续失败。 ## 根因 `ci-check`与`ci-l2`是不同的runner环境,`ci-check`的DinD网络/端口映射配置有问题。Integration Tests使用`ci-l2` runner,TCP连通性检查一次通过,验证了`ci-l2`环境正常。 ## 修复 将以下4个job从`ci-check`统一迁移到`ci-l2` runner: - check-frontend-only - Validate Code Quality And Tests - Frontend Lint - Frontend Unit Tests 统一运行环境,消除runner差异导致的偶发/必现失败。
xiaoxia added 1 commit 2026-07-19 22:14:06 +08:00
fix(ci): 将Validate/Frontend等job从ci-check迁移到ci-l2 runner,解决ci-check环境Docker端口映射失效问题
CI/CD Pipeline / Build Staging API Image (pull_request) Has been skipped
CI/CD Pipeline / Build Staging Web Image (pull_request) Has been skipped
CI/CD Pipeline / Build Staging Worker Image (pull_request) Has been skipped
CI/CD Pipeline / Deploy Staging (Watchtower auto-deploy) (pull_request) Has been skipped
CI/CD Pipeline / Build Production API Image (pull_request) Has been skipped
CI/CD Pipeline / Build Production Web Image (pull_request) Has been skipped
CI/CD Pipeline / Staging E2E Tests (pull_request) Has been skipped
CI/CD Pipeline / Staging API Integration Tests (pull_request) Has been skipped
CI/CD Pipeline / Build Production Worker Image (pull_request) Has been skipped
CI/CD Pipeline / Deploy Production (pull_request) Has been skipped
CI/CD Pipeline / ACR Image Cleanup (pull_request) Has been skipped
CI/CD Pipeline / Production Browser E2E (pull_request) Has been skipped
CI/CD Pipeline / Check if frontend-only change (pull_request) Successful in 16s
CI/CD Pipeline / Frontend Unit Tests (pull_request) Has been skipped
Preview Deploy / Deploy Preview Environment (pull_request) Successful in 1m10s
AI Code Review / AI Code Review (pull_request) Successful in 1m30s
CI/CD Pipeline / Validate Code Quality And Tests (pull_request) Successful in 3m26s
CI/CD Pipeline / Unit Tests (pull_request) Successful in 4m5s
CI/CD Pipeline / Frontend Lint (pull_request) Successful in 4m54s
PR Automation / Auto Approve on CI Green (pull_request) Successful in 4m56s
CI/CD Pipeline / Integration Tests (pull_request) Successful in 1m59s
PR Automation / Auto Merge on CI Green + Approved (pull_request) Successful in 6m45s
Preview Cleanup / Cleanup Preview Environment (pull_request) Successful in 10s
0d54876999
ci-check runner的Docker-in-Docker端口映射存在问题,容器内部pg_isready显示healthy
但宿主侧TCP连接始终失败(60秒超时),导致Validate Code Quality的Alembic迁移验证
以及所有需要独立PG/Redis容器的检查失败。

将所有ci-check runner的job统一迁移到ci-l2(与Integration Tests同环境),
ci-l2的Docker网络端口映射工作正常,确保所有需要容器的检查能稳定运行。

影响的job:
- check-frontend-only
- Validate Code Quality And Tests
- Frontend Lint
- Frontend Unit Tests

🚀 预览环境已部署

项目 详情
PR号 #616
预览链接 https://pr-616.preview.xiaoxiajianji.com
API环境 staging

💡 预览环境使用 staging API 数据,请勿在预览环境中操作重要数据。

🔄 每次提交新代码后预览环境会自动更新。

🗑️ PR 关闭或合并后,预览环境会自动清理。

🚀 **预览环境已部署** | 项目 | 详情 | |------|------| | PR号 | #616 | | 预览链接 | [https://pr-616.preview.xiaoxiajianji.com](https://pr-616.preview.xiaoxiajianji.com) | | API环境 | staging | > 💡 预览环境使用 staging API 数据,请勿在预览环境中操作重要数据。 > > 🔄 每次提交新代码后预览环境会自动更新。 > > 🗑️ PR 关闭或合并后,预览环境会自动清理。
Collaborator

📊 审查概览

  • 整体评价:通过
  • 严重问题数量:0 个
  • 一般建议数量:0 个

需修改的问题(严重)

💡 改进建议(一般)

良好实践

  1. 配置一致性:在所有相关 Job(check-frontend-only, validate, frontend-lint, frontend-unit-test)中统一将 runs-onci-check 修改为 ci-l2,确保了 CI 环境迁移的一致性。
  2. 语法规范:YAML 语法修改正确,缩进和格式均符合规范。

🤖 由 AI 代码审查机器人自动生成 | 2026-07-19 22:15:38 | 模型:

### 📊 审查概览 - 整体评价:通过 - 严重问题数量:0 个 - 一般建议数量:0 个 ### ❌ 需修改的问题(严重) 无 ### 💡 改进建议(一般) 无 ### ✅ 良好实践 1. **配置一致性**:在所有相关 Job(`check-frontend-only`, `validate`, `frontend-lint`, `frontend-unit-test`)中统一将 `runs-on` 从 `ci-check` 修改为 `ci-l2`,确保了 CI 环境迁移的一致性。 2. **语法规范**:YAML 语法修改正确,缩进和格式均符合规范。 --- <sub>🤖 由 AI 代码审查机器人自动生成 | 2026-07-19 22:15:38 | 模型: </sub> <!-- AI_CODE_REVIEW_AUTO_COMMENT -->
auto-approve-bot approved these changes 2026-07-19 22:19:04 +08:00
auto-approve-bot left a comment
Collaborator

CI全绿,自动审批通过。

CI全绿,自动审批通过。
auto-approve-bot approved these changes 2026-07-19 22:19:04 +08:00
auto-approve-bot left a comment
Collaborator

CI全绿,自动审批通过。

CI全绿,自动审批通过。
auto-approve-bot merged commit dbe8580f85 into develop 2026-07-19 22:20:53 +08:00
auto-approve-bot deleted branch fix/ci-validate-runner 2026-07-19 22:20:53 +08:00

🗑️ 预览环境已清理

PR #616 已关闭或合并,对应的预览环境已被清理。

如有需要,可以重新打开 PR 来重新生成预览环境。

🗑️ **预览环境已清理** PR #616 已关闭或合并,对应的预览环境已被清理。 > 如有需要,可以重新打开 PR 来重新生成预览环境。
Sign in to join this conversation.