---
title: GCP Cloud Build configuration
slug: gcp-cloud-build-configuration
docTags: 
createdAt: 2026-05-28T13:01:35.307Z
---

GCP Cloud Build is a serverless CI/CD build platform requiring no infrastructure to create. the leading tool for continuously inspecting the Code Quality and Security of codebases and guiding development teams during Code Reviews. For  DevOps Intelligence to pull data from SonarQube, you must configure a SonarQube account.

# Configuring DevOps Intelligence GCP Cloud Build, recent customers

:::hint{type="info"}
The procedures in this section are valid only for customers onboarded 6 June 2024 or after.
:::

Use the following procedure to configure the DevOps Intelligence for Azure Pipelines:

:::hint{type="info"}
Tools must be configured for a specific application in a specific DevOps Intelligence phase. In step 2 of the following procedure, you are choosing the application and  DevOps Intelligence phase to associate with GCP Cloud Build as part of the configuration procedure.
:::

1. Click** Settings & Utilities** → **Application Configuration**. You will see a list of existing applications.
2. Select the existing application for which you want to configure GCP Cloud Build or create a new application.
3. Click the overflow menu (vertical ellipsis) on the Build row for the selected application.
4. Select **Add New Tool Configuration** from the overflow menu. The service displays the **Add Tool Configuration** form.
5. Select **Build** for **Build Categories**. The service displays the **Tool Engine** field.
6. Select Azure Pipelines for **Tool Engine**. The service displays the **Status** field.
7. Enter the current statuses of the builds of the GCPCloud Build (Passed, Failed and In Progress and multiselect).
8. Click **Submit**.

# Onboarding GCP Cloud Build

After configuring Azure Pipeline, you must onboard the technical service. Use the following procedure:

1. Click the overflow menu for the selected application.
2. Select **Onboard Technical Service**. The service displays the Onboard Technical Service form.
3. Select **Build** for **DevOps Phase**. The service displays the Build Categories field.
4. Select **Build** for **Build Categories**. The service displays the Tool Engine field.
5. Select **GCP Cloud Build** for **Tool Engine**. The service displays the **Select Connection** field.
6. Select the appropriate connection. The service displays the **Select Organization** field.
7. Select the appropriate organization. The service displays the **Project** field.
8. Click **Onboard**. The service navigates to the Application Configuration page.
9. You now have the option of clicking the overflow menu for Develop and selecting **Edit/Delete Tools Configuration** to confirm that Azure Pipelines has been fully configured.

# Deleting Azure Pipelines as a technical service

The administrator may, at will, delete the Azure Pipeline technical service. Use the following procedure:

1. Navigate to  DevOps Intelligence → **Settings & Utilities** → **Application Configuration**.
2. Expand the application to view all associated phases.
3. Click the Overflow menu for **Build**.
4. Click **Delete Technical Service**.
5. Click Azure Pipelines for **Select Tools Configured**. The service displays the **Select Organization** field.
6. Select the appropriate organization. The service displays the **Select Projects** field.
7. Select the appropriate project.
8. Click **Delete**.