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

[timdorr]

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

[jsolson → timdorr]

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

[pbiggar → timdorr]

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.

[djb_hackernews → timdorr]

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.

[bacongobbler → djb_hackernews]

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.

[robinson-wall → bacongobbler]

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