How to defend against deployment-specific production bugs

[Carter]

Is there a way to deploy Task Queue definitions separately from the
deployment of the whole application?

We plan to start alternating app versions with each and every
deployment as a way to defend against deployment-specific bugs.
However, we have both Python and Java verions of our overall system
that run concurrently as two different app versions. They rely on
being able to pass work between the two versions by by assigning
<target></target> values for each of the Task Queues.

So while we'd like to alternate versions with each deployment so that
we can canary-test in production before switching to the new version,
it appears that we would have to re-deploy just to update the version
numbers in the queue.xml configuration - which would defeat the
safeguard because we'd be deploying again.

thanks for any tips,
Carter

p.s. - we were motivated to come up with a strategy after experiencing
the "CSS null mimi-type" deployment bug that was fixed with Java SDK
fixed by 1.6.1.1

[Kaan Soral]

What kind of deployment bugs are there?

[Cayden Meyer]

You can use appcfg update_queues to just update queue definitions.
However, there is no way to omit queue.yaml/xml changes from appcfg
update (the more general version deployment).

I am curious to hear what kind of deployment bugs you are seeing.

Cayden Meyer
Product Manager, Google App Engine

[Carter Maslan]

Thank you for the appcfg update_queues tip; we will try that out.

We have had only one deployment bug that was corrected:

https://groups.google.com/d/msg/google-appengine-java/bW6T0W_Z6Ec/BY_jLu6QTJMJ

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To post to this group, send email to google-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.