Membangun repositori dari Bitbucket Server di jaringan pribadi
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Cloud Build memungkinkan Anda membuat pemicu untuk membangun dari repositori yang dihosting di Bitbucket Server, sehingga Anda dapat menjalankan build sebagai respons terhadap peristiwa seperti push commit atau permintaan pull yang terkait dengan repositori Bitbucket Server Anda.
Halaman ini menjelaskan cara mengaktifkan fungsi pemicu di instance Bitbucket Server jika instance Anda dihosting di jaringan pribadi.
Sebelum memulai
Enable the Cloud Build, Secret Manager, Compute Engine, and Service Networking APIs.
Jika Anda belum membuat kumpulan pribadi, ikuti petunjuk di
Membuat dan mengelola kumpulan pribadi
untuk membuat kumpulan pribadi. Anda memerlukan kumpulan pribadi untuk
membangun di jaringan pribadi.
Membangun repositori dari Bitbucket Server di jaringan pribadi
Jika instance Bitbucket Server Anda dihosting di jaringan pribadi dan tidak dapat dijangkau melalui koneksi internet publik, Anda harus membuat koneksi pribadi antara jaringan VPC dan jaringan produsen layanan. Anda juga memerlukan kumpulan pribadi untuk membangun di jaringan pribadi.
Untuk membuat pemicu Bitbucket Server untuk membangun di jaringan pribadi:
Buat koneksi pribadi antara jaringan VPC dan jaringan produsen layanan Anda dengan menyelesaikan langkah-langkah berikut:
Alokasikan rentang IP internal di VPC yang dapat digunakan jaringan produsen Cloud Build untuk dialokasikan ke VM yang mempertahankan koneksi dengan repositori pribadi.
Untuk menggunakan jaringan VPC dengan Cloud Build, panjang awalan Anda harus /23 atau lebih rendah, seperti /22 atau /21. Hal ini dilakukan untuk mengakomodasi, setidaknya, pemicu dan kumpulan pekerja Anda, karena setiap koneksi layanan mencoba mengklaim rentang IP dengan panjang awalan /24.
Anda dapat menentukan rentang menggunakan notasi perutean Classless Inter-Domain Routing (CIDR)
dalam format STARTING_IP/SUBNET_PREFIX_SIZE. Misalnya,
192.0.2.0/24 memiliki panjang awalan 24. 24 bit pertama rentang IP digunakan sebagai subnet mask (192.0.2.0), sedangkan kemungkinan alamat host berkisar dari 192.0.2.0 hingga 192.0.2.255.
Buat koneksi pribadi jaringan VPC antara jaringan VPC Anda dan Google Cloud. Untuk mempelajari lebih lanjut, lihat Membuat koneksi pribadi.
Jika telah mengonfigurasi DNS untuk instance Bitbucket Server, Anda harus melakukan peering zona DNS secara manual ke penyedia layanan kami. Untuk mempelajari lebih lanjut, lihat Berbagi zona DNS pribadi dengan produsen layanan.
[OPSIONAL] Jika tidak ingin membuat koneksi pribadi dari project Cloud, Anda dapat menyiapkan VPC Bersama dan membuat project Cloud Anda menggunakan jaringan tersebut jika project Anda adalah bagian dari organisasi. Anda tetap memerlukan VPC Bersama untuk di-peering ke jaringan.
Pemicu Bitbucket Server Anda kini akan otomatis memanggil build di instance Bitbucket Server berdasarkan konfigurasi Anda. Untuk mempelajari cara menjalankan build menggunakan pool pribadi, lihat Menjalankan build di pool pribadi.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-04 UTC."],[[["\u003cp\u003eCloud Build triggers can be set up to initiate builds from Bitbucket Server repositories in response to events like commit pushes or pull requests.\u003c/p\u003e\n"],["\u003cp\u003eFor Bitbucket Server instances within a private network, a private connection between the VPC network and the service producer network is required.\u003c/p\u003e\n"],["\u003cp\u003eBuilding in a private network necessitates the use of a private pool, which needs to be created if not already present.\u003c/p\u003e\n"],["\u003cp\u003eCreating a private connection involves setting up a VPC network, allocating internal and named IP ranges, and establishing the connection between your VPC and Google Cloud.\u003c/p\u003e\n"],["\u003cp\u003eBitbucket Server triggers can be established by connecting a Bitbucket Server host, connecting the repository, and then creating the trigger.\u003c/p\u003e\n"]]],[],null,["# Build repositories from Bitbucket Server in a private network\n\nCloud Build enables you to create triggers to build from\nrepositories hosted on [Bitbucket Server](https://confluence.atlassian.com/bitbucketserver/bitbucket-data-center-and-server-documentation-776639749.html), allowing you to execute builds\nin response to events such as commit pushes or pull requests associated with your Bitbucket Server repository.\n\nThis page explains how you can enable trigger functionality on a\nBitbucket Server instance if your instance is hosted in a private network.\n\nBefore you begin\n----------------\n\n-\n\n\n Enable the Cloud Build, Secret Manager, Compute Engine, and Service Networking APIs.\n\n\n [Enable the APIs](https://console.cloud.google.com/flows/enableapi?apiid=cloudbuild.googleapis.com,secretmanager.googleapis.com,compute.googleapis.com,servicenetworking.googleapis.com&redirect=https://cloud.google.com/build/docs/automating-builds/bitbucket/build-repos-from-bitbucket-server-private-network)\n\n\u003c!-- --\u003e\n\n- If you have not created a private pool, follow the instructions in [Create and manage private pools](/build/docs/private-pools/create-manage-private-pools) to create a private pool. You will need a private pool to build in a private network.\n\nBuilding repositories from Bitbucket Server in a private network\n----------------------------------------------------------------\n\nIf your Bitbucket Server instance is hosted in a private network\nand not reachable over a public internet connection,\nyou must create a private connection between\nyour VPC\nnetwork and the [service producer network](/../vpc/docs/private-services-access#service_producer_network). You\nalso need a [private pool](/build/docs/private-pools/private-pools-overview) to build in a private network.\n\nTo create a Bitbucket Server trigger to build in a private network:\n\n1. Create a private connection between the VPC network\n and your service producer network by completing the following steps:\n\n 1. [Create a new VPC network](/../vpc/docs/create-modify-vpc-networks#create-custom-network) or [select an existing VPC network](https://console.cloud.google.com/networking/networks/list).\n\n | **Note:** You must configure your VPC network to have access to your Bitbucket Server instance in a private network.\n 2. [Allocate a named IP range in the VPC network](/vpc/docs/configure-private-services-access#allocating-range) for your peered network.\n\n 3. [Allocate an internal IP range in the VPC](/vpc/docs/configure-private-services-access#allocating-range) that the Cloud Build\n producer network can use to allocate to VMs maintaining a connection\n with private repositories.\n\n To use the VPC network with Cloud Build, your\n prefix length must be `/23` or lower, such as `/22` or `/21`. This is to\n accommodate, at a minimum, both your triggers and your worker pools,\n because each service connection tries to claim an IP range with a prefix\n length of `/24`.\n\n You can specify the range using the Classless Inter-Domain Routing (CIDR)\n routing notation in the format `STARTING_IP/SUBNET_PREFIX_SIZE`. For example,\n `192.0.2.0/24` has a prefix length of 24. The first 24 bits of the IP range\n are used as the subnet mask (`192.0.2.0`) while the possible hosts addresses\n range from `192.0.2.0` to `192.0.2.255`.\n | **Note:** The value of your prefix length must not exceed `/29`. If no value is specified for the range, a default value of `/24` is automatically assigned. If no value is specified for the prefix length, IP addresses are automatically assigned within the peered VPC network.\n 4. Establish a VPC network private connection between your VPC network and Google Cloud. To learn more, see [Creating a private connection](/../vpc/docs/configure-private-services-access#creating-connection).\n\n 5. If you have DNS configured for your Bitbucket Server instance, you need to manually peer your DNS zone to our service provider. To learn\n more, see the [Sharing private DNS zones with service producers](/../vpc/docs/configure-private-services-access#dns-peering).\n\n 6. \\[OPTIONAL\\] If you do not want to create a private connection from your Cloud project,\n you can set up a [Shared VPC](/../vpc/docs/provisioning-shared-vpc) and have your Cloud project use that network instead if your project is part of an organization. You will still need the Shared VPC to be peered to the network.\n\n2. Use [private pools](/build/docs/private-pools/private-pools-overview)\n to run your builds. If you have not created a private pool,\n see [create a new private pool](/build/docs/private-pools/create-manage-private-pools).\n\n3. [Connect a Bitbucket Server host](/build/docs/automating-builds/bitbucket/connect-host-bitbucket-server).\n\n4. [Connect a Bitbucket Server repository](/build/docs/automating-builds/bitbucket/connect-repo-bitbucket-server).\n\n5. [Create a Bitbucket Server trigger](/build/docs/automating-builds/bitbucket/build-repos-from-bitbucket-server)\n to build repositories hosted on a Bitbucket Server instance.\n\nYour Bitbucket Server trigger will now automatically invoke builds on\nyour Bitbucket Server instance based on your configuration. To learn how to run builds using a private pool, see [Running builds in a private pool](/build/docs/private-pools/run-builds-in-private-pool).\n\nWhat's next\n-----------\n\n- Learn how to [create and manage build triggers](/build/docs/automating-builds/create-manage-triggers).\n- Learn how to [perform blue/green deployments on Compute Engine](/build/docs/deploying-builds/deploy-compute-engine)."]]
