With Google rapidly expanding their cloud service coverage, Buddy keeps up the pace with dedicated integrations for Google developers. Currently, we support 4 Google Cloud integrations: Cloud Storage, Compute Engine, App Engine, and Container Registry. Just like with AWS, we'll be adding more integrations, depending on the feedback from the community.

Deploy to GCS (Google Cloud Storage)

Google Cloud Storage is a unified object storage service for developers and enterprises. It offers four types of storage: Multi-regional, ideal for frequently accessed website assets like videos; Regional, ideal for cloud developers because of its availability and performance; and Nearline/Coldline storages for rarely accessed data.

Example pipeline:

The project is PHP. Static assets, such as videos, PDFs, Javascript, CSS and image files are kept in a multi-regional GCS account. On every push to the master, branch Buddy will test and upload your website to the SFTP server + and update assets on GCE. Here's a video demonstrating automatic GCE deployments:

Deploy to GCE (Google Compute Engine)

Google Compute Engine – an equivalent of AWS EC2 – is a virtual machine in Google Cloud that you can connect to via SFTP and use to serve your application.

Example pipeline:

The project is Java/Maven. The application in the form of a .war file is uploaded to the GCE and restarted with an SSH script on every push to the repository:

Example pipeline with GCE deployment
Example pipeline with GCE deployment

Deploy to GAE (Google App Engine)

Google App Engine lets developers upload, build and serve web and mobile backends on Google's infrastructure. The service is similar to Heroku or Amazon's Elastic Beanstalk.

Example pipeline:

With Buddy, you can automate deployments to GAE using a dedicated file transfer action. Just like in previous actions, you can upload your package automatically on push to the selected branch or a wildcard pattern, on demand, or recurrently at a specific time.

GAE action details
GAE action details

Build and push Docker image to GCR (Google Container Registry)

To build a Docker image, you need a repository with the application code and a dockerfile with instructions how the image should be built. You can configure Buddy to build a new Docker image and push it to the GCR on every push to the selected branch. It's also possible to add an SSH action that will pull the Docker image on the selected host and launch the new version of the application.

You can read more about building Docker images in this article.

Selecting GCR registry in Docker image build action
Selecting GCR registry in Docker image build action