Native PulseUno variables provide information related to the chain run, for example, the chain number, the changeset ID/commit hash, or the temporary system credentials to authenticate to a vault. For details, see Built-in variables.

The values for built-in variables are derived automatically from the system.

Built-in variables overwrite any other variables that have the same names.

You define chain variables on a chain. When two or more chain steps need the same value, add a chain variable with the necessary value, and reference the variable in multiple chain steps.

If a global or agent variable with the same name exists, PulseUno uses the value of the chain variable.

For details, see Define chain and global variables.

You add agent variables to an agent. They provide information about the agent, for example, the location of a specific compiler. This way, you can reference the compiler location using the variable instead of a fixed value.

When the chain runs on the agent, the variable is replaced with the value defined for the agent.

If the same variable is defined on the associated chain, PulseUno uses the value of the chain variable.

For details, see Add variables to agents.

Administrators can define global variables. You can use these variables across multiple chains and chain steps.

If the same variable is defined on the associated agent or chain, PulseUno uses the value of the agent or chain variable. Chain variables override agent or global variables that have the same names.

For details, see Define chain and global variables.

The alphanumeric identifier of the changeset checked out in the Fetch Sources step.

Has the same value as pulse.changeset_id.

The name of the stream or branch checked out in the Fetch Sources step.

Dimensions CM streams:PulseUno displays the value in the following format:

PRODUCT:STREAM_NAME

The title of the chain, including the space and product in which the chain runs, for example:

my-space/my-product/my-CI-chain

pulse.chain_num

chainnum

The unique ID of the chain run, for example, 5678901.

Not the same as pulse.chain_num.

The URL of the chain run, for example:

http://pulseuno:8080/pulse/redirect/chainrun/1234567

pulse.changeset_branch_name

stream_name

pulse.changeset_branch_version

stream_version

Dimensions CM streams: The stream version that was delivered.

PulseUno displays the value in the following format:

PRODUCT:STREAM_NAME;VERSION

Git branches: Has the same value as pulse.changeset_id.

pulse.changeset_id

changeset_id

Git only: The head reference for the Git branch associated with the changeset, for example:

/refs/heads/<my-git-branch>

The URL of your PulseUno Git server, for example:

http://pulseuno:8080/git-server/repo

pulse.product

product_name

The name of the product or Git repository in which the chain runs, for example:

my-product

pulse.product_id

pulse.repository_id

The unique ID of the product or Git repository in which the chain runs.

These variables have the same value.

The space and product/Git repository in which the chain runs, for example:

my-space/my-product

pulse.space

suite_name

The URL of your PulseUno server, for example:

http://pulseuno:8080/pulse

PULSE_VAULT_USERNAME

PULSE_VAULT_PASSWORD

Temporary system credentials that represent a one-time username and password to authenticate to a vault when deploying artifacts.

Temporary system credentials are valid only for the duration of the chain run. PulseUno generates the username and password values automatically when a chain is triggered, and invalidates them when the chain finishes.

Note: A chain that uses temporary system credentials must run from a trusted product or Git repository. For details, see Define trusted products for vault.