# Quickstart: Deploy to Cloud Run from a Git repository
This page shows you how to continuously deploy from a Git repository to Cloud Run
using Cloud Build.
You can continuously deploy from a repository using [Cloud Build](https://docs.cloud.google.com/run/docs/continuous-deployment.md.txt#set-up-with-cloud-build)
or [Developer Connect](https://docs.cloud.google.com/run/docs/continuous-deployment.md.txt#set-up-with-developer-connect).
*** ** * ** ***
To follow step-by-step guidance for this task directly in the
Google Cloud console, click **Guide me**:
[Guide me](https://console.cloud.google.com//?tutorial=run--quickstart-github-repo)
*** ** * ** ***
## Before you begin
1.
Enable the Cloud Build API, if it is not already enabled.
**Roles required to enable APIs**
To enable APIs, you need the `serviceusage.services.enable` permission. If you
created the project, then you likely already have this permission through the
Owner role (`roles/owner`). Otherwise, you can get this permission through the
Service Usage Admin role (`roles/serviceusage.serviceUsageAdmin`).
[Learn how to grant roles](https://docs.cloud.google.com/iam/docs/granting-changing-revoking-access.md.txt).
[Enable the API](https://console.cloud.google.com/apis/enableflow?apiid=cloudbuild.googleapis.com)
2. If you are under a domain restriction organization policy [restricting](https://docs.cloud.google.com/resource-manager/docs/organization-policy/restricting-domains) unauthenticated invocations for your project, you will need to access your deployed service as described under [Testing private services](https://docs.cloud.google.com/run/docs/triggering/https-request.md.txt#testing-private).
3. Review [Cloud Run
pricing](https://cloud.google.com/run/pricing) or estimate costs with the [pricing calculator](https://cloud.google.com/products/calculator).
### Required roles
To get the permissions that
you need to complete this quickstart,
ask your administrator to grant you the
following IAM roles:
- [Cloud Run Source Developer](https://docs.cloud.google.com/iam/docs/roles-permissions/run.md.txt#run.sourceDeveloper) (`roles/run.sourceDeveloper`) on the service
- [Cloud Run Admin](https://docs.cloud.google.com/iam/docs/roles-permissions/run.md.txt#run.admin) (`roles/run.admin`) on the project
- [Service Account User](https://docs.cloud.google.com/iam/docs/roles-permissions/iam.md.txt#iam.serviceAccountUser) (`roles/iam.serviceAccountUser`) on the service identity
- [Logs Viewer](https://docs.cloud.google.com/iam/docs/roles-permissions/logging.md.txt#logging.viewer) (`roles/logging.viewer`) on the project
For more information about granting roles, see [Manage access to projects, folders, and organizations](https://docs.cloud.google.com/iam/docs/granting-changing-revoking-access.md.txt).
You might also be able to get
the required permissions through [custom
roles](https://docs.cloud.google.com/iam/docs/creating-custom-roles) or other [predefined
roles](https://docs.cloud.google.com/iam/docs/roles-overview#predefined).
## Create a repository from template
To create a repository:
1. Go to the template repository:
### Node.js
Go to [github.com/GoogleCloudPlatform/cloud-run-microservice-template-nodejs](https://github.com/GoogleCloudPlatform/cloud-run-microservice-template-nodejs)
### Python
Go to [github.com/GoogleCloudPlatform/cloud-run-microservice-template-python](https://github.com/GoogleCloudPlatform/cloud-run-microservice-template-python)
### Go
Go to [github.com/GoogleCloudPlatform/cloud-run-microservice-template-go](https://github.com/GoogleCloudPlatform/cloud-run-microservice-template-go)
### Java
Go to [github.com/GoogleCloudPlatform/cloud-run-microservice-template-java](https://github.com/GoogleCloudPlatform/cloud-run-microservice-template-java)
2. Click **Use this template**.
3. Select **Create a new repository**.
4. In the form, enter a **repository name**.
5. Click **Create repository**.
## Deploy from the repository
To deploy from the repository:
1. In the Google Cloud console, go to the Cloud Run page:
[Go to Cloud Run](https://console.cloud.google.com/run?enableapi=true)
2. Select **Services** from the menu, and click **Connect repo**.
3. In the form, select **Cloud Build** , and click **Set up with Cloud Build**.
4. In the right panel:
1. Under **Repository** , select the newly created repository. If you haven't
already authenticated, you might be required to do so. Use the
**authenticate** link under the **Repository Provider** field.
2. Check the confirmation agreement about GitHub and Google Cloud interactivity.
3. Click **Next**.
4. Under **Build Type** , select **Google Cloud Buildpacks**.
5. Click **Save**.
5. In the **Create service** form:
1. Confirm the name of the service. It will be automatically populated
with the repository name.
2. In the **Region** pulldown menu, select the
[region](https://docs.cloud.google.com/run/docs/quickstarts/deploy-continuously.md.txt#deploy-from-repo) where you want your service located.
3. Under **Authentication** , select **Allow public access**.
If you don't have permissions (Cloud Run Admin role) to select
this, the service will deploy and require authentication.
4. Click **Create** to deploy the sample repository to
Cloud Run and wait for the deployment to finish.
6. Click the displayed URL link to run the deployed container.
### Cloud Run locations
Cloud Run is regional, which means the infrastructure that
runs your Cloud Run services is located in a specific region and is
managed by Google to be redundantly available across
[all the zones within that region](https://docs.cloud.google.com/docs/geography-and-regions.md.txt).
Meeting your latency, availability, or durability requirements are primary
factors for selecting the region where your Cloud Run services are run.
You can generally select the region nearest to your users but you should consider
the location of the [other Google Cloud
products](https://cloud.google.com/about/locations/#locations) that are used by your Cloud Run service.
Using Google Cloud products together across multiple locations can affect
your service's latency as well as cost.
Cloud Run is available in the following regions:
#### Subject to [Tier 1 pricing](https://cloud.google.com/run/pricing#tables)
- `asia-east1` (Taiwan)
- `asia-northeast1` (Tokyo)
- `asia-northeast2` (Osaka)
- `asia-south1` (Mumbai, India)
- `asia-southeast3 ` (Bangkok)
- `europe-north1` (Finland)  [Low CO~2~](https://cloud.google.com/sustainability/region-carbon#region-picker)
- `europe-north2` (Stockholm)  [Low CO~2~](https://cloud.google.com/sustainability/region-carbon#region-picker)
- `europe-southwest1` (Madrid)  [Low CO~2~](https://cloud.google.com/sustainability/region-carbon#region-picker)
- `europe-west1` (Belgium)  [Low CO~2~](https://cloud.google.com/sustainability/region-carbon#region-picker)
- `europe-west4` (Netherlands)  [Low CO~2~](https://cloud.google.com/sustainability/region-carbon#region-picker)
- `europe-west8` (Milan)  [Low CO~2~](https://cloud.google.com/sustainability/region-carbon#region-picker)
- `europe-west9` (Paris)  [Low CO~2~](https://cloud.google.com/sustainability/region-carbon#region-picker)
- `me-west1` (Tel Aviv)
- `northamerica-south1` (Mexico)
- `us-central1` (Iowa)  [Low CO~2~](https://cloud.google.com/sustainability/region-carbon#region-picker)
- `us-east1` (South Carolina)
- `us-east4` (Northern Virginia)
- `us-east5` (Columbus)
- `us-south1` (Dallas)  [Low CO~2~](https://cloud.google.com/sustainability/region-carbon#region-picker)
- `us-west1` (Oregon)  [Low CO~2~](https://cloud.google.com/sustainability/region-carbon#region-picker)
#### Subject to [Tier 2 pricing](https://cloud.google.com/run/pricing#tables)
- `africa-south1` (Johannesburg)
- `asia-east2` (Hong Kong)
- `asia-northeast3` (Seoul, South Korea)
- `asia-southeast1` (Singapore)
- `asia-southeast2 ` (Jakarta)
- `asia-south2` (Delhi, India)
- `australia-southeast1` (Sydney)
- `australia-southeast2` (Melbourne)
- `europe-central2` (Warsaw, Poland)  [Low CO~2~](https://cloud.google.com/sustainability/region-carbon#region-picker)
- `europe-west10` (Berlin)
- `europe-west12` (Turin)  [Low CO~2~](https://cloud.google.com/sustainability/region-carbon#region-picker)
- `europe-west2` (London, UK)  [Low CO~2~](https://cloud.google.com/sustainability/region-carbon#region-picker)
- `europe-west3` (Frankfurt, Germany)
- `europe-west6` (Zurich, Switzerland)  [Low CO~2~](https://cloud.google.com/sustainability/region-carbon#region-picker)
- `me-central1` (Doha)
- `me-central2` (Dammam)
- `northamerica-northeast1` (Montreal)  [Low CO~2~](https://cloud.google.com/sustainability/region-carbon#region-picker)
- `northamerica-northeast2` (Toronto)  [Low CO~2~](https://cloud.google.com/sustainability/region-carbon#region-picker)
- `southamerica-east1` (Sao Paulo, Brazil)  [Low CO~2~](https://cloud.google.com/sustainability/region-carbon#region-picker)
- `southamerica-west1` (Santiago, Chile)  [Low CO~2~](https://cloud.google.com/sustainability/region-carbon#region-picker)
- `us-west2` (Los Angeles)
- `us-west3` (Salt Lake City)
- `us-west4` (Las Vegas)
If you already created a Cloud Run service, you can view the
region in the Cloud Run dashboard in the
[Google Cloud console](https://console.cloud.google.com/run).
## Update the service
To make changes to the service:
1. Push a commit to the main branch of the repository.
2. Refresh the Cloud Run service to see the status of the update.
> [!TIP]
> **Success:** You deployed a container image from a Git repository to Cloud Run.
Cloud Run automatically scales your container instances based on demand,
and you only pay for the CPU, memory, and networking consumed during request
processing.
## Clean up
To avoid additional charges to your Google Cloud account, delete all the resources
you deployed with this quickstart.
### Delete your repository
Cloud Run doesn't charge you when your deployed service isn't in use.
However, you might still be [charged for storing the container image in
Artifact Registry](https://cloud.google.com/artifact-registry/pricing). To delete Artifact Registry repositories,
follow the steps in [Delete
repositories](https://docs.cloud.google.com/artifact-registry/docs/manage-repos#delete) in the Artifact Registry
documentation.
### Delete your service
Cloud Run services don't incur costs until they receive requests.
To delete your Cloud Run service, follow one of these steps:
### Console
To delete a service:
1. In the Google Cloud console, go to the Cloud Run **Services** page:
[Go to Cloud Run](https://console.cloud.google.com/run/services)
2. Locate the service you want to delete in the services list, and click
its checkbox to select it.
3. Click **Delete**. This deletes all revisions of the service.
### gcloud
To delete a service, run the following command:
```
gcloud run services delete SERVICE --region REGION
```
Replace the following:
- SERVICE: name of your service.
- REGION: Google Cloud region of the service.
### Delete your test project
Deleting your Google Cloud project stops billing for all resources in that
project. To release all Google Cloud resources in your project, follow these steps:
> [!CAUTION]
> **Caution** : Deleting a project has the following effects:
>
> - **Everything in the project is deleted.** If you used an existing project for the tasks in this document, when you delete it, you also delete any other work you've done in the project.
> - **Custom project IDs are lost.** When you created this project, you might have created a custom project ID that you want to use in the future. To preserve the URLs that use the project ID, such as an `appspot.com` URL, delete selected resources inside the project instead of deleting the whole project.
1. In the Google Cloud console, go to the **Manage resources** page.
[Go to Manage resources](https://console.cloud.google.com/iam-admin/projects)
2. In the project list, select the project that you want to delete, and then click **Delete**.
3. In the dialog, type the project ID, and then click **Shut down** to delete the project.
## What's next
- [Quickstart: Build and deploy](https://docs.cloud.google.com/run/docs/quickstarts.md.txt#build-and-deploy-a-web-service)
- [Continuous deployment with Cloud Build](https://docs.cloud.google.com/run/docs/continuous-deployment-with-cloud-build)
- [Building containers using Buildpacks](https://docs.cloud.google.com/run/docs/building/containers.md.txt#buildpacks)