Thanks for the reply, Nick. While connection issues in a cloud environment are to be expected, the > tools we use to make connections should be fault-tolerant although this > isn't always automatically the case. >
Do you mean we should expect these tools to fail? Your post didn't make it quite clear exactly how this manifests, as full > system and logs context were not given. > Well, the appengine push-to-deploy setup, states very clearly, how to use 'gcloud' on a compute-engine instance to deploy to appengine. The attached logs were the output of 'gcloud preview app deploy', as visible on line#7 of the logs. > However, there is enough information to make clear that you need to > contact either Cloud Platform or Bitnami support. You could either try to > report it in the Cloud Platform Public Issue Tracker > <https://code.google.com/p/google-cloud-platform/issues/list>, or use the > recommended path from the documentation > <https://cloud.google.com/launcher/solution/bitnami-launchpad/jenkins>, > which explains: > > That doesn't help a lot Nick. > Either way you will shortly be in touch with someone who can assist you > further. Be sure to provide full context of how you run the deployment, how > you gather the error, all messages which are output, etc. > > Thanks. This should help. Do let me know if you need more info or if you need me to run gcloud in a debug / verbose mode. If there's anything else you feel I could assist with here, feel free to > let me know and I'll do my best to answer any questions. > > Sincerely, > > Nick > Cloud Platform Community Support > > On Monday, March 28, 2016 at 5:55:08 AM UTC-4, Mayank Bhagya wrote: >> >> We face this issue every day. And no, I am not exaggerating. >> EVERY SINGLE DAY! >> >> Every day, from about 12 in the afternoon to 5 in the evening (GMT+0530), >> the push-to-deploy bitnami-jenkins setup complains that it couldn't copy >> files to cloud storage. >> The error is intermittent. Certain deployments succeed in first attempt, >> some others in second and some others don't complete for hours! >> >> Today we have to deploy a critical fix and this thing is not ready to >> deploy! >> >> Here are some logs: >> >> Updating module [default]...- >> Updating module [default]...\ >> Updating module [default]...| >> Updating module [default].../ >> Updating module [default]...- >> Updating module [default]...failed. >> ERROR: (gcloud.preview.app.deploy) Error Response: [13] Errors were >> encountered while copying files to App Engine. >> >> Details: [ >> [ >> { >> "@type": "type.googleapis.com/google.rpc.ResourceInfo", >> "description": "Error reading from Google Cloud Storage.", >> "resourceName": >> "https://storage.googleapis.com/staging.myappname.appspot.com/9daf160fc37b8d609092a9f47367188d596ab34e.jpeg";, >> "resourceType": "file" >> } >> ] >> ] >> >> >> Do you think adding more features and not addressing bugs like these will >> make your customers' life easy? >> Whatever happened to quality. >> Can Google folks be serious enough and understand the impact of such >> issues? >> >> Having downtime in an application is not a joke. >> Not everybody ships with 'beta' quality. >> >> Please look into this issue asap and let me know if you know anything >> from my side. >> > -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/fe42abba-1690-4bdd-852a-e98cba730f54%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
![https://storage.googleapis.com/staging.myappname.appspot.com/9daf160fc37b8d609092a9f47367188d596ab34e.jpeg"](https://storage.googleapis.com/staging.myappname.appspot.com/9daf160fc37b8d609092a9f47367188d596ab34e.jpeg"){kind=link}