Duannx
Duannx

Reputation: 8726

Google Cloud Build show no logs

I have a Google Cloud Trigger that triggers cloud build on Github push.

The problem is that the Cloud Build shows no logs. I followed this doc but can not find any logs on neither the Cloud Build log nor the Logs Explorer (see the image below)

enter image description here

This is my cloudbuild.yaml

steps:
# install dependencies
- name: node:16
  entrypoint: yarn
  args: []
# create .env file
- name: 'ubuntu'
  args: ['bash', './makeEnv.sh']
  env: 
    - 'GCP_SHOPIFY_STOREFRONT_ACCESS_TOKEN=$_GCP_SHOPIFY_STOREFRONT_ACCESS_TOKEN'
    - 'GCP_SHOPIFY_DOMAIN=$_GCP_SHOPIFY_DOMAIN'
# build code
- name: node:16
  entrypoint: yarn
  args: ["build"]
# deploy to gcp
- name: 'gcr.io/google.com/cloudsdktool/cloud-sdk'
  entrypoint: 'bash'
  args: ['-c', 'gcloud config set app/cloud_build_timeout 1600 && gcloud app deploy --promote']
timeout: "1600s"
options:
  logging: CLOUD_LOGGING_ONLY

The build failed but it actually create a subsequence App Engine build that successfully deploy a version to App Engine. But that version is not auto-promoted (see the image below)

enter image description here

Upvotes: 2

Views: 2692

Answers (2)

Zymotik
Zymotik

Reputation: 7307

In my case, looking at the Google Cloud Build Service Account ([email protected]) in the Google Cloud IAM console, it was missing the role Cloud Build Service Account. I was also missing logs.

This fixed symptom of a cloud function deploy with the message:

(gcloud.functions.deploy) OperationError: code=3, message=Build failed: {
   "metrics":{},
   "error":{
      "buildpackId":"",
      "buildpackVersion":"",
      "errorType":"OK",
      "canonicalCode":"OK",
      "errorId":"",
      "errorMessage":""
   }
}

Upvotes: 3

Sudhanshu Yadav
Sudhanshu Yadav

Reputation: 568

I do not have all the details, so trying to help with all the above information mentioned.

As I can see you are using CLOUD_LOGGING_ONLY and not been able to see the log in the log explorer and considering you have all the permissions to access the logs.

I would suggest you to look into the service account that you are using for cloud build must at least have the role: role/logging.logWriter or permission:logging.logEntries.create permission if it is not the default cloud build SA [email protected].

Hope this helps :)

Upvotes: 4

Related Questions