---
name: ContinuousDelivery-cicd_publish_build
title: Publishing a build record
description: You can publish a build record by using other continuous integration and continuous delivery (CI/CD) tools with the IBM Cloud command line interface (CLI) to integrate with IBM Cloud&reg; DevOps Insights. Build records notify DevOps Insights when a build is complete. This record contains the application name, branch, build ID, reference to Git repo, and other fields. You must publish build records to view any test records, deployment records, or evaluate policies in DevOps Insights.
last-updated: 2026-07-23
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/ContinuousDelivery?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

{:shortdesc: .shortdesc}
{:screen: .screen}
{:codeblock: .codeblock}
{:tip: .tip}
{:note: .note}
{:important: .important}
{:pre: .pre}

# Publishing a build record 
{: #publish-build-cicd}

DevOps Insights will reach end of service and be discontinued on **August 31, 2026**. After this date, the service will no longer be available. New DevOps Insights tool integrations can no longer be created. [Learn more](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-faq_region_feature_consolidation&format=markdown)
{: important}

You can publish a build record by using other continuous integration and continuous delivery (CI/CD) tools with the IBM Cloud command line interface (CLI) to integrate with IBM Cloud&reg; DevOps Insights. Build records notify DevOps Insights when a build is complete. This record contains the application name, branch, build ID, reference to Git repo, and other fields. You must publish build records to view any test records, deployment records, or evaluate policies in DevOps Insights.
{: shortdesc}


## Before you begin
{: #prereq-build-cicd}

Before you publish a build record, you must set consistent parameter values. For more information, see [Setting consistent parameter values by using other CI/CD tools](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-setting-values-cicd&format=markdown).


## Publishing a build record with other CI/CD tools
{: #build-cicd}

In a build job, use the following script to upload a build record. Use the **`buildrecord-publish`** command to upload a build record. 

```bash
#!/bin/bash

#install the latest version of DevOps Insights plugin
ibmcloud plugin install -f doi

# Log in to IBM Cloud if you are not already logged in.  Assumes that $API_KEY environment variable has been set
ibmcloud login --apikey $API_KEY --no-region

# Please set variable $GIT_BRANCH, $GIT_URL and $GIT_COMMIT for better build record data
# Assumes you have set $MY_APP_NAME and $MY_BUILD_NUMBER as described earlier

ibmcloud doi buildrecord-publish --logicalappname="$MY_APP_NAME" --buildnumber="$MY_BUILD_NUMBER" --branch $GIT_BRANCH --repositoryurl $GIT_URL --commitid $GIT_COMMIT --status pass
```
{: codeblock}

The `status` field takes the `pass` or `fail` values.
{: tip}


## Viewing Build Frequency
{: #build-frequency-cicd}

When this build job completes, your CI/CD tool publishes a message to DevOps Insights that a build is complete. You can view the build record on the Build Frequency page. To view the Build Frequency page, use the following steps.

1. From the IBM Cloud console, click the **Menu** icon ![hamburger icon](images/icon_hamburger.svg) > **Platform Automation** > **Toolchains**.
2. Select your toolchain.
3. From your toolchain's Overview page, on the **IBM Cloud tools** card, click **DevOps Insights**.
4. Click **Build Frequency**.  

## Next steps
{: #next-build-cicd} 

[Publish a deployment record](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-publish-deploy-cicd&format=markdown) by using other CI/CD tools.