At work we use CloudFoundry as our PaaS, but I also like to keep informed about what other platforms do.
Google AppEngine Introduces Push-To-Deploy
Google AppEngine recently added an interesting feature: Push-to-Deploy through Git.
With Push-To-Deploy, you can simply push your code to a Git repository to get your code deployed on AppEngine.
This Git repository is maintained by Google and tied to your cloud account. I guess this is implemented using the
post-receive Git server hook.
Push-To-Deploy Removes Friction
What I like about this feature is that it removes some friction from the deployment process: you no longer need to know about how to deploy your application on AppEngine.
Push-To-Deploy inches us closer to a Frictionless Development Environment (FDE). The two most likely candidates to become the FDE of choice both support Git, so it’s easy to use Push-To-Deploy in both Orion and Cloud9.
More Friction Remains
Of course, this is only a small step and a lot more work needs to be done before we really have an FDE.
In my ideal world, for any change that I make the FDE would automatically run the tests and code checkers in the background and, when successful, push the changes to a development branch to make them available for my co-workers.
To make this efficient, only tests that could potentially have been impacted by the changes would run, and they would run in parallel in the cloud. When specified criteria are matched, changes on the development branch would propagate to master and, using Push-To-Deploy, to production.
Although this is all far far away, every step is to be applauded, and I hope other PaaS providers will follow Google’s example.
What Do You Think?
Do you use Google AppEngine? Git? Would you use Push-To-Deploy? Would you like to see a similar feature in CloudFoundry or another PaaS?
Please leave a comment.
You must be logged in to post a comment.