如何解决如何访问从Firebase函数生成的Google Cloud Build日志文件
我的Google Build脚本陷入了他与Angular通用项目服务器之间的僵局。我正在尝试访问日志,也许有助于解决问题。
编辑#1
这是一个Angular项目,此构建是基于Firebase函数的Angular通用构建
Starting Step #6
Step #6: Already have image: node:12.3
Step #6:
Step #6: > supportfinity@0.0.0 stage-server /workspace
Step #6: > node --max_old_space_size=8000 ./node_modules/@angular/cli/bin/ng run sf-mini:server:stage
Step #6:
Step #6: Compiling angular2-query-builder : main as umd
Step #6: Killed
Step #6: npm ERR! code ELIFECYCLE
Step #6: npm ERR! errno 137
Step #6: npm ERR! supportfinity@0.0.0 stage-server: `node --max_old_space_size=8000 ./node_modules/@angular/cli/bin/ng run sf-mini:server:stage`
Step #6: npm ERR! Exit status 137
Step #6: npm ERR!
Step #6: npm ERR! Failed at the supportfinity@0.0.0 stage-server script.
Step #6: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
Step #6:
Step #6: npm ERR! A complete log of this run can be found in:
Step #6: npm ERR! /builder/home/.npm/_logs/2020-10-05T12_48_55_502Z-debug.log
Finished Step #6
如何访问上面的日志。
这也是构建yaml:
steps:
- name: 'gcr.io/cloud-builders/docker'
args: [ 'build','-t','gcr.io/$PROJECT_ID/firebase','./dockerfiles/firebase']
- name: 'gcr.io/$PROJECT_ID/firebase'
args: [ 'use','$_PROJECT_NAME','--token','${_FIREBASE_TOKEN}']
- name: 'node:12.3'
entrypoint: npm
args: ['install']
- name: 'node:12.3'
entrypoint: npm
args: ['install','--prefix','functions']
- name: 'node:12.3'
entrypoint: npm
args: ['link']
- name: 'node:12.3'
entrypoint: npm
args: ['run-script','stage-browser']
- name: 'node:12.3'
entrypoint: npm
args: ['run-script','--debug','build-server'] <== this one which cause problem
- name: 'node:12.3'
entrypoint: npm
dir: 'functions'
args: ['run-script','copyAndRename']
- name: 'gcr.io/$PROJECT_ID/firebase'
args: [ 'deploy','${_FIREBASE_TOKEN}']
timeout: 2000s
从package.json构建命令
"build-server": "node --max_old_space_size=16384 ./node_modules/@angular/cli/bin/ng run sf-mini:server:production","stage-browser": "node --max_old_space_size=8000 ./node_modules/@angular/cli/bin/ng build --prod --configuration=stage --aot --vendor-chunk --common-chunk --delete-output-path",
解决方法
可能是内存问题。有几个GitHub [1] [2]个错误代码为137的问题,他们能够通过增加其RAM来解决。
编辑:
如评论中所述,您将无法访问/builder
日志,因为单独的VM将运行构建步骤。
但是,这可以帮助您了解导致问题的原因。 Firebase Functions中的有效最大内存值为2GB,但是您使用--max_old_space_size
将内存增加到16GB (构建)和8GB (阶段) 。这可以帮助解释为什么您无法从内存中获取代码。
版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。