Thank you Nick! We're back to deploying happily. We had 11 major versions because we never saw/used the now obvious delete button on the Versions management page. Now our versions are down to a tidy 2.
For future searchers who see this post, here are three tidbits that I had not known about: "App Engine deployment too many versions possibilities as well as app.yaml versions" ... 1) You should delete versions when you no longer need them. 2) Versions need not be monotonically increasing or even be integers ... you can go with two versions whose names are "production" and "staging" and cycle back and forth. 3) If you see a "Too Many Versions (403)" message, delete versions that you do not need and try again. One question that remains to be answered via this trail or the documentation is whether or not you can potentially see a "Too Many Versions" message if you have too many minor versions (the versions that are incremented every time you do a deploy to a major version). If you're here and you have only a couple major versions, you might be in a (major) minor version logjam ... but I am *not* sure whether or not that is possible... If there is a wiki version of the docs that anybody is keeping out there, I'd be happy to insert (1) - (3) into the documentation appropriate! On May 20, 9:38 am, "Nick Johnson (Google)" <[email protected]> wrote: > How many major versions do you have active on App Engine? It's not > really intended that you have 10+ active versions of an app - once > you're done with an old version, you should delete it. > > Also note - if it's helpful - that major version names are strings, > not integers, so you can name your versions as you wish. I typically > use "trunk" and "live", which gives me a stable name for my > in-development work. Once I've verified a release doesn't break > anything, I just redeploy to 'live'. > > -Nick Johnson > > > > On Tue, May 19, 2009 at 10:57 PM, Joe <[email protected]> wrote: > > > Is anybody else seeing a "Too Many Versions (403)" error when they > > attempt a deploy? It's happening for me on version 11 of my app, even > > though this would be only the second mini-version within 11 ... and I > > tried bumping my version up to 12 to see if it was a bug specific to > > version 11 ... but I still received the error. I cannot go back to > > version 10 and test that direction because 10 is in production and I'd > > hate to lose... > > > In the App Engine issue tracker, this is related to #744, I think... > > And, I put a comment up there yesterday but have not heard anything so > > I'm putting it out here for the community because it's a show-stopping > > kind of thing. Anyone else seen this kind of bug in deployment and > > found a workaround? > > > Thank y'all kindly! > > > Oh, just in case folks want to take a peek, here's a link directly to > > my issue tracker comment ... it includes debug output and app name: > > >http://code.google.com/p/googleappengine/issues/detail?id=744&q=too%2... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
