Thanks David. So I had to read a lot of Google cloud SDK code to figure out how GAE, CloudBuild, GCR and GCS are used to orchestrate a deployment onto GAE.
I'm doing all this because the files in GCS and GCR cost money, that storage is not free. So I'd like to understand it. My questions have narrowed down to the following: 1) During `app deploy`, CloudBuild fetches source files from GCS, builds images (or uses cached ones if any in GCR), and pushes the latest image to GCR under the `ttl-2h` folder. I see that this ttl is respected for most images there, except the ones from 2 most recent builds. Why is this? 2) Following point 1, it seems all images are stored in cloud also (maybe under us.artifacts?), but that's not free: https://cloud.google.com/container-registry/pricing. So can you point to any documentation to explain us.artifacts bucket and what temp files are in there? 3) Link you shared for default and staging buckets only mentions pricing on the default bucket (which btw is always empty). Can you share any information on the pricing of staging and us.artifacts bucket? Are those free since they're used for intermediate steps which I have no visibility into? Thanks in advance! On Thursday, April 23, 2020 at 10:41:20 AM UTC-4, David (Cloud Platform Support) wrote: > > Hello, > > Here is some information about the default and staging buckets > <https://cloud.google.com/appengine/docs/standard/python3/using-cloud-storage#default_bucket>. > > As for the artifact, this is a bucket for the build cache which holds > intermediary build output. The staging and artifact buckets hold temporary > files which are part of the deployment process. It is not recommended to > delete any of these buckets but it won’t break your project if you do. > > Manually running the command "gcloud app deploy" should check for any file > changes and only upload those files that were updated. The behavior may be > different if done from a Cloud Build step. In this case, it would need to > use previous builds in order to speed up the building time. For more > information about making your builds faster, please see our documentation on > best > practices for speeding up builds > <https://cloud.google.com/cloud-build/docs/speeding-up-builds>. > > Please review this document about running Django on GAE standard > <https://cloud.google.com/python/django/appengine#deploying_the_app_to_the_standard_environment_> > > which provides information about Django's collectstatic. Build steps wise: > > > > args: ['-m', 'pip', 'install', '-t', '.', '-r', 'requirements.txt'] > > args: ['./manage.py', 'collectstatic', '--noinput'] > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/1c7e9dad-f43b-4014-9a99-72dec25e4ae6%40googlegroups.com.
