Closed GoogleCodeExporter closed 8 years ago
Can you verify that your current user (`gcloud config list
--format='value(core.account)'`) has "EDITOR" or "OWNER" permission on your
current project (the argument to `--project`)? You can see this permission in
the Cloud Developers Console (https://console.developers.google.com/).
Have you ever seen a deployment work using this user/project combination? Or
has this bug always been present.
Original comment by z...@google.com
on 30 Nov 2015 at 8:59
Yes, I am the current user, and I have owner permission on the project. I've
always successfully deployed this project via the Google Plugin for Eclipse but
have never successfully deployed via gcloud. I'm trying to move to a push to
deploy workflow and have everything working except for the gcloud deployment
step.
Todd
Original comment by todd.eve...@gmail.com
on 30 Nov 2015 at 9:25
We're going to have our server-side team take a look at this.
When you say "a push-to-deploy" workflow, what do you mean? Is there a
particular set of instructions that you're following? How did you log in on the
machine that's performing the gcloud step (ex. via "gcloud auth login" or via a
service account)?
Original comment by z...@google.com
on 30 Nov 2015 at 10:08
I'm following the instructions here closely:
https://cloud.google.com/tools/cloud-repositories/docs/push-to-deploy. One
excpetion is that I'm not using 'mvn gcloud:deploy' to deploy because I'm using
Gradle.
The 403 error occurs whether I attempt to deploy via Bitnami Jenkins or via my
local Google Cloud SDK shell.
Thanks for your help!
Todd
Original comment by todd.eve...@gmail.com
on 30 Nov 2015 at 10:16
Original issue reported on code.google.com by
todd.eve...@gmail.com
on 29 Nov 2015 at 12:57