En la parte superior de la página, selecciona la pestaña 1.ª gen..
Haz clic en Conectar repositorio.
Selecciona Bitbucket Server.
Verá el panel Conectar repositorio. Sigue estos pasos para conectar tu repositorio de Bitbucket Server:
Región: selecciona la región en la que se encuentra tu conexión.
En Seleccionar proveedor de gestión de código fuente, selecciona Bitbucket Server.
Conexión de host: selecciona el nombre de tu conexión de host en el menú desplegable.
Haz clic en Continuar.
En Select Repository (Seleccionar repositorio), elige los repositorios de Bitbucket Server que quieras conectar a Cloud Build.
Una vez que haya seleccionado su cuenta y sus repositorios de Bitbucket Server, lea la renuncia de consentimiento y marque la casilla situada junto a ella para indicar que acepta los términos presentados.
Haz clic en Conectar para conectar tus repositorios.
Cuando se conecta un repositorio, Cloud Build configura un webhook en el repositorio de tu instancia de Bitbucket Server. El repositorio envía webhooks para invocar los activadores de Bitbucket Server correspondientes cuando haces cambios en el repositorio. Un repositorio también se puede conectar varias veces con varias conexiones de host.
Para saber cómo gestionar webhooks, consulta Gestionar webhooks.
Para localizar el webhook, necesitas su ID. El ID de webhook de cada repositorio conectado se puede encontrar en BitbucketServerConfig.
Introduce el siguiente comando para obtener el ID del webhook:
PROJECT_NUMBER es el número de tu proyecto de Cloud.
REGION es la región asociada a tu configuración de Bitbucket Server.
BITBUCKET_SERVER_CONFIG_NAME es el nombre de tu configuración de Bitbucket Server.
PROJECT_KEY es la clave de tu proyecto de Bitbucket Server.
Si quieres conectar un repositorio personal, la clave de tu proyecto debe incluir el símbolo de tilde (~) antes de tu nombre de usuario. Por ejemplo, ~${USERNAME}. La URL completa de un repositorio de host puede tener este aspecto: https://${HOST_URI}/projects/~${USER_NAME}/repos/${REPO_SLUG}.
REPO_SLUG es el slug de tu repositorio de Bitbucket Server.
Introduce el siguiente comando curl en tu terminal:
PROJECT_NUMBER es el número de tu proyecto de Cloud.
PROJECT_ID es el ID de tu proyecto de Cloud.
REGION es la región asociada a tu configuración de Bitbucket Server.
OPERATION_ID es el ID de la operación de creación de la configuración de Bitbucket Server.
Puedes encontrar el ID de operación en el campo name de tu respuesta. El formato del campo name de tu respuesta es el siguiente: projects/project-id/locations/region/operations/operation-id.
Es posible que tengas que seguir ejecutando el comando de la API GetOperation hasta que la respuesta contenga done: true, lo que indica que la operación se ha completado. Si el repositorio de Bitbucket Server se conecta correctamente, puedes verlo en el campo response.bitbucketServerConnectedRepositories. De lo contrario, consulta el campo error para ver un informe de errores detallado.
[[["Es fácil de entender","easyToUnderstand","thumb-up"],["Me ofreció una solución al problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Es difícil de entender","hardToUnderstand","thumb-down"],["La información o el código de muestra no son correctos","incorrectInformationOrSampleCode","thumb-down"],["Me faltan las muestras o la información que necesito","missingTheInformationSamplesINeed","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 2025-08-21 (UTC)."],[[["\u003cp\u003eThis page details the process of connecting a Bitbucket Server repository to Cloud Build, allowing for automated builds upon code changes.\u003c/p\u003e\n"],["\u003cp\u003eBefore connecting, users must enable the Cloud Build, Secret Manager, and Compute Engine APIs, and also connect a Bitbucket Server host.\u003c/p\u003e\n"],["\u003cp\u003eConnecting a repository can be done through the Google Cloud console, where users must select their region, source code management provider, host connection, and specific repositories.\u003c/p\u003e\n"],["\u003cp\u003eAlternatively, users can connect a Bitbucket Server repository using the API, which involves using a JSON template and \u003ccode\u003ecurl\u003c/code\u003e commands to configure and verify the connection.\u003c/p\u003e\n"],["\u003cp\u003eOnce connected, Cloud Build configures a webhook on the repository, allowing it to send webhooks that invoke triggers when changes occur, and users can further manage webhooks to learn about troubleshooting them.\u003c/p\u003e\n"]]],[],null,["# Connect to a Bitbucket Server repository\n\nThis page explains how to connect to a [Bitbucket Server](https://confluence.atlassian.com/bitbucketserver/bitbucket-data-center-and-server-documentation-776639749.html) repository\nto Cloud Build.\n\nBefore you begin\n----------------\n\n-\n\n\n Enable the Cloud Build, Secret Manager, and Compute Engine APIs.\n\n\n [Enable the APIs](https://console.cloud.google.com/flows/enableapi?apiid=cloudbuild.googleapis.com,secretmanager.googleapis.com,compute.googleapis.com&redirect=https://cloud.google.com/build/docs/automating-builds/bitbucket/connect-repo-bitbucket-server)\n\n\u003c!-- --\u003e\n\n- Follow the instructions to [connect a Bitbucket Server host](/build/docs/automating-builds/bitbucket/connect-host-bitbucket-server) before connecting repositories.\n\nConnecting to a Bitbucket Server repository\n-------------------------------------------\n\n### Console\n\nTo connect a Bitbucket Server repository to Cloud Build\nusing the Google Cloud console:\n\n1. Open the **Repositories** page in the Google Cloud console.\n\n [Open the Repositories page](https://console.cloud.google.com/cloud-build/repositories)\n2. At the top of the page, select the **1st gen** tab.\n\n3. Click **Connect Repository**.\n\n4. Select **Bitbucket Server**.\n\n You will see the **Connect Repository** panel. Complete the following\n steps to connect your Bitbucket Server repository:\n 1. **Region**: Select a region your connection is in.\n\n 2. Under **Select source code management provider** , select **Bitbucket Server**.\n\n 3. **Host connection**: Select the name of your host connection from the drop-down menu.\n\n 4. Click **Continue**.\n\n 5. Under **Select Repository**, select the Bitbucket Server repositories\n you wish to connect to Cloud Build.\n\n 6. Once you have selected your Bitbucket Server account and repositories,\n read the consent disclaimer and select the checkbox next to it to indicate\n that you accept the presented terms.\n\n 7. Click **Connect** to connect your repositories.\n\n When a repository is connected, Cloud Build\n configures a webhook on the repository\n in your Bitbucket Server instance. The repository\n then sends webhooks to invoke the\n corresponding Bitbucket Server triggers when\n you make changes to your repository. A\n repository can also be connected multiple\n times with multiple host connections.\n To learn how to manage webhooks, see [Manage webhooks](https://confluence.atlassian.com/bitbucketserver/manage-webhooks-938025878.html#Managewebhooks-troubleshootingwebhooks).\n\n To locate the webhook, you need the webhook ID. The webhook ID\n for each connected repository can be found in the `BitbucketServerConfig`.\n\n Enter the following command to retrieve the webhook ID: \n\n gcloud alpha builds enterprise-config bitbucketserver describe \u003cvar translate=\"no\"\u003eCONFIG_NAME\u003c/var\u003e --region=\u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e\n\n Where:\n - \u003cvar translate=\"no\"\u003eCONFIG_NAME\u003c/var\u003e is the name of the Bitbucket Server config\n - \u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e is the region of the Bitbucket Server host connection\n5. Click **Done** . Optionally, click **Create a trigger** to create a trigger.\n\n### API\n\nTo connect your Bitbucket Server repository to Cloud Build\nusing the API, complete the following steps:\n\n1. Use the following JSON template below to connect your repository:\n\n {\n \"parent\": \"projects/\u003cvar translate=\"no\"\u003ePROJECT_NUMBER\u003c/var\u003e/locations/\u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e/bitbucketServerConfigs/\u003cvar translate=\"no\"\u003eBITBUCKET_SERVER_CONFIG_NAME\u003c/var\u003e\",\n \"requests\": {\n \"parent\": \"projects/\u003cvar translate=\"no\"\u003ePROJECT_NUMBER\u003c/var\u003e/locations/\u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e/bitbucketServerConfigs/\u003cvar translate=\"no\"\u003eBITBUCKET_SERVER_CONFIG_NAME\u003c/var\u003e\",\n \"bitbucketServerConnectedRepository\": {\n \"parent\": \"projects/\u003cvar translate=\"no\"\u003ePROJECT_NUMBER\u003c/var\u003e/locations/\u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e/bitbucketServerConfigs/\u003cvar translate=\"no\"\u003eBITBUCKET_SERVER_CONFIG_NAME\u003c/var\u003e\",\n \"repo\": {\n \"projectKey\": \"\u003cvar translate=\"no\"\u003ePROJECT_KEY\u003c/var\u003e\",\n \"repoSlug\": \"\u003cvar translate=\"no\"\u003eREPO_SLUG\u003c/var\u003e\"\n }\n }\n }\n }\n\n Where:\n - \u003cvar translate=\"no\"\u003ePROJECT_NUMBER\u003c/var\u003e is the project number of your Cloud project.\n - \u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e is the [region](/build/docs/locations) associated with your Bitbucket Server configuration.\n - \u003cvar translate=\"no\"\u003eBITBUCKET_SERVER_CONFIG_NAME\u003c/var\u003e is the name of your Bitbucket Server configuration.\n - \u003cvar translate=\"no\"\u003ePROJECT_KEY\u003c/var\u003e is the key of your Bitbucket Server project. If you want to connect a personal repository, your project key should contain the tilde (`~`) symbol before your username. For example, `~${USERNAME}`. The complete URL for a host repository may look like `https://${HOST_URI}/projects/~${USER_NAME}/repos/${REPO_SLUG}`.\n - \u003cvar translate=\"no\"\u003eREPO_SLUG\u003c/var\u003e is the [slug](https://support.atlassian.com/bitbucket-cloud/docs/what-is-a-slug/) of your Bitbucket Server repository.\n2. Enter the following `curl` command in your terminal:\n\n curl -X POST -H \"Authorization: Bearer \"$(gcloud auth print-access-token) -H \"Content-Type: application/json; charset=utf-8\" -H \"x-goog-user-project: \u003cvar translate=\"no\"\u003ePROJECT_NUMBER\u003c/var\u003e\" https://cloudbuild.googleapis.com/v1/projects/\u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003ePROJECT_ID\u003c/span\u003e\u003c/var\u003e/locations/\u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003eREGION\u003c/span\u003e\u003c/var\u003e/bitbucketServerConfigs/\u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003eBITBUCKET_SERVER_CONFIG_NAME\u003c/span\u003e\u003c/var\u003e/connectedRepositories:batchCreate -d @requests.json\n\n Where:\n - \u003cvar translate=\"no\"\u003ePROJECT_NUMBER\u003c/var\u003e is your Cloud project number.\n - \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e is your Cloud project ID.\n - \u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e is the [region](/build/docs/locations) associated with your Bitbucket Server configuration.\n - \u003cvar translate=\"no\"\u003eBITBUCKET_SERVER_CONFIG_NAME\u003c/var\u003e is the name of your Bitbucket Server configuration.\n\n If successful, the response body contains a newly created instance of [Operation](https://cloud.google.com/build/docs/api/reference/rest/v1/operations#Operation).\n3. Enter the following `curl` command in your terminal:\n\n curl -X GET -H \"Authorization: Bearer \"$(gcloud auth print-access-token) -H \"Content-Type: application/json; charset=utf-8\" -H \"x-goog-user-project: \u003cvar translate=\"no\"\u003ePROJECT_NUMBER\u003c/var\u003e\" https://cloudbuild.googleapis.com/v1/projects/\u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-nt\"\u003ePROJECT_ID\u003c/span\u003e\u003c/var\u003e/locations/\u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-nt\"\u003eREGION\u003c/span\u003e\u003c/var\u003e/operations/\u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-nt\"\u003eOPERATION_ID\u003c/span\u003e\u003c/var\u003e\n\n Where:\n - \u003cvar translate=\"no\"\u003ePROJECT_NUMBER\u003c/var\u003e is your Cloud project number.\n - \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e is your Cloud project ID.\n - \u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e is the [region](/build/docs/locations) associated with your Bitbucket Server configuration.\n - \u003cvar translate=\"no\"\u003eOPERATION_ID\u003c/var\u003e is the ID of your Bitbucket Server configuration creation operation. You can find the Operation ID in the `name` field of your response. The format of the `name` field in your response looks like the following: `projects/project-id/locations/region/operations/operation-id`.\n\n You may need to keep running the `GetOperation` API command until the response contains `done: true`, which indicates the operation is completed. If the Bitbucket Server repository is connected successfully, you can see the connected repository in the `response.bitbucketServerConnectedRepositories` field. Otherwise, see the `error` field for a detailed error report.\n\nWhat's next\n-----------\n\n- Learn how to [build repositories from Bitbucket Server](/build/docs/automating-builds/bitbucket/build-repos-from-bitbucket-server).\n- Learn how to [build repositories from Bitbucket Server in a private network](/build/docs/automating-builds/bitbucket/build-repos-from-bitbucket-server-private-network).\n- Learn how to [perform blue/green deployments on Compute Engine](/build/docs/deploying-builds/deploy-compute-engine)."]]