Yes, I saw that SO issue but I couldn't work out what the correct dir: value should be.
In both cases the app deploy successfully but in the second case when accessing the url I receive a 500 error and the deployed code is only ~600 bytes which suggests to me it's deployed an empty folder or something like that. This leads me to believe I need to specify the source for the build step, but if I am running the cloudbuild from within a subfolder how do I escape up the folder tree, e.g. ../../ ? On Friday, May 29, 2020 at 2:29:28 PM UTC+1, Olu wrote: > > Hello, Alex > > Can you please provide the specific error obtained while using your second > setup that is failing? This will provide more context. Yes, as indicated in > this Stackoverflow link[1], it is necessary to specify the DIR in the > Cloudbuild.yaml whenever you are trying to trigger your build configuration > in a subdirectory. Additionally, with information available to me, I > understand you cannot have the app.yaml and the cloudbuild.yaml in the same > directory if you are deploying in a non-custom runtime > > [1] > https://stackoverflow.com/questions/52725046/google-cloud-builder-how-to-trigger-build-configuration-in-a-subdirectory > -- 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 google-appengine+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/4a8f5338-1c96-4c00-8857-6705400a464e%40googlegroups.com.
