尝试使用 cloud build (gcp) 部署时出现 URL not found

Posted 2023-02-16

【中文标题】尝试使用 cloud build (gcp) 部署时出现 URL not found

【英文标题】：URL not found appears when try to deploy with cloud build (gcp)

【发布时间】：2021-04-06 23:27:33

【问题描述】：

应用程序 - 角度

我正在尝试在 GCP 中自动化我的 Angular 应用程序的部署过程。当我从云外壳手动部署时，一切正常，但是当我尝试使用 cloudbuild.yaml 构建-部署时，云构建触发它说部署成功。当我点击 URL 时，它显示 404 未找到。

手动部署命令

gsutil rsync -r gs://v2-appname.appspot.com ./deploytest
cd deploytest
gcloud app deploy

我对云构建不太熟悉。

问题可能出在下面给出的 cloudbuild.yaml 文件中。

steps:

      # Install node packages
      - name: "gcr.io/cloud-builders/npm:latest"
        args: ["install"]
    
      # Build production package
      - name: "gcr.io/cloud-builders/npm"
        args: ["build", "--configuration=staging"]
    
      # Deploy to google cloud app engine
      - name: "gcr.io/cloud-builders/gcloud"
        args: ["app", "deploy", "app.yaml"]

我的理解是，当我们手动部署时，我们会构建文件并将其上传到存储中的“dist”文件夹。然后我们同步目录进行部署，然后使用 gcloud app deploy 进行部署。

但是在使用云构建进行此操作时 - 我有连接到触发器的 GitHub 存储库，任何推送都发生在某个分支上，它会拾取 cloudbuild.yaml 文件和进程。但是 cloudbuild.yaml 没有任何目录可以部署或同步这是我缺少的东西吗？如何添加它？如果不是请纠正我！

谢谢，

编辑

EA_Website ->
         src/
         cloudbuild.yaml
         app.yaml
         angular.json
         package.json 

app.yaml

runtime: python27
threadsafe: yes
api_version: 1

# Google App Engine's cache default expiration time is 10 minutes. It's suitable for most Production
# scenarios, but a shorter TTL may be desired for Development and QA, as it allows us to see a fresh
# code in action just a minute after the deployment.
default_expiration: 60s

handlers:

# To enhance security, all http requests are redirected to their equivalent https addresses (secure: always).

# Assets are retrieved directly from their parent folder.
- url: /assets
  static_dir: dist/projectname/assets
  secure: always

# Static files located in the root folder are retrieved directly from there, but their suffixes need to be
# mapped individually in order to avoid them from being hit by the most general (catch-all) rule.
- url: /(.*\.css)
  static_files: dist/projectname/\1
  upload: dist/projectname/(.*\.css)
  secure: always

- url: /(.*\.html)
  static_files: dist/projectname/\1
  upload: dist/projectname/(.*\.html)
  secure: always

- url: /(.*\.ico)
  static_files: dist/projectname/\1
  upload: dist/projectname/(.*\.ico)
  secure: always

- url: /(.*\.js)
  static_files: dist/projectname/\1
  upload: dist/projectname/(.*\.js)
  secure: always

- url: /(.*\.txt)
  static_files: dist/projectname/\1
  upload: dist/projectname/(.*\.txt)
  secure: always

# Site root.
- url: /
  static_files: dist/projectname/index.html
  upload: dist/projectname/index.html
  secure: always

# Catch-all rule, responsible from handling Angular application routes (deeplinks).
- url: /.*
  static_files: dist/projectname/index.html
  upload: dist/projectname/index.html
  secure: always

skip_files:
- ^(?!dist)

当我将 cloudbuild.yaml 更新到以下时，我得到以下错误

steps:

- name: "gcr.io/cloud-builders/npm:node-12.18.3"
  entrypoint: npm
  args: ['install']

- name: gcr.io/cloud-builders/npm
  args: [run, build, --prod]

- name: gcr.io/cloud-builders/gcloud
  args: [ app, deploy, --version=$SHORT_SHA ]


ERROR in ./src/styles.scss (./node_modules/@angular-devkit/build-angular/src/angular-cli-files/plugins/raw-css-loader.js!./node_modules/postcss-loader/src??embedded!./node_modules/sass-loader/lib/loader.js??ref--14-3!./src/styles.scss)
Module build failed (from ./node_modules/sass-loader/lib/loader.js):
Error: Node Sass does not yet support your current environment: Linux 64-bit with Unsupported runtime (83)
For more information on which environments are supported please see:
https://github.com/sass/node-sass/releases/tag/v4.12.0

【问题讨论】：

你能在运行 NPM 构建命令后分享你的 Bucket 的目录树吗？我可以回答你，但我需要知道目录树才能提供正确的！

你是指angular.json文件还是dist文件夹？

请看一下编辑区，如果这是你想要的。

好的，但是您的编辑是您的 GCS 存储或 git 存储库的目录树？

它属于 git repo

【参考方案1】：

使用下面不会引发错误，但甚至不会生成。

  args: ["build", "--prod"]

替换以下任何作品

  args: ["run", "build", "--prod"]

或

  args: [run, build, --prod]

我的最终 cloudbuild.yaml

steps:

- name: gcr.io/cloud-builders/npm
  args: [ install ]

- name: gcr.io/cloud-builders/npm
  args: [ run, build, --prod]

- name: gcr.io/cloud-builders/gcloud
  args: [ app, deploy, --version=$SHORT_SHA ]
  

app.yaml

runtime: python27
threadsafe: yes
api_version: 1

# Google App Engine's cache default expiration time is 10 minutes. It's suitable for most Production
# scenarios, but a shorter TTL may be desired for Development and QA, as it allows us to see a fresh
# code in action just a minute after the deployment.
default_expiration: 60s

handlers:
    # Static files located in the root folder are retrieved directly from there, but their suffixes need to be
    # mapped individually in order to avoid them from being hit by the most general (catch-all) rule.
    - url: /(.*\.css)
      static_files: dist/projectname/\1
      upload: dist/projectname/(.*\.css)
      secure: always
    
    - url: /(.*\.html)
      static_files: dist/projectname/\1
      upload: dist/projectname/(.*\.html)
      secure: always
    
    - url: /(.*\.ico)
      static_files: dist/projectname/\1
      upload: dist/projectname/(.*\.ico)
      secure: always
    
    - url: /(.*\.js)
      static_files: dist/projectname/\1
      upload: dist/projectname/(.*\.js)
      secure: always
    
    - url: /(.*\.txt)
      static_files: dist/projectname/\1
      upload: dist/projectname/(.*\.txt)
      secure: always
    
    # Site root.
    - url: /
      static_files: dist/projectname/index.html
      upload: dist/projectname/index.html
      secure: always
    
    # Catch-all rule, responsible from handling Angular application routes (deeplinks).
    - url: /.*
      static_files: dist/projectname/index.html
      upload: dist/projectname/index.html
      secure: always
    
    skip_files:
    - ^(?!dist)

我遇到了一些与包裹相关的错误 - 我通过更新合适的版本来修复它

我遇到了角度错误 云构建发生未处理的异常：找不到模块'@angular/compiler-cli/src/tooling'

这是由于缓存造成的，因此您应该重新安装/更新模块。 Error: Cannot find module '@angular/compiler-cli 如果没有任何效果，请尝试创建一个新分支并从那里触发它（只需点击并试用）。

【讨论】：

这会将项目部署到工作区/，但我无法直接从外壳或编辑器访问它，因为它不可见。不确定我们是否可以访问它，或者我们必须更改设置才能访问它。

【参考方案2】：

会有帮助吗？

// Excerpt app-routing.module.ts

@NgModule(
  imports: [
    RouterModule.forRoot(routes, 
      useHash: true,
    ),
  ],
  exports: [RouterModule],
)

【讨论】：

这没有帮助！

您能否提供一个最小的可重现代码示例作为起点，例如stackblitz.com 中的一个 Angular 项目。这样就更容易为您提供帮助了。