xiaoxia/xiaoxia-saas
1
0
Fork 0
Code Issues 9 Pull Requests 2 Actions Packages Projects Releases 7 Wiki Activity

perf(ci): 修复Frontend Lint的npm缓存假命中问题 #341

Merged
xiaoxia merged 2 commits from feat/frontend-cache-fix into develop 2026-07-15 09:04:03 +08:00
Conversation 1 Commits 2 Files Changed 1
+1 -1
xiaoxia commented 2026-07-15 08:03:26 +08:00
Owner
Copy Link
Copy Source

问题

Frontend Lint Job每次执行 rm -rf node_modules/* 然后 npm ci，Docker volume缓存完全失效，缓存等于摆设。

优化方案

基于 package-lock.json 的 md5 hash 判断依赖是否变更：

  • hash不变 → 跳过npm ci（缓存命中）
  • hash变化 → 执行npm ci并更新hash（缓存失效）

预期收益

  • 依赖不变时，Lint Job从~4min → ~1min（省60%+）
  • 依赖变更时，耗时不变（正常npm ci）

验证方式

合并后连续观察3-5次PR的Frontend Lint耗时，对比优化前数据。

## 问题 Frontend Lint Job每次执行 `rm -rf node_modules/*` 然后 `npm ci`，Docker volume缓存完全失效，缓存等于摆设。 ## 优化方案 基于 package-lock.json 的 md5 hash 判断依赖是否变更： - hash不变 → 跳过npm ci（缓存命中） - hash变化 → 执行npm ci并更新hash（缓存失效） ## 预期收益 - 依赖不变时，Lint Job从~4min → ~1min（省60%+） - 依赖变更时，耗时不变（正常npm ci） ## 验证方式 合并后连续观察3-5次PR的Frontend Lint耗时，对比优化前数据。
xiaoxia added 1 commit 2026-07-15 08:03:27 +08:00
perf(ci): 修复Frontend Lint的npm缓存假命中问题 0e44ff407f 
- 移除每次rm -rf node_modules的操作
- 基于package-lock.json hash判断是否需要重装依赖
- 依赖不变时跳过npm ci，预计节省50%+Lint耗时
xiaoxia added 1 commit 2026-07-15 08:47:06 +08:00
fix(ci): 修复YAML语法错误，npm缓存逻辑需在同一行双引号字符串内
CI/CD Pipeline / Frontend Lint (pull_request) Successful in 1m1s
Details
CI/CD Pipeline / Validate Code Quality And Tests (pull_request) Successful in 1m27s
Details
CI/CD Pipeline / Build Staging API Image (pull_request) Has been skipped
Details
CI/CD Pipeline / Build Staging Worker Image (pull_request) Has been skipped
Details
CI/CD Pipeline / Build Staging Web Image (pull_request) Has been skipped
Details
CI/CD Pipeline / Build Production API Image (pull_request) Has been skipped
Details
CI/CD Pipeline / Build Production Worker Image (pull_request) Has been skipped
Details
CI/CD Pipeline / Build Production Web Image (pull_request) Has been skipped
Details
CI/CD Pipeline / Deploy Production (pull_request) Has been skipped
Details
CI/CD Pipeline / Deploy Staging (Watchtower auto-deploy) (pull_request) Has been skipped
Details
CI/CD Pipeline / Staging E2E Tests (pull_request) Has been skipped
Details
CI/CD Pipeline / Staging API Integration Tests (pull_request) Has been skipped
Details
CI/CD Pipeline / Production Browser E2E (pull_request) Has been skipped
Details
CI/CD Pipeline / Unit Tests (pull_request) Successful in 1m33s
Details
CI/CD Pipeline / Integration Tests (pull_request) Successful in 1m5s
Details
e2c6d77965
auto-approve-bot approved these changes 2026-07-15 09:02:01 +08:00
auto-approve-bot left a comment
Collaborator
Copy Link
Copy Source

CI全绿，自动审批通过。

CI全绿，自动审批通过。
xiaoxia merged commit e705cbdd8a into develop 2026-07-15 09:04:03 +08:00
xiaoxia deleted branch feat/frontend-cache-fix 2026-07-15 09:04:04 +08:00
Sign in to join this conversation.
Reviewers
No Reviewers
auto-approve-bot
Labels
Clear labels
P0
阻塞性，必须立即处理
 P1
高优先级
 P2
中优先级
 P3
低优先级/后考虑
 architecture
架构设计
 backend
后端相关
 blocked
阻塞中
 bug
Bug修复
 ci-bug
CI本身的bug
 ci-optimization
CI优化类任务
 ci-pipeline
CI流水线/workflow相关
 cleanup
代码清理
 devops
运维/部署/CI
 documentation
文档相关
 feature
新功能
 frontend
前端相关
 question
需要讨论确认
 ready
PR CI通过，可合并
 refactor
代码重构
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
auto-approve-bot xiaoxia
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: xiaoxia/xiaoxia-saas#341
Delete Branch "feat/frontend-cache-fix"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?