Cloud Build is now available in theasia-southeast3 region.

For more information, seeCloud Build locations.

Cloud Build now supports OCI artifacts. OCI artifacts for a buildare shown in the following locations:

• The Artifacts column of Build history page
• The Execution details tab of the Build details page
• The Build Artifacts tab of the Build details page

For more information, seeView build results.

In build config files, themavenArtifacts field now supports thedeployFolder field. You can use thedeployFolder field to upload all Mavenfiles in a folder to a specific Artifact Registry repository. For moreinformation, seeUpload all Maven files in a folder to an Artifact Registry repository.

The Service Account User role has been removed from the Cloud Build Permissions page in the Google Cloud Console. Instead, when you enable certain roles on your Cloud Build service account, you can configure your Cloud Build Service account to impersonate the service account of the managed services related to those roles. This configuration lets you deploy builds using managed services while maintaining minimal permissions. For more information, seeConfigure Cloud Build service account impersonation for managed services.

In addition, the Cloud Build Permissions page in the Google Cloud Console will only show thelegacy Cloud Build service account if your organization's policy allows it.

Developer Connect build triggers are nowgenerally available.

You can now create build triggers that build fromrepositories connected to Developer Connect using the Google Cloud Console,gcloud, the Cloud Build API, and Terraform.

Dark theme is now available for Cloud Build. To enable the dark theme, in the Google Cloud console, clickSettings and utilities >Preferences. In the navigation menu, clickAppearance, and then select your color theme and clickSave.

C3 and N2D machine families are now generally available in private pools. For a complete list of supported machines, see themachineType entry in the private pool configuration file schema.

In addition, theCreate private pool andEdit private pool pages now show a monthly estimate based on the pool's machine type configuration. For more information, seeView private pool price estimates.

You can now create build triggers that build fromrepositories connected to Developer Connect.

You can now specify build dependencies in your build configuration file. For more information, seeManage build dependencies.

In the filtering toolbar of the Build history page, you can now filter builds by region. The region drop-down has been removed. For more information, seeView build results.

In the filtering toolbar of the Triggers page, you can now filter by trigger repository and region. The region drop-down has been removed. For more information, seeCreate and manage build triggers.

You can now specify, in your build config file, a custom Pub/Sub topic for build notifications. For more information, seePub/Sub topics for build notifications.

Cloud Build is now available in thenorthamerica-south1 region.

For more information, seeCloud Build locations.

You can now map specific build log fields to log entry fields when the build log is sent to Cloud Logging. For more information, seeMap build log fields to log entry fields.

You can now use Cloud Build to push Go modules to Artifact Registry. For more information, seeBuild and test Go applications.

Cloud Build is now available in the africa-south1 region.

For more information, seeCloud Build locations.

Cloud Build support forcustom organization policies is nowgenerally available.

Custom organization policies let you define constraints for programmatic, fine-grained control over your organization's resources. You can set these policies at the organization, folder, or project level.

To learn more, seeManage Cloud Build resources with custom constraints.

Cloud Build users can connect to Bitbucket Cloud and Bitbucket Data Center hosts and add repositories with theTerraform provider for Google Cloud.

To learn more, seeConnect to a Bitbucket Cloud host andConnect to a Bitbucket Data Center host.

Cloud Build is introducing new organization policy constraints.

The default behavior for how Cloud Build uses service accounts in new projects was changed to improve the security posture of our customers going forward. Organizations can opt out of these changes using neworganization policy boolean constraints.

To learn more about these changes, seeCloud Build Service Account Change.

Cloud Build support forSupply-chain Levels for Software Artifacts (SLSA) version 1.0 compliant provenance is nowgenerally available to help you safeguard your automated build pipelines.

Build provenance is verifiable metadata that you can use to audit builds. Cloud Build can generate provenance aligned with the SLSA v1.0 spec when you use the optionrequestedVerifyOption with triggered builds.

Learn how to usebuild provenance in Cloud Build.

Cloud Build repositories (2nd gen) now supports integration withBitbucket Cloud andBitbucket Data Center. These features aregenerally available.

Cloud Build is now available in the following regions:

• europe-west10
• europe-west12
• me-central1
• me-central2

For more information, seeCloud Build locations.

Cloud Build is introducing a new organization policy constraint.

On April 29, 2024, we are introducing changes to Cloud Build's default behavior and use of service accounts in new projects. Organizations can opt out of these changes using a neworganization policy boolean constraint.

Cloud Build is now available in the following regions:

• europe-southwest1
• europe-west8
• europe-west9
• me-west1
• us-east5
• us-south1

For more information, seeCloud Build locations.

Users can now set an IP range size and starting IP address for private connections in Bitbucket Data Center using thepeeredNetworkIpRange. This feature isgenerally available. To learn more, seeBuild repositories in Bitbucket Data Center in a private network.

Users can now usemanual triggers,webhook triggers, andPub/Sub triggers to build Bitbucket Server and Bitbucket Data Center repositories throughCloud Build repositories (1st gen). This feature isgenerally available. To learn more, seeBuild repositories from Bitbucket Server andBuild repositories from Bitbucket Data Center.

Cloud Build's free tier now offers thee2-standard-2machine type as the new default machine type. The free tier now offers 2,500 build-minutes per month to provide you with more flexibility to use free build-minutes however you want throughout the month instead of being limited to a daily allocation. Changes to the Cloud Build free tier are effective as of September 1, 2023. To learn more, seeCloud Build pricing.

You can now configure Cloud Build to generate Google-signed identity tokens for user-specified service accounts during a build. Leveraging identity tokens with Cloud Build, you can:

• Authorize service-to-service access from Cloud Build
• Sign your builds

Identity tokens that you generate with Cloud Build conform to the OpenID Connect (OIDC) specification.

This feature isgenerally available.

Cloud Build now generates provenance attestations that meetSupply-chain Levels for Software Artifacts (SLSA) v1.0 specifications. Build provenance is a verifiable collection of metadata that you can use to audit builds and safeguard deployments.

This feature is inPreview. Builds triggered by repository events such as pushes or pull requests will generate the v1.0 provenance.

Learn how to usebuild provenance in Cloud Build.

Thee2-medium machine type is now supported as a custom machine type that you can specify in yourcloudbuild.yaml build configuration file. For more information, seemachineType.

Cloud Build repositories (2nd gen) is nowgenerally available. Cloud Build repositories (2nd gen) integrates directly withGitHub,GitHub Enterprise,GitLab, andGitLab Enterprise Edition and comes with end-to-end Terraform support. To learn more, see theRepositories overview page.

Cloud Build now provides the ability to upload npm packages to Artifact Registry automatically and generate Supply-chain Levels for Software Artifacts (SLSA) Level 3 build provenance. This feature isgenerally available. For more information, seeBuild and test Node.js applications.

The Cloud BuildSecurity insights panel that displays security metrics such as Supply-chain Levels for Software Artifacts (SLSA) level for built artifacts, vulnerabilities, and build details is nowgenerally available.

When you enable the Cloud Build API in a project, Cloud Build automatically creates a default service account to execute builds on your behalf. This Cloud Build service account previously had thelogging.privateLogEntries.list IAM permission, which allowed builds to have access to list private logs by default. This permission has now been revoked from the Cloud Build service account to adhere to the security principle of least privilege.

For instructions and more details, see theCloud Build security bulletin.

You can now createmanual triggers,webhook triggers, orPub/Sub triggers using Cloud Build repositories (2nd gen). This feature is available at thepreview release stage. To learn more, see theRepositories overview page.

You can now restrict the creation of Cloud Build builds, triggers, and repositories to a particular location using an Organization Policy Service constraint. This feature isgenerally available. To learn more, seeRestricting Resource Locations.

You can now configure Cloud Build to continue executing a build even if specified steps fail. This feature isgenerally available. To learn more, see the allowFailure and allowExitCodes topics inBuild configuration file schema.

The organization policy for allowed regions when creating new Cloud Build resources is nowgenerally available. Users can apply the policy to control when resource creation is possible given criteria specified in the policy. To learn more, seeRestricting resource locations.

Users can generate Supply chain Levels for Software Artifacts (SLSA) build provenance information for standalone Maven and Python packages when they upload artifacts to Artifact Registry using new fields available in the Cloud Buildconfig file. This feature isgenerally available. For more information, seeBuild and test Java applications andBuild and test Python applications.

You now have the option to use default logs buckets stored within your own project in the same region as your build. You can enable this feature by setting thedefaultLogsBucketBehavior option in your build config file. When you use this option, you gain more control over data residency. Using logs within your own project also allows you to fine-tune access permissions and object lifecycle settings for your build logs. This feature isgenerally available. For more information, see theStore and manage build logs page.

You can now create and manage repository connections using Terraform when using Cloud Build repositories (2nd gen). Cloud Build repositories (2nd gen) is available forGitHub andGitHub Enterprise repositories at thepreview release stage. To learn more, see theRepositories overview page.

Cloud Build repositories (2nd gen) lets you easily create and manage repository connections, not only through Cloud Console but also throughgcloud and the Cloud Build API. Cloud Build repositories (2nd gen) is available forGitHub andGitHub Enterprise repositories at thepreview release stage. To learn more, see theRepositories overview page.

Users can now configure private pools to consume fewer IP addresses within their peered Virtual Private Clouds (VPCs). The newpeeredNetworkIpRange config field enables users to specify a starting IP address and the IP block size that a private pool uses. The IP block size can be as small as /29. This feature isgenerally available.

gcloud commands for creating and managing build triggers are nowgenerally available.

The default build timeout period has been extended. Cloud Build now allows builds to run for up to 60 minutes unless you specify another timeout limit by using thetimeout field.

Users can now customize email, BigQuery, and webhook-based notifications using notifier templates. To learn more, seeConfigure SMTP notifications,Configure BigQuery notifications, andConfigure HTTP notifications.

Users can generate Supply chain Levels for Software Artifacts (SLSA) build provenance information for standalone Java and Python packages when they upload artifacts to Artifact Registry using new fields available in theCloud Build config file. This feature is inpublic preview. For more information, seeBuild and test Java applications andBuild and test Python applications.

You can now configure Cloud Build to continue executing a build even if specified steps fail. This feature is available as apreview release. To learn more, see theallowFailure andallowExitCodes topics inBuild configuration file schema.

Users can now customize Slack notifications for their builds using notifier templates. To learn more, seeConfigure Slack notifications.

Cloud Build now displays build security information for artifacts stored in Artifact Registry in the Google Cloud console. The new Security insights panel is part of Build History in the console. Users can access information such as Supply chain Levels for Software Artifacts (SLSA) level for built artifacts, vulnerabilities and provenance in the panel. To learn more, seeView build security insights. This feature is inpublic preview.

Users can now build repositories from GitLab Enterprise Edition, including instances hosted in a private network. This integration is available at thepreview release stage. To learn more, seeBuilding repositories from GitLab Enterprise Edition.

Users can now use Cloud Build's GitHub Issues notifier to create issues in their GitHub repository in response to build events. To learn more, seeConfiguring GitHub Issue notifications.

Users can now use Cloud Console to configure a trigger to send build logs to GitHub or GitHub Enterprise. For more information, seeBuilding repositories from GitHub andBuilding repositories from GitHub Enterprise.

gcloud support for manual triggers is now available. To learn more, seeManually build code in source repositories.

Cloud Build now supports Supply chain Levels for Software Artifacts (SLSA) level 3 assurance. Taking steps to reach SLSA level 3 can help you protect your build pipeline. To learn more, seeViewing build provenance.

The Cloud Build script field is nowgenerally available. This allows users to specify build steps using their scripting language of choice rather than as arguments to Docker. To learn more, seeRunning bash scripts.

Cloud Build is now available in the following regions:

• asia-south2
• australia-southeast2
• northamerica-northeast2
• southamerica-west1

For more information, seeCloud Build locations.

Thegcr.io/cloud-builders/docker builder has been upgraded to Docker client version 20.10.14. For instructions on using this builder with the Docker client versions, seeInteracting with Docker Hub images.

Regional support for default pools and build triggers is nowgenerally available. To learn more, seeCloud Build locations.

Users can now receive build status notifications in Google Chat via a Google Chat notifier. To learn more, seeConfiguring Google Chat notifications.

Users can view build logs directly in GitHub or GitHub Enterprise without logging into Cloud Build. For more information, seeBuilding repositories from GitHub andBuilding repositories from GitHub Enterprise. This feature isgenerally available.

You can now use Cloud Build attestors to secure your image deployments. To learn how to set up gated deployments, seeSecuring image deployments to Cloud Run and Google Kubernetes Engine. To learn how to view build integrity records, seeViewing build provenance. This feature isgenerally available.

Cloud Build now supports ascript field, which allows users to specify shell scripts to execute in a build step. This feature is available as apreview release. To learn more, seeUsing the script field.

Cloud Build default pools now support regional builds at thepreview release stage. To learn more, seeCloud Build locations.

Cloud Build now supports regional build triggers at thepreview release stage. To learn more, seeCloud Build locations.

The operating system of the machine that Cloud Build uses to run builds has been upgraded to Debian 11. This results in faster build start up time when you run builds on:

• e2-highcpu-8 ore2-highcpu-32 in the default pool.
• Any of theavailable machine types in a private pool.

The organization policy for integrations with services such as GitHub is nowgenerally available. Users can now apply the policy to control triggered builds from external services, such as GitHub. To learn more, seeLimiting builds triggered from external services.

VPC Service Controls support for Cloud Build is nowgenerally available. For instructions on using this feature, seeUsing VPC Service Controls.

Support for configuring triggers to use a particular service account is nowgenerally available. To learn more, seeConfiguring user-specified service accounts.

Cloud Build's Bitbucket Server and Bitbucket Data Center integration is nowgenerally available. Users can build repositories from Bitbucket Server and Bitbucket Data Center, including on-premises instances. For more information, seeBuilding repositories from Bitbucket Server andBuilding repositories from Bitbucket Data Center.

Build integrity features inpreview let you secure deployments by requiring that images are built by Cloud Build. To set up your build verification policy, seeUsing binary authorization to control image deployment. To learn how to view build integrity records, seeViewing build provenance.

Build triggers support forbuildpacks is nowgenerally available. To learn more, seeCreating and managing build triggers.

VPC Service Controls support for build triggers is now available in thepreview release stage. This feature enables users to use build triggers in projects in the VPC Service Controls perimeter. For instructions, seeUsing VPC Service Controls.

Cloud Build approvals are nowgenerally available, allowing users to configure triggers that only execute a build when granted approval by a set of users. To learn how to create a trigger gated by approval, seeCreating and managing triggers. To learn how to approve a build, seeApproving builds.

GitHub Enterprise triggers are nowgenerally available. Users can build repositories from GitHub Enterprise, including on-premises instances. For more information, seeCreating GitHub Enterprise triggers.

Users can now configure triggers to use a particular service account, available at thepreview release stage. To learn more, seeConfiguring user-specified service accounts.

Cloud Build private pools are nowgenerally available. Private pools offerregionalization and greater customization over the build environment, including the ability to access resources in a private network withsupport for VPC Service Controls. For more information, seePrivate pools overview.

Upgraded to Docker server version 20.10.6.

Webhook triggers are now generally available. Learn more about using webhook triggers to build repos hosted onGitlab,Bitbucket Cloud, andBitbucket Server.

Manual triggers are nowgenerally available, allowing users to run triggers on schedule. For more information, seeScheduling builds.

Pub/Sub triggers are nowgenerally available. Users can create triggers to execute builds in response to events published to a Pub/Sub topic. For more information see,Creating Pub/Sub triggers.

Users can now create triggers that execute builds in response to webhook events, including events from external source code management services. This feature is available as apreview release. To learn more, seeCreating webhook triggers andBuilding repositories hosted on Bitbucket Server.

You can nowconfigure Cloud Build to access secrets from Secret Manager via environment variables.

Regionalized builds from Cloud Functions are now visible in the Cloud Build History UI. To learn more, seeViewing build results.

Users can now specify their own service accounts for Cloud Build to run builds. For more information, seeUser-specified service accounts.

Cloud Build Service Level Agreement (SLA) has been published with a Monthly Uptime Percentage of at least 99.95%.

Users can now create manual triggers to run builds at a specified time. To learn more about how to schedule your builds, seeScheduling builds.

Users can now transfer Cloud Build metrics to BigQuery through theBigQuery notifier, a new open-source notifier.

Manual triggers are nowgenerally available. You can create triggers and invoke triggers manually through the Cloud Console. To learn how to create and run manualtriggers, seeCreating manual triggers.

Cloud Build allows you to specify git operations in your build configuration file and run your file using the git repository cloned onto your workspace. The cloned repository cannot exceed 500 MB.

Users can now build containers without a Dockerfile or a Cloud Build config fileusing Cloud Native Buildpacks.

The Cloud Build GitHub App now allows users toview triggers by name onGitHub, including in pull requests. Note that required status checks may need to be updated on GitHub after enabling this feature.

Open-source notifiers forSlack andSMTP are nowgenerally available.These notifiers can be configured to securely alert users about build status.

Bash-style string operations and payload bindings are nowgenerally available. Cloud Build's substitution variables can now refer to other substitution variables, manipulate them using bash-style string operations, and pull information from a trigger event payload. To learn more, seeUsing bash-style string operations and payload bindings in substitutions.

Upgraded to Docker server version 19.03.8.

TheCreate trigger page on the Cloud Console has been updated. To learn more about creating build triggers, seeCreating and managing triggers.

GitHub App triggers is now Generally Available.

TheCloud Build Dashboard, which provides a high-level overview of recent builds for build triggers, is now Generally Available. For information about theDashboard, seeViewing the Dashboard.

TheBuild history page and Build details page in the Google Cloud Platform Console are updated.

Closing pull requests will now cancel running builds in pull requests associated withGitHub App triggers.

GitHub App triggers Beta is now released. Newsubstitution variable values are now available for GitHub pull requests.

Users can now create build triggers to start builds onGitHub pull requests.

GitHub App trigger results are posted to GitHub via the GitHub Checks API.

Added a newCloud Build Settings page in the Google Cloud console for managing service account permissions.

CI/CD developer hub is now available.

Exposed the quota for concurrent builds in the Google Cloud consoleQuotas page.

This also allows projects to lower the number of concurrent builds that can be run at one time, or request a higher limit from the Google Cloud console.

Environment variables can now bedefined globally for all build steps in a build.

Cloud Build now providesCustomer-Managed Encryption Keys (CMEK) compliance.

gke-deploy builder is now available.

Build triggers with inverted regex can now be run in specified branches.

Upgraded to Docker server version 18.09.3.

Repository to project mapping is now available in theGoogle Cloud Build GitHub app.

Upgraded to Docker version 18.09.0.

Upgraded to Docker version 18.06.1.

• Container Builder is now named Cloud Build.
• Added a new top-level menu forCloud Build in the Google Cloud console.
• Thegcloud commands for Cloud Build are updated togcloud builds ....
• Addedsupport for storing non-container artifacts to a Cloud Storage bucket.
• Added support for providingfilepath filters to trigger a build only on changes to the specified files or subdirectories.
• Added a newCloud Build GitHub app.

Upgraded to Docker version 17.12.0.

Cloud Build providestimeout andstatus for build steps.

Added support forgcloudignore.

Community-contributed build steps released.

Cloud Build plugin for Jenkins is now available.

• Lowered per-minute pricing for the default n1-standard-1 machine from $0.0034 to $0.003.
• Addedtwo new machine types with 8 CPU and 32 CPU.
• Added an option to select acustom disk size.

For more information, see thePricing documentation.

Builds are not triggered if the commit message includes[skip ci] or[ci skip].

Upgraded to Docker version 17.06.1.

Builds acceptsecrets and build steps acceptsecretEnv to specify environment variables with values that have been encrypted usingCloud KMS.

SeeEncrypting an Environment Variable Using the CryptoKey.

Build steps acceptvolumes to persist specified paths across build steps.

cloud-build-local, a tool for running builds locally, is available. You can install the tool usinggcloud components install cloud-build-local.

To learn more, seeRunning builds locally.

gradle is now asupported build step.

homevol mounted across build steps as$HOME directory.

kubectl is nowsupported build step.

Expandedbuilder service account permissions to empower end-user and IAM-based control over builder robot permissions, thereby enablinggcloud app deploy,kubectl, and other permissioned APIs to becalled as part of a build.

Upgraded to Docker version 17.05.

General availability of user interface in Google Cloud PlatformConsole, includingbuild history menu.

Beta release ofbuild triggers.

Upgraded to Docker version 1.12.6.

General availability of Cloud Build API.

Supported build steps released.

General availability ofCloud SDK CLI to Cloud Build.

Beta release ofCloud SDK CLI to Cloud Build.

Upgraded to Docker version 1.9.1.

Alpha release ofCloud SDK CLI to Cloud Build.

Beta release of Cloud Build.