Cloud Run Deployment with Auto DevOps

1 post · Aug 2017 – Jan 2025

What this trail covers

GitLab Auto DevOps is being enabled by default for all users, starting with gitlab.com and then for self-managed customers. This aims to ensure all users benefit from its automated build, test, and monitoring capabilities. The system will disable Auto DevOps automatically if a pipeline fails, notifying the project owner to allow for necessary configuration changes. This post details how to deploy a PHP application to Google Cloud Run using GitLab CI/CD, leveraging the Google Cloud integration for service account creation and Cloud Run deployment via merge requests.

All GitLab trails

Jan 2025Deploy a server using Go with GitLab + Google CloudThis post details the practical steps for a developer to deploy a Go server to Google Cloud Run using GitLab CI/CD. It covers creating a GitLab project, writing a basic Go server, using GitLab's Google Cloud integration to create a service account and configure Cloud Run via a merge request, and accessing the deployed service. It also includes instructions for cleaning up the environment and extending the Go server with a new endpoint.
Jan 2025Google Cloud integrations for secure Cloud Run deployments at GitLabThis post details how to integrate GitLab CI/CD with Google Cloud's Workload Identity Federation, Artifact Registry, and Cloud Run for secure deployments. It provides step-by-step instructions for configuring the integrations within GitLab and Google Cloud, and outlines the `.gitlab-ci.yaml` configuration for building, uploading, and deploying containerized applications to Cloud Run. The post emphasizes the use of CI/CD components for automation and security assurance.
Jan 2025Deploy a NodeJS Express app with GitLab's Cloud Run integrationThis post details how to deploy a NodeJS application to Google Cloud Run using GitLab CI/CD and the Google Cloud integration. It outlines the steps for creating a project, setting up the application with a specific CI template, configuring a Google Cloud Service Account via GitLab's integration, and deploying to Cloud Run through a merge request. It also provides an example of adding a new endpoint and a cleanup guide.
Dec 2024How to deploy a PHP app using GitLab's Cloud Run integrationThis post details how to deploy a PHP application to Google Cloud Run using GitLab CI/CD. It outlines the steps for creating a GitLab project, setting up a basic PHP application, utilizing the GitLab Google Cloud integration to create a service account and configure Cloud Run via a merge request, and then deploying the application. It also demonstrates how to add another endpoint to the application and redeploy it.
Nov 2024Fast Python Flask server deployment with GitLab + Google CloudThis post details the process of deploying a Python Flask application to Google Cloud Run using GitLab CI/CD. It covers creating a GitLab project, setting up a basic Flask server with `main.py` and `requirements.txt`, configuring a Google Cloud Service Account through GitLab's integration, and deploying to Cloud Run via a merge request. The post highlights the automation of these steps, enabling developers to deploy applications quickly and efficiently.
Advertisement
Aug 2023How to secure Google Cloud Run deployment with GitLab Auto DevOpsThis post details the technical steps for securing a Google Cloud Run deployment using GitLab Auto DevOps. It outlines the prerequisites, including Google Cloud project setup and service account configuration. The core contribution is the step-by-step guide on modifying the `gitlab-ci.yml` file to include the Auto DevOps template, configure necessary environment variables (`BASE64_GOOGLE_CLOUD_CREDENTIALS`, `PROJECT_ID`, `SERVICE_ID`), and script the deployment process using `gcloud` commands for authentication, image submission, and Cloud Run deployment. It also covers the integration of DAST with specific variables for full and browser scans.
Oct 2022GitLab & Google Cloud partnership accelerates cloud adoptionThis post details the integration of GitLab Auto DevOps with Google Cloud Run, outlining the steps for configuring Google Cloud credentials, adding the Auto DevOps template, setting up environment variables, and customizing the CI/CD pipeline for deployment. It also mentions the integration of DAST for enhanced security.
Jun 2022How to automate software delivery using Quarkus and GitLabThis post details the steps to automate the software delivery of a Quarkus application using GitLab Auto DevOps. It covers generating a Quarkus project via code.quarkus.io, uploading it to GitLab, configuring a DOCKERFILE_PATH CI/CD variable, modifying the Dockerfile.jvm for a build stage and updated copy paths, creating an .gitlab/auto-deploy-values.yaml file to set the service internalPort to 8080, adding a system.properties file to set the Java runtime version to 11, and enabling the Default to Auto DevOps pipeline with a specific deployment strategy.
May 2021Auto DevOps: Where we are and where we are headedThis post details user feedback on Auto DevOps, highlighting issues with speed, troubleshooting, scalability, and limited deployment targets (primarily Kubernetes). It discusses the value users derive from Auto DevOps templates and the need for more flexible customization and support for diverse deployment targets beyond Kubernetes, such as application stores, simple package creation, and Lambda functions. The post announces a design sprint to reimagine Auto DevOps and invites community discussion.
Nov 2020Adapting Auto DevOps & managed apps to Helm repo changesThis post details the impact of the Helm Stable repository's removal on GitLab Auto DevOps and Managed Apps. It outlines the mitigation strategy implemented by GitLab, which involves switching to a GitLab-maintained Helm Stable Archive repository. Specific instructions are provided for users to update their GitLab versions or CI/CD configurations to resolve potential pipeline failures related to fetching Helm charts. The post also clarifies which users and applications are not affected by this change.
May 2020Deploying apps to GitLab-managed Amazon EKS with Auto DevOpsThis post details the practical steps for deploying a Ruby application to a GitLab-managed Amazon EKS cluster using Auto DevOps. It covers setting up the project by importing a sample application, enabling the Auto DevOps pipeline, and configuring the base domain and Route 53 alias for EKS integration. It also demonstrates the workflow for making changes, including creating merge requests, utilizing Review Apps, and deploying updates to production.
Sep 2018Auto DevOps will be enabled by default as part of GitLab’s 11.3 releaseThis post announces the default enablement of Auto DevOps in GitLab 11.3, building upon its general availability in 11.0. It details the product principle of 'default to on' for valuable features and outlines the fallback mechanism to disable Auto DevOps if a pipeline fails, with notifications to project owners. The rollout strategy for gitlab.com and self-managed instances is also mentioned.
Aug 2018GitLab Auto DevOps in actionThis post introduces GitLab Auto DevOps as a feature that automates the CI/CD pipeline for building, testing, scanning, packaging, and deploying software. It highlights the benefits of faster delivery, improved quality, and security scanning. The post encourages users to explore documentation and feature pages for more information.
Aug 2017Auto Deploy a GitLab.com project to Google CloudThis post details the practical steps and considerations for using GitLab Auto Deploy to deploy a project to Google Kubernetes Engine (GKE). It explains what Auto Deploy is, why GKE was chosen, and the sequence of actions required: creating a GitLab project with a Dockerfile, creating a GKE cluster, copying credentials to GitLab, and applying the Auto Deploy template to `.gitlab-ci.yml`. It also provides a link to a quick start guide for new Kubernetes users.