Using GitHub for Push-to-Deploy to Google App Engine | Hacker News Reader

Using GitHub for Push-to-Deploy to Google App Engine

googlecloudplatform.blogspot.com

58 pointshashx13 comments

Is there any option to run a test suite before deploying? Otherwise this is about as dangerous as fixing code on a production server.

You typically will only be pushing in to master once the changes have passed through a CI system where you'd run all of your tests.

Most people pass their code to a CI system after it's been pushed. Run your unit tests locally, push your code, run it through your CI system (integration and unit tests, anything else), then push goldbits to production.

Yes, but on a different branch. CI runs tests then merges to master (or whatever branch triggers deployment) and pushes.

Yes. This was demoed at the GCP Live event a few weeks ago. I don't know if it's included in the public offering yet.

Some blog coverage here: http://blog.cloudbees.com/2014/03/jenkins-man-behind-curtain...

(Note: I work on Cloud at Google, although not on this part of it. Thus I'm going to be a little conservative and only discuss things I know we've announced)

edit: Oooooh, or just ask the TL: https://news.ycombinator.com/item?id=7617385

Absolutely. You probably want something like CircleCI (disclaimer: I work there). Here's our doc on deploying to GAE: https://circleci.com/docs/deploy-google-app-engine.

I'm the tech lead for the GitHub integration, I'd be happy to answer any questions.

Is it possible to do custom builds on the GCE instance thats building and deploying your code? I.e. run scripts to minify JS, etc? Or is this something you would do locally and make sure the artifacts were checked into git?

Similarly if you run full functional tests (selenium in a browser), can these be started on the gce instance and be part of the "test" step?

We discourage checking in artifacts (e.g., minified JS) into source control because it defeats the purpose in a lot of ways.

Currently there is no support for custom build/test steps but the builds that are done for Java apps are done using Jenkins so you can imagine that in the fullness of time anything Jenkins supports would also be supported as a pre-deploy step. I don't have any specific details though, as my work has been focused on the GitHub integration.

Thanks for that!

I just tried this stuff out and I can't get it to work. I have a python Django app.

When I push the deploy fails. There's no information on Release History, it just says failed. The duration of the build task is 0 seconds.

If I do locally `appcfg.py update --oauth2 .` it work as usual.

I feel like we need more info when things fail.

Absolutely, this is a big thing we're working on, giving visibility into failures. Having the push go to GitHub means our options for error reporting are a little more limited, unfortunately.

One thing you may want to check is that your app.yaml is in the root directory of the master branch. That's where we look currently to figure out what to deploy.

If you'd like me to investigate further you can email jasonhall@google.com and I'll look into what's going on.

at Codeship (I'm one of the founders) you can run your tests and use our app engine integration to push whenever your tests pass. Setup takes a minute. let me know if you have any questions at flo@codeship.io

Reply on news.ycombinator.com