如何解决尝试使用云构建 (gcp) 进行部署时出现未找到的 URL
应用程序 - Angular
我正在尝试在 GCP 中自动执行我的 angular 应用程序的部署过程。当我从云 shell 手动部署时,一切正常,但是当我尝试使用 cloudbuild.yaml 进行构建部署时,云构建会触发它说部署成功。当我点击 URL 时,它说 404 not found。
手动部署命令
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
解决方法
在下面使用不会引发错误,但甚至不会构建。
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,--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 如果没有任何效果,请尝试创建一个新分支并从那里触发它(只需点击并试用即可)。
,这有帮助吗?
// Excerpt app-routing.module.ts
@NgModule({
imports: [
RouterModule.forRoot(routes,{
useHash: true,}),],exports: [RouterModule],})
版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。