I'm sorry but I disagree. The only real solution is that deployment should fail and rollback if it cannot complete the task.
Perpetrating the illusion that the deployment was successful when in fact it wasn't is not only disingenuous (unintentional as it may be) but it is also extremely dangerous. Here is one example: I use Eclipse along with the AppEngine plugin. Of all the times that I deployed and the index creation process was stuck after deployment was there nary one message or warning. In fact, if I were to have just gone by the status reported by the plugin I never would have checked the admin console and have learned that all was not well and that my app was not really installed and ready to serve new requests. Good sense learned from having received other misleading or ambiguous messages and feedback got me into the habit of always checking the admin console after every deployment. I am greatly appreciative of all the talented Google engineers who contribute to the project and wish to thank them for their effort and good intentions. I am also a huge proponent of AppEngine and I have bet a majority of the acreage of my farm on it but all is not well with it and to ignore that and to not urge Google to acknowledge that and to act upon that as to correct it would be foolish. I urge Google to focus on the issues that compromise the system first before providing any new features or services. I also urge Google to curtail or eliminate any charges for AppEngine while it is still in beta or preview mode. I don't believe that we who are in effect customers should be charged for what can only be described as goods that are severely damaged at this time. Jeff On Sat, Jun 26, 2010 at 6:19 AM, Jody Belka <[email protected]> wrote: > What you can do of course, is deploy the new version but don't make it live > until the indexes are ready > > On 26 June 2010 00:09, Jeff Schwartz <[email protected]> wrote: > >> LOL. I hear you, man, and sympathize with you completely. There's nothing >> more annoying than having to wait for the prod server to complete an update, >> especially when you are as you say doing spot testing. >> >> The other issue I have is with the chance that with every new deployment >> the index building phase can take a long time yet your new code is ready to >> serve requests. That is totally unacceptable. That is not what I would call >> a real production environment. If you cannot deploy your app to production >> with the guarantee that all the pieces will come together at the same time >> then the system obviously isn't ready for production applications. Who can >> deploy an app with code that makes use of database features such as the >> availability of an index if they can not guarantee the indexes will be ready >> to serve the code. This to me at least is the greatest danger of deploying >> an app on appengine. It is equivalent to a banking system where if you >> transfer money between accounts only one side of the transaction completes >> yet the system treats it like both sides completed. Google needs to correct >> this immediately. >> >> I've said it before and I will say it again, until Google stops calling >> app engine a beta they shouldn't charge for it. Period. >> >> I believe there is great potential in app engine but in its current state >> it is not ready for prime time. >> >> Jeff >> >> >> On Fri, Jun 25, 2010 at 1:18 PM, peterk <[email protected]> wrote: >> >>> ..Well, forever meaning several minutes. I'm trying to update my app >>> at the moment and it's currently taking 7 minutes and counting. It's >>> been like this for the last day. >>> >>> I can only test some things on a live environment. Several minutes of >>> update time makes for terrible turnaround time on tweak testing. It's >>> driving me nuts! >>> >>> Please fix, Google? :\ >>> >>> -- >>> 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]<google-appengine%[email protected]> >>> . >>> For more options, visit this group at >>> http://groups.google.com/group/google-appengine?hl=en. >>> >>> >> >> >> -- >> -- >> Jeff >> >> -- >> 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]<google-appengine%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/google-appengine?hl=en. >> > > -- > 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]<google-appengine%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- -- Jeff -- 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.
