---
name: ContinuousDelivery-cicd_setting_values
title: Setting consistent parameter values
description: You can set consistent parameter values by using other continuous integration and continuous delivery (CI/CD) tools to integrate with IBM Cloud® DevOps Insights. To publish build records, test records, deployment records, and to evaluate gate policies within the same pipeline, you must use the same app name and build number for each stage. You need to pass parameter values `logicalappname` and `buildnumber`, and export your toolchain ID to use consistently with DevOps Insights. To use consistent identifiers, set your properties as environment properties.
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.

# Setting consistent parameter values
{: #setting-values-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 set consistent parameter values by using other continuous integration and continuous delivery (CI/CD) tools to integrate with IBM Cloud® DevOps Insights. To publish build records, test records, deployment records, and to evaluate gate policies within the same pipeline, you must use the same app name and build number for each stage. You need to pass parameter values `logicalappname` and `buildnumber`, and export your toolchain ID to use consistently with DevOps Insights. To use consistent identifiers, set your properties as environment properties.
{: shortdesc}

DevOps Insights tracks deployment risk based on published test data. When you integrate DevOps Insights with your continuous integration and continuous delivery (CI/CD) tool, you're instrumenting DevOps Insights to gather information to provide you with important data for visibility of quality.


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

Configure your CI/CD tool to build, test, and deploy. You must complete this step before you continue with the integration.

You need an API key for access to the toolchain, and to log in by using the `ibmcloud` commandline interface (CLI). For more information about creating and managing API keys, see [Managing user API keys](https://cloud.ibm.com/docs/iam?topic=iam-userapikey&interface=ui&format=markdown).


## Exporting your toolchain ID
{: #export-id-cicd}

To set the toolchain ID as an environment variable, first identify and save the toolchain ID for the DevOps Insights instance you would like to aggregate the data. For more information about how to find your toolchain ID, see [Identifying your toolchain ID](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-aggregating-multiple-sources&format=markdown#identifying-toolchain-ID). 

Use the following steps to go to the Continuous Delivery pipeline in your toolchain and set the toolchain ID as an environment variable:

1. From the IBM Cloud console, click the **Menu** icon ![hamburger icon](images/icon_hamburger.svg) > **Platform Automation** > **Toolchains**.
2. Select a location to view your toolchains that contain instances of DevOps Insights. 
3. Select your toolchain. 
4. From your toolchain's Overview page, on the **Delivery pipelines** card, click **Delivery Pipeline**.
5. Click the **Settings** icon ![gear icon](images/settings.svg) > **Configure Stage**.
6. Click the **Jobs** tab. 
7. Make your changes in the script section. For each stage where you use commands to send build, test, and deployment records, set `TOOLCHAIN_ID` as the environment variable to the toolchain ID. Export the toolchain ID before they call the command. 

```text
export TOOLCHAIN_ID="YOUR_TOOLCHAIN_ID_HERE"
```
{: codeblock}


## Setting environment properties
{: #setting-parameters-cicd}

Use the `logicalappname` and `buildnumber` parameters consistently for publishing data to DevOps Insights or for evaluating policies. Refer to your CI/CD tool documentation to set `logicalappname` and `buildnumber` across jobs consistently.


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

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