Closed GoogleCodeExporter closed 8 years ago
Hi there,
Sorry for the confusion.
1. The new flag is `--docker-build=remote` (or `--docker-build=local`).
2. N/A, but in general you can pin to a specific version using the instructions
here: https://cloud.google.com/sdk/#alternative (under the "Alternative
Methods" tab). Any client-side behavior should remain supported indefinitely.
3. When you run `gcloud components update`, the following message is displayed:
For the latest release notes, please visit:
https://dl.google.com/dl/cloudsdk/channels/rapid/RELEASE_NOTES
There is also a RELEASE_NOTES file in the root of your Cloud SDK installation (/root/google-cloud-sdk/RELEASE_NOTES) in this case.
We know that neither of these are in the most prominent place; we plan to add the RELEASE_NOTES to our online documentation very soon, and starting in the upgrade from 0.9.74 to 0.9.75, we'll print out the new additions to the RELEASE_NOTES on upgrade.
Additionally, in this case, `gcloud preview app deploy` printed the following warning for the last two releases:
WARNING: `--remote` flag is deprecated and will be removed in Cloud SDK version 0.9.74. Please use the `--docker-build` flag instead.
The error you're seeing with no arguments is unexpected; please try with
`--docker-build=remote`. If that doesn't work, please downgrade.
Once more, our apologies for any confusion. We're working hard to stabilize
`gcloud app` so that changes of this sort won't happen any more, but some of
the initial goals, technical details, and designs have changed, so there's
going to be a bit of churn (that's why it's still a `preview` command; our
stable commands change very rarely).
Original comment by z...@google.com
on 20 Aug 2015 at 2:49
(One small bit of misinformation in my last post; the RELEASE_NOTES will be
printed starting in the upgrade from 0.9.75->0.9.76, which is one release later
than I specified).
Original comment by z...@google.com
on 20 Aug 2015 at 3:00
Thank you, the --docker-build=remote got me running again. And no problem, I
realize I'm playing with bleeding-edge stuff here. :)
The reason I haven't noticed any of the messages you mention is that my build
is completely automated on Shippable. I don't typically look at the output
unless the build fails -- by which point it was of course too late to see the
helpful message. I don't even have gcloud installed on my dev machine.
The release notes you pointed to are great! Now if only Google Search indexed
them... I guess that will happen once you add them to the docs. It would also
be nice to publish the updates on a newsgroup or some such, so I don't have to
manually poll the doc every few days.
Original comment by pi...@ideanest.com
on 20 Aug 2015 at 8:14
Ahh, makes sense. On our end, we'll look into the following (can't promise
anything yet, though):
1. Make the error for deprecated flags point to the new flags in the future (so
when you ran `--remote`, it'd tell you what the warning had told you
previously), and in general consider your use case (not using gcloud manually
ever).
2. Making a mailing list for new releases.
You're right that RELEASE_NOTES will show up in Google search once we get them
on the web site.
We've fixed the issue you saw where the build was failing without the
`--docker-build=remote` flag failing explicitly; it should be released in
version 0.9.76. In the meantime, please continue to use that flag (it will
continue working indefinitely).
Thanks for bearing with us through this slightly-choppy change.
Original comment by z...@google.com
on 20 Aug 2015 at 8:29
FYI, we've created a mailing list to announce new releases:
https://groups.google.com/forum/#!forum/google-cloud-sdk-announce
Original comment by z...@google.com
on 21 Aug 2015 at 9:21
Original issue reported on code.google.com by
pi...@ideanest.com
on 20 Aug 2015 at 3:25