fix(ci): 修复docker login YAML格式 - 所有镜像构建失败 #606

Merged
xiaoxia merged 1 commits from fix/docker-login-format into develop 2026-07-19 19:22:53 +08:00
Owner

问题

#605 CI架构精简合并后,所有staging/production镜像构建失败,错误:

"docker login" requires at most 1 argument.

根因

ci-pipeline.yml 中3处 docker login 步骤的 run 字段,从原来的 | 块格式改成了单引号多行字符串格式。

YAML中单引号字符串内的换行会被折叠成空格,导致所有命令挤在同一行。第二个 docker login 被当成了第一个命令的参数,因此报错。

修复

改回 run: | 块格式,确保每行命令独立执行。

涉及3处:

  • build-staging job 的 Docker login
  • deploy-staging job 的 Docker login
  • build-production job 的 Docker login
## 问题 #605 CI架构精简合并后,所有staging/production镜像构建失败,错误: ``` "docker login" requires at most 1 argument. ``` ## 根因 `ci-pipeline.yml` 中3处 `docker login` 步骤的 `run` 字段,从原来的 `|` 块格式改成了单引号多行字符串格式。 YAML中单引号字符串内的换行会被折叠成空格,导致所有命令挤在同一行。第二个 `docker login` 被当成了第一个命令的参数,因此报错。 ## 修复 改回 `run: |` 块格式,确保每行命令独立执行。 涉及3处: - build-staging job 的 Docker login - deploy-staging job 的 Docker login - build-production job 的 Docker login
xiaoxia added 1 commit 2026-07-19 19:16:11 +08:00
fix(ci): 修复docker login YAML格式 - 单引号多行字符串导致命令挤在同一行
CI/CD Pipeline / Build Staging Web Image (pull_request) Has been skipped
CI/CD Pipeline / Build Staging API 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 / Build Production Worker Image (pull_request) Has been skipped
CI/CD Pipeline / ACR Image Cleanup (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 / Deploy Production (pull_request) Has been skipped
CI/CD Pipeline / Production Browser E2E (pull_request) Has been skipped
Preview Deploy / Deploy Preview Environment (pull_request) Failing after 16s
CI/CD Pipeline / Check if frontend-only change (pull_request) Successful in 21s
CI/CD Pipeline / Frontend Unit Tests (pull_request) Has been skipped
AI Code Review / AI Code Review (pull_request) Successful in 1m37s
CI/CD Pipeline / Frontend Lint (pull_request) Successful in 3m42s
CI/CD Pipeline / Unit Tests (pull_request) Successful in 3m27s
CI/CD Pipeline / Validate Code Quality And Tests (pull_request) Successful in 3m50s
PR Automation / Auto Approve on CI Green (pull_request) Successful in 4m18s
CI/CD Pipeline / Integration Tests (pull_request) Successful in 2m3s
Preview Cleanup / Cleanup Preview Environment (pull_request) Successful in 19s
PR Automation / Auto Merge on CI Green + Approved (pull_request) Successful in 7m16s
d6593ad075
#605架构精简时把docker login步骤的run从|块格式改成了单引号多行字符串,
YAML解析后所有命令被折叠成一行,第二个docker login被当成了第一个的参数,
导致报'requires at most 1 argument'错误,所有镜像构建失败。

改回|块格式修复。
Collaborator

📊 审查概览

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

需修改的问题(严重)

💡 改进建议(一般)

良好实践

  1. [.gitea/workflows/ci-pipeline.yml] 优化 YAML 脚本块语法
    • 具体内容:将 run 字段从单引号包裹的字符串拼接(run: '...')改为 YAML 的多行块标量(run: |)。这一改动消除了为了在单引号字符串中包含单引号而进行的繁琐转义(如 ''%s''),使得 Shell 脚本内容更直观、易读,且降低了 YAML 解析错误的风险。

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

### 📊 审查概览 - 整体评价:通过 - 严重问题数量:0 个 - 一般建议数量:0 个 ### ❌ 需修改的问题(严重) 无 ### 💡 改进建议(一般) 无 ### ✅ 良好实践 1. **[.gitea/workflows/ci-pipeline.yml] 优化 YAML 脚本块语法** - 具体内容:将 `run` 字段从单引号包裹的字符串拼接(`run: '...'`)改为 YAML 的多行块标量(`run: |`)。这一改动消除了为了在单引号字符串中包含单引号而进行的繁琐转义(如 `''%s''`),使得 Shell 脚本内容更直观、易读,且降低了 YAML 解析错误的风险。 --- <sub>🤖 由 AI 代码审查机器人自动生成 | 2026-07-19 19:17:49 | 模型: </sub> <!-- AI_CODE_REVIEW_AUTO_COMMENT -->
auto-approve-bot approved these changes 2026-07-19 19:20:30 +08:00
auto-approve-bot left a comment
Collaborator

CI全绿,自动审批通过。

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

CI全绿,自动审批通过。

CI全绿,自动审批通过。
xiaoxia merged commit 291ac95975 into develop 2026-07-19 19:22:53 +08:00
xiaoxia deleted branch fix/docker-login-format 2026-07-19 19:22:53 +08:00

🗑️ 预览环境已清理

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

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

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