You can see the latest product updates for all of Google Cloud on the Google Cloud page, browse and filter all release notes in the Google Cloud console, or programmatically access release notes in BigQuery.
To get the latest product updates delivered to you, add the URL of this page to your feed reader, or add the feed URL directly.
September 23, 2024
Cloud Build is now available in the africa-south1 region.
For more information, see Cloud Build locations.
August 19, 2024
Cloud Build support for custom organization policies is now generally 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, see Manage Cloud Build resources with custom constraints.
July 09, 2024
Cloud Build users can connect to Bitbucket Cloud and Bitbucket Data Center hosts and add repositories with the Terraform provider for Google Cloud.
To learn more, see Connect to a Bitbucket Cloud host and Connect to a Bitbucket Data Center host.
July 02, 2024
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 new organization policy boolean constraints.
To learn more about these changes, see Cloud Build Service Account Change.
June 25, 2024
Cloud Build support for Supply-chain Levels for Software Artifacts (SLSA) version 1.0 compliant provenance is now generally 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 option requestedVerifyOption with triggered builds.
Learn how to use build provenance in Cloud Build.
March 07, 2024
Cloud Build repositories (2nd gen) now supports integration with Bitbucket Cloud and Bitbucket Data Center. These features are generally available.
January 22, 2024
Cloud Build is now available in the following regions:
- europe-west10
- europe-west12
- me-central1
- me-central2
For more information, see Cloud Build locations.
January 16, 2024
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 new organization policy boolean constraint.
November 30, 2023
Cloud Build is now available in the following regions:
- europe-southwest1
- europe-west8
- europe-west9
- me-west1
- us-east5
- us-south1
For more information, see Cloud Build locations.
October 11, 2023
Users can now set an IP range size and starting IP address for private connections in Bitbucket Data Center using the peeredNetworkIpRange. This feature is generally available. To learn more, see Build repositories in Bitbucket Data Center in a private network.
September 07, 2023
Users can now use manual triggers, webhook triggers, and Pub/Sub triggers to build Bitbucket Server and Bitbucket Data Center repositories through Cloud Build repositories (1st gen). This feature is generally available. To learn more, see Build repositories from Bitbucket Server and Build repositories from Bitbucket Data Center.
September 01, 2023
Cloud Build's free tier now offers the e2-standard-2 machine 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, see Cloud Build pricing.
August 29, 2023
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:
Identity tokens that you generate with Cloud Build conform to the OpenID Connect (OIDC) specification.
This feature is generally available.
August 18, 2023
Cloud Build now generates provenance attestations that meet Supply-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 in Preview. Builds triggered by repository events such as pushes or pull requests will generate the v1.0 provenance.
Learn how to use build provenance in Cloud Build.
July 21, 2023
The e2-medium machine type is now supported as a custom machine type that you can specify in your cloudbuild.yaml build configuration file. For more information, see machineType.
July 20, 2023
Cloud Build repositories (2nd gen) is now generally available. Cloud Build repositories (2nd gen) integrates directly with GitHub, GitHub Enterprise, GitLab, and GitLab Enterprise Edition and comes with end-to-end Terraform support. To learn more, see the Repositories overview page.
June 23, 2023
The Cloud Build Security insights panel that displays security metrics such as Supply-chain Levels for Software Artifacts (SLSA) level for built artifacts, vulnerabilities, and build details is now generally available.
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 is generally available. For more information, see Build and test Node.js applications.
June 08, 2023
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 the logging.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 the Cloud Build security bulletin.
May 11, 2023
You can now create manual triggers, webhook triggers, or Pub/Sub triggers using Cloud Build repositories (2nd gen). This feature is available at the preview release stage. To learn more, see the Repositories overview page.
May 09, 2023
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 is generally available. To learn more, see Restricting Resource Locations.
April 26, 2023
You can now configure Cloud Build to continue executing a build even if specified steps fail. This feature is generally available. To learn more, see the allowFailure and allowExitCodes topics in Build configuration file schema.
April 20, 2023
The organization policy for allowed regions when creating new Cloud Build resources is now generally available. Users can apply the policy to control when resource creation is possible given criteria specified in the policy. To learn more, see Restricting resource locations.
April 04, 2023
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 Build config file. This feature is generally available. For more information, see Build and test Java applications and Build and test Python applications.
March 20, 2023
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 the defaultLogsBucketBehavior 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 is generally available. For more information, see the Store and manage build logs page.
February 08, 2023
You can now create and manage repository connections using Terraform when using Cloud Build repositories (2nd gen). Cloud Build repositories (2nd gen) is available for GitHub and GitHub Enterprise repositories at the preview release stage. To learn more, see the Repositories overview page.
January 23, 2023
Cloud Build repositories (2nd gen) lets you easily create and manage repository connections, not only through Cloud Console but also through gcloud and the Cloud Build API. Cloud Build repositories (2nd gen) is available for GitHub and GitHub Enterprise repositories at the preview release stage. To learn more, see the Repositories overview page.
January 18, 2023
Users can now configure private pools to consume fewer IP addresses within their peered Virtual Private Clouds (VPCs). The new peeredNetworkIpRange 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 is generally available.
January 17, 2023
gcloud commands for creating and managing build triggers are now generally available.
January 13, 2023
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 the timeout field.
December 27, 2022
Users can now customize email, BigQuery, and webhook-based notifications using notifier templates. To learn more, see Configure SMTP notifications, Configure BigQuery notifications, and Configure HTTP notifications.
November 30, 2022
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 the Cloud Build config file. This feature is in public preview. For more information, see Build and test Java applications and Build and test Python applications.
November 18, 2022
You can now configure Cloud Build to continue executing a build even if specified steps fail. This feature is available as a preview release. To learn more, see the allowFailure and allowExitCodes topics in Build configuration file schema.
November 07, 2022
Users can now customize Slack notifications for their builds using notifier templates. To learn more, see Configure Slack notifications.
October 11, 2022
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, see View build security insights. This feature is in public preview.
October 07, 2022
Users can now build repositories from GitLab Enterprise Edition, including instances hosted in a private network. This integration is available at the preview release stage. To learn more, see Building repositories from GitLab Enterprise Edition.
September 15, 2022
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, see Configuring GitHub Issue notifications.
September 13, 2022
Users can now use Cloud Console to configure a trigger to send build logs to GitHub or GitHub Enterprise. For more information, see Building repositories from GitHub and Building repositories from GitHub Enterprise.
gcloud support for manual triggers is now available. To learn more, see Manually build code in source repositories.
September 12, 2022
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, see Viewing build provenance.
September 09, 2022
The Cloud Build script field is now generally available. This allows users to specify build steps using their scripting language of choice rather than as arguments to Docker. To learn more, see Running bash scripts.
August 17, 2022
Cloud Build is now available in the following regions:
- asia-south2
- australia-southeast2
- northamerica-northeast2
- southamerica-west1
For more information, see Cloud Build locations.
July 12, 2022
The gcr.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, see Interacting with Docker Hub images.
June 27, 2022
Regional support for default pools and build triggers is now generally available. To learn more, see Cloud Build locations.
May 23, 2022
Users can now receive build status notifications in Google Chat via a Google Chat notifier. To learn more, see Configuring Google Chat notifications.
May 17, 2022
Users can view build logs directly in GitHub or GitHub Enterprise without logging into Cloud Build. For more information, see Building repositories from GitHub and Building repositories from GitHub Enterprise. This feature is generally available.
May 10, 2022
You can now use Cloud Build attestors to secure your image deployments. To learn how to set up gated deployments, see Securing image deployments to Cloud Run and Google Kubernetes Engine. To learn how to view build integrity records, see Viewing build provenance. This feature is generally available.
May 05, 2022
Cloud Build now supports a script field, which allows users to specify shell scripts to execute in a build step. This feature is available as a preview release. To learn more, see Using the script field.
April 15, 2022
Cloud Build default pools now support regional builds at the preview release stage. To learn more, see Cloud Build locations.
Cloud Build now supports regional build triggers at the preview release stage. To learn more, see Cloud Build locations.
March 02, 2022
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-8ore2-highcpu-32in the default pool.- Any of the available machine types in a private pool.
February 18, 2022
The organization policy for integrations with services such as GitHub is now generally available. Users can now apply the policy to control triggered builds from external services, such as GitHub. To learn more, see Limiting builds triggered from external services.
VPC Service Controls support for Cloud Build is now generally available. For instructions on using this feature, see Using VPC Service Controls.
February 14, 2022
Support for configuring triggers to use a particular service account is now generally available. To learn more, see Configuring user-specified service accounts.
February 07, 2022
Cloud Build's Bitbucket Server and Bitbucket Data Center integration is now generally available. Users can build repositories from Bitbucket Server and Bitbucket Data Center, including on-premises instances. For more information, see Building repositories from Bitbucket Server and Building repositories from Bitbucket Data Center.
October 12, 2021
Build integrity features in preview let you secure deployments by requiring that images are built by Cloud Build. To set up your build verification policy, see Using binary authorization to control image deployment. To learn how to view build integrity records, see Viewing build provenance.
September 07, 2021
Build triggers support for buildpacks is now generally available. To learn more, see Creating and managing build triggers.
September 01, 2021
VPC Service Controls support for build triggers is now available in the preview release stage. This feature enables users to use build triggers in projects in the VPC Service Controls perimeter. For instructions, see Using VPC Service Controls.
August 18, 2021
Cloud Build approvals are now generally 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, see Creating and managing triggers. To learn how to approve a build, see Approving builds.
August 09, 2021
GitHub Enterprise triggers are now generally available. Users can build repositories from GitHub Enterprise, including on-premises instances. For more information, see Creating GitHub Enterprise triggers.
August 05, 2021
Users can now configure triggers to use a particular service account, available at the preview release stage. To learn more, see Configuring user-specified service accounts.
July 27, 2021
Cloud Build private pools are now generally available. Private pools offer regionalization and greater customization over the build environment, including the ability to access resources in a private network with support for VPC Service Controls. For more information, see Private pools overview.
May 20, 2021
Upgraded to Docker server version 20.10.6.
April 27, 2021
Webhook triggers are now generally available. Learn more about using webhook triggers to build repos hosted on Gitlab, Bitbucket Cloud, and Bitbucket Server.
Manual triggers are now generally available, allowing users to run triggers on schedule. For more information, see Scheduling builds.
March 10, 2021
Pub/Sub triggers are now generally 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.
February 10, 2021
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 a preview release. To learn more, see Creating webhook triggers and Building repositories hosted on Bitbucket Server.
February 03, 2021
You can now configure Cloud Build to access secrets from Secret Manager via environment variables.
January 15, 2021
Regionalized builds from Cloud Functions are now visible in the Cloud Build History UI. To learn more, see Viewing build results.
January 11, 2021
Users can now specify their own service accounts for Cloud Build to run builds. For more information, see User-specified service accounts.
December 15, 2020
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, see Scheduling builds.
November 19, 2020
Users can now transfer Cloud Build metrics to BigQuery through the BigQuery notifier, a new open-source notifier.
November 11, 2020
Manual triggers are now generally available. You can create triggers and invoke triggers manually through the Cloud Console. To learn how to create and run manual triggers, see Creating manual triggers.
November 09, 2020
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.
November 04, 2020
Users can now build containers without a Dockerfile or a Cloud Build config file using Cloud Native Buildpacks.
August 17, 2020
The Cloud Build GitHub App now allows users to view triggers by name on GitHub, including in pull requests. Note that required status checks may need to be updated on GitHub after enabling this feature.
June 30, 2020
Open-source notifiers for Slack and SMTP are now generally available.These notifiers can be configured to securely alert users about build status.
June 22, 2020
Bash-style string operations and payload bindings are now generally 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, see Using bash-style string operations and payload bindings in substitutions.
June 12, 2020
Upgraded to Docker server version 19.03.8.
March 12, 2020
The Create trigger page on the Cloud Console has been updated. To learn more about creating build triggers, see Creating and managing triggers.
February 06, 2020
GitHub App triggers is now Generally Available.
The Cloud Build Dashboard, which provides a high-level overview of recent builds for build triggers, is now Generally Available. For information about the Dashboard, see Viewing the Dashboard.
January 30, 2020
The Build history page and Build details page in the Google Cloud Platform Console are updated.
December 13, 2019
Closing pull requests will now cancel running builds in pull requests associated with GitHub App triggers.
September 26, 2019
GitHub App triggers Beta is now released. New substitution variable values are now available for GitHub pull requests.
Users can now create build triggers to start builds on GitHub pull requests.
GitHub App trigger results are posted to GitHub via the GitHub Checks API.
August 29, 2019
Added a new Cloud Build Settings page in the Google Cloud console for managing service account permissions.
CI/CD developer hub is now available.
July 12, 2019
Exposed the quota for concurrent builds in the Google Cloud console Quotas 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.
June 27, 2019
Environment variables can now be defined globally for all build steps in a build.
June 20, 2019
Cloud Build now provides Customer-Managed Encryption Keys (CMEK) compliance.
June 19, 2019
gke-deploy builder is now available.
May 27, 2019
Build triggers with inverted regex can now be run in specified branches.
May 20, 2019
Upgraded to Docker server version 18.09.3.
February 12, 2019
Repository to project mapping is now available in the Google Cloud Build GitHub app.
January 09, 2019
Upgraded to Docker version 18.09.0.
October 18, 2018
Upgraded to Docker version 18.06.1.
July 24, 2018
- Container Builder is now named Cloud Build.
- Added a new top-level menu for Cloud Build in the Google Cloud console.
- The
gcloudcommands for Cloud Build are updated togcloud builds .... - Added support for storing non-container artifacts to a Cloud Storage bucket.
- Added support for providing filepath filters to trigger a build only on changes to the specified files or subdirectories.
- Added a new Cloud Build GitHub app.
March 06, 2018
Upgraded to Docker version 17.12.0.
February 28, 2018
Cloud Build provides timeout and status for build steps.
January 10, 2018
Added support for gcloudignore.
November 02, 2017
Community-contributed build steps released.
October 28, 2017
Cloud Build plugin for Jenkins is now available.
October 25, 2017
- Lowered per-minute pricing for the default n1-standard-1 machine from $0.0034 to $0.003.
- Added two new machine types with 8 CPU and 32 CPU.
- Added an option to select a custom disk size.
For more information, see the Pricing documentation.
October 10, 2017
Builds are not triggered if the commit message includes [skip ci] or [ci skip].
August 28, 2017
Upgraded to Docker version 17.06.1.
August 23, 2017
Builds accept secrets and build steps accept secretEnv to specify environment variables with values that have been encrypted using Cloud KMS.
August 03, 2017
Build steps accept volumes to persist specified paths across build steps.
July 26, 2017
cloud-build-local, a tool for running builds locally, is available. You can install the tool using gcloud components install cloud-build-local.
To learn more, see Running builds locally.
July 18, 2017
gradle is now a supported build step.
July 10, 2017
homevol mounted across build steps as $HOME directory.
June 15, 2017
kubectl is now supported build step.
June 07, 2017
Expanded builder service account permissions to empower end-user and IAM-based control over builder robot permissions, thereby
enabling gcloud app deploy, kubectl, and other permissioned APIs to be
called as part of a build.
May 27, 2017
Upgraded to Docker version 17.05.
March 06, 2017
General availability of user interface in Google Cloud Platform Console, including build history menu.
Beta release of build triggers.
January 23, 2017
Upgraded to Docker version 1.12.6.
December 15, 2016
General availability of Cloud Build API.
Supported build steps released.
November 23, 2016
General availability of Cloud SDK CLI to Cloud Build.
November 02, 2016
Beta release of Cloud SDK CLI to Cloud Build.
August 22, 2016
Upgraded to Docker version 1.9.1.
July 20, 2016
Alpha release of Cloud SDK CLI to Cloud Build.
January 14, 2016
Beta release of Cloud Build.