A FYI about alternating versions for deployment to production...
Our build script names the version according data from SVN (GIT would
be similar), as a working copy (name = data and time), revision
(name=r123), or tag (name = tag name = our release version number).
Then the uploaded versions in
One thing that would make this helpful would be the ability to
automatically delete old versions. The current limit of 10 versions
means I have to manually go through and delete old ones before I can
deploy new ones. It would be nice to automate a scrolling window of
versions.
Of course, not
Ikai -
Our site was unusable for 30 minutes while we quickly downloaded the
1.6.1.1 fix and redeployed with the new SDK.
We could have deployed in two phases with a different version so that we
could have discovered the bug prior to being live.
Is it best practice to alternate between versions
Re: Carter
Going a bit off topic, but in general I have always worked at places that
stage deployments. That is - you have some environment only accessible by
your team that reaches live data after your verification and QA more or
less have determined that in the worse case scenario, your change
thanks for the tips.
We will start alternating versions with each deployment.
I have another question about managing target/target for queues that I
will post under a distinct topic.
thanks,
Carter
On Fri, Jan 13, 2012 at 3:16 PM, Ikai Lan (Google) ika...@google.comwrote:
Re: Carter
Going a
Just to be clear though, in this case, we *should* have been able to trust
the tool (the SDK) to upload the file correctly. I mean there should be
some sort of checks and balances for a system like that.
In this case, I am deploying to my staging system, seeing the problems with
CSS and then
We have an SDK update that resolves this issue on upload (I've also posted
in a separate thread about this):
http://code.google.com/p/googleappengine/downloads/detail?name=appengine-java-sdk-1.6.1.1.zip
--
Ikai Lan
Developer Programs Engineer, Google App Engine
plus.ikailan.com |
I just ran into it after a push, right after everything reset and with the
css mime-type workaround in place.
jon
On Mon, Jan 9, 2012 at 6:19 PM, Matthew Johnson
ijustmakecof...@gmail.comwrote:
Ikai,
I'm using GAP SDK 1.6.1, and so far, I'm the only dev on my team who's
experienced this.
-appengine-java@googlegroups.com
Date: Tue, 10 Jan 2012 16:08:39
To: google-appengine-java@googlegroups.com
Reply-To: google-appengine-java@googlegroups.com
Cc: google-appeng...@googlegroups.com
Subject: Re: [appengine-java] Re: problem with Content-type: null with css files
If someone has
Ikai, I sent you my testcase some days ago (it's still broken). Can't you
use it? Didn't get any feedback from you?
I'm pretty sure:
- It's a SDK 1.6.1 issue (didn't get it before, but got it now from time
to time when doing deployments)
- It seems to be Java only
- It seems to be a
Just to update this thread with info from another thread:
We think we know what's happening. This is something that is happening at
app upload time. Can you try setting a new version name for your app, then
passing the --no_batch option when using appcfg.sh?
appcfg.sh --no_batch update
We think we know what's happening. This is something that is happening at
app upload time. Can you try setting a new version name for your app, then
passing the --no_batch option when using appcfg.sh?
appcfg.sh --no_batch update [YOUR_WAR_DIRECTORY]
Seems to solve it. I can't reproduce the
For those affected, it looks like a workaround is to add the following to
your web.xml:
mime-mapping
extensioncss/extension
mime-typetext/css/mime-type
/mime-mapping
On Mon, Jan 2, 2012 at 3:19 PM, Jon Stevens latch...@gmail.com wrote:
Well, it seems it isn't just me, so I just filed a
Just did that, redeployed and it didn't fix anything.
Edited the part below to have extension.css/extension (adding a
period) and now the workaround to the workaround works.
jon
On Mon, Jan 9, 2012 at 3:16 PM, Amy Unruh amyu+gro...@google.com wrote:
For those affected, it looks like a
Are you all on the 1.6.1 SDK? Is someone experiencing this deploying with
an older SDK?
If someone has a deterministically reproducible case that you can share
with us (project files and everything), it'd be very helpful for us to nail
this bug. We aren't able to do this with our test apps (big
Jon, FYI, this fix didn't work for me until I incremented the version number.
Then it worked great.
Cheers,
Matt
On Jan 9, 2012, at 4:39 PM, Jon Stevens wrote:
Just did that, redeployed and it didn't fix anything.
Edited the part below to have extension.css/extension (adding a period)
It sounds like the data about this XML snippet is still inconclusive.
- Jon Stevens reports that if you change the extension to .css, it works
- Matt, in addition to using Jon's fix to the fix, you needed to increment
the version to fix the broken mime-type
So it's possible the XML snippet might
I have no idea how your internal systems work, but I'd look into the code
which sets the Content-Type header and see what could possibly set it to
null or not set it at all and then work back from there.
Some more data points for reproduction?
My css file is fairly large since I have one file
Ikai,
I'm using GAP SDK 1.6.1, and so far, I'm the only dev on my team who's
experienced this.
Sorry I wasn't clear in my earlier reply to Jon. I did NOT need to use Jon's
fix; my mime-mapping entry (seemed to) work fine without the period, but only
AFTER I incremented the version number. I
If someone has a deterministically reproducible case that you can share with
us (project files and everything), it'd be very helpful for us to nail this
bug. We aren't able to do this with our test apps (big apps, small apps).
There's got to be some parameter that's different in your apps.
I
I'm seeing this as well. It garbles up the whole page
http://www.zivvit.com/css/main.css
Any headway? I checked to make sure my file was encoded fine and
everything. Not sure what's going on here... Seems like a bug in the
static file distribution system.
On Dec 24, 4:48 pm, jon stevens
I got it working again by updating the version number in my appengine-
web.xml and pushing the new version. Still have no idea what happened
here.
-J
On Dec 24, 4:48 pm, jon stevens latch...@gmail.com wrote:
Hey there,
I've got an app up on GAE-J that when I request a .css file, I get back a
we had the same problem and it was solved by updating the css file (with a
space) and pushing again (without an app version change). Appreciate any info
you find on preventing this problem. It behaved as though it was a problem in
GAE's caching of static files.
On Dec 30, 2011, at 8:34 PM,
Well, it seems it isn't just me, so I just filed a ticket:
http://code.google.com/p/googleappengine/issues/detail?id=6655
Please star it.
jon
On Sun, Jan 1, 2012 at 8:13 PM, Carter Maslan jcmas...@gmail.com wrote:
we had the same problem and it was solved by updating the css file (with a
24 matches
Mail list logo
