如何修复Cloud Build同步GCS文件错误，实现React应用自动部署至App Engine？

问题出在两个关键点上，直接修正即可实现全流程自动化：

1. rsync参数格式错误 #

你在copy_bucket_to_directory步骤中，把GCS桶路径和本地目录路径写到了同一个字符串里，导致gsutil无法识别两个独立的参数。正确写法应该将两者拆分为单独的字符串参数。

2. 目标目录未提前创建 #

Cloud Build的执行环境是临时容器，默认不存在./react_app目录，部分场景下gsutil rsync会因目标目录不存在报错，需提前创建。

修正后的完整Cloud Build配置 #

steps:
  - name: 'gcr.io/cloud-builders/npm'
    args: ['install']
    dir: "./frontend"
    id: "install_npm"

  - name: 'gcr.io/cloud-builders/npm'
    args: ['run', 'build']
    dir: "./frontend"
    id: "run_build"

  - name: 'gcr.io/cloud-builders/gsutil'
    args: ['cp', '-r', 'frontend/build', 'gs://react_bucket']
    id: "copy_build_to_bucket"

  - name: 'gcr.io/cloud-builders/gsutil'
    args: ['cp', '-r', 'ops/app.yaml', 'gs://react_bucket']
    id: "copy_app_yaml_to_bucket"

  # 新增：提前创建目标目录，-p参数避免目录已存在时报错
  - name: 'gcr.io/cloud-builders/bash'
    args: ['mkdir', '-p', './react_app']
    id: "create_target_directory"

  # 修正：拆分rsync的源和目标为独立参数
  - name: 'gcr.io/cloud-builders/gsutil'
    args: [ 'rsync', '-r', 'gs://react_bucket', './react_app' ]
    id: "copy_bucket_to_directory"

  - name: 'gcr.io/cloud-builders/gcloud'
    args: [ 'app', 'deploy', './react_app/app.yaml' ]
    id: "deploy_to_app_engine"

额外优化建议（跳过GCS中转） #

其实没必要先上传GCS再同步回来，直接在Cloud Build环境内整理构建产物和配置文件后部署，步骤更少、效率更高，还能避免GCS相关的权限/路径问题：

steps:
  - name: 'gcr.io/cloud-builders/npm'
    args: ['install']
    dir: "./frontend"
    id: "install_npm"

  - name: 'gcr.io/cloud-builders/npm'
    args: ['run', 'build']
    dir: "./frontend"
    id: "run_build"

  # 直接在本地整理部署文件
  - name: 'gcr.io/cloud-builders/bash'
    args:
      - '-c'
      - |
        mkdir -p ./deploy_dir
        cp -r frontend/build/* ./deploy_dir/
        cp ops/app.yaml ./deploy_dir/
    id: "prepare_deploy_files"

  - name: 'gcr.io/cloud-builders/gcloud'
    args: [ 'app', 'deploy', './deploy_dir/app.yaml' ]
    id: "deploy_to_app_engine"

内容的提问来源于stack exchange，提问作者Shadow Walker