Open GoogleCodeExporter opened 8 years ago
Thank you for reporting this. We will track this and get it fixed soon.
Original comment by vil...@google.com
on 15 Jan 2016 at 4:05
Issue 475 has been merged into this issue.
Original comment by vil...@google.com
on 19 Jan 2016 at 3:59
I'm running into the same issue. I don't understand why
"golang.org/x/net/context" can't be imported.
Original comment by ib...@google.com
on 26 Jan 2016 at 7:19
@#3: My solution to the import error was to stop using gcloud deploy and go
back to using the old appcfg.py script.
See this issue I created for the compilation issue:
https://code.google.com/p/googleappengine/issues/detail?id=12670
Original comment by m...@blixt.org
on 26 Jan 2016 at 2:50
@#3: Thanks for the info.
I'm using Jenkins to deploy to AppEngine and I am running the
"bitnami-jenkins". I tried using appcfg.py or goapp and got the following
error (or related appcfg.py not found):
/tmp/hudson3160291730849678757.sh: 2: /tmp/hudson3160291730849678757.sh: goapp:
not found.
So then I found this:
https://community.bitnami.com/t/push-to-deploy-with-bitnami-jenkins-image/38931
detailing that the Docker containers don't contain the Google App Engine SDK so
I can't use goapp or appcfg.py unless I install it.
Though I feel like I shouldn't have to, I did the steps in the URL and got
Jenkins to see the GAE SDK.
However, it would get to a step where the output read "Getting current resource
limits." and it would just sit there and never move onto the next step.
I feel like the glcoud command shouldn't have this problem should just deploy.
Any thoughts?
if #1/#2 wants any other info or can help resolve this issue, I'm ibjhb@
internally. Please feel free to reach out, I'll be around all day.
Original comment by ib...@google.com
on 26 Jan 2016 at 3:41
Is there a workaround for the original issue reported in this ticket using
gcloud? I am having the same problem
Original comment by iasona...@gmail.com
on 14 Feb 2016 at 4:52
The docs at
https://cloud.google.com/appengine/docs/managed-vms/go/hello-world#running_hello
_world_on_app_engine mention you should use aedeploy.
Original comment by svalen...@google.com
on 18 Feb 2016 at 8:52
That's Managed VMs though. Did anyone try this with non-Managed VMs? Also this
means there are at least four ways to deploy: appcfg.py, goapp deploy,
aedeploy, gcloud preview app deploy...
Original comment by m...@blixt.org
on 18 Feb 2016 at 8:57
`gcloud preview app deploy` is not advertised as a stable command (that's what
the "preview" means: it's in developer preview release right now), and should
not be recommended by any of our docs (except for features, such as Managed
VMs, which are also in preview release).
Original comment by z...@google.com
on 18 Feb 2016 at 10:49
Issue 631 has been merged into this issue.
Original comment by vil...@google.com
on 8 Mar 2016 at 3:49
Original comment by jsche...@google.com
on 14 Mar 2016 at 8:45
Original issue reported on code.google.com by
m...@blixt.org
on 15 Jan 2016 at 1:29