Variables and expressions

Context value expression

${CONTEXT_NAME}

The name may come from the pipeline’s attached variable group or secret group. Names must be unique across both groups. ICE preserves the expression and the runtime resolves it immediately before execution.

Action output expression

${action_reference.output_name}

action_reference is the unique reference configured on the canvas or declared in ICE. output_name must be declared by the action definition.

Codinamo preserves these expressions while editing and saving ICE. They are resolved only when the pipeline runs and the upstream action has exported the value.

Examples:

Expression Value

Expression	Value
`${clone.repository_path}`	Path of the repository created by Git Clone
`${clone.commit_sha}`	Full checked-out commit SHA
`${build.artifact_path}`	Primary Maven or Gradle artifact
`${image.image_name}`	Image produced by Docker Build
`${push.image_digest}`	Digest returned by Docker Push

${clone.repository_path}

Path of the repository created by Git Clone

${clone.commit_sha}

Full checked-out commit SHA

${build.artifact_path}

Primary Maven or Gradle artifact

${image.image_name}

Image produced by Docker Build

${push.image_digest}

Digest returned by Docker Push

Naming constraints

Reference names start with a letter and contain letters, numbers, and underscores. Renaming an action does not silently rewrite arbitrary text in unrelated parameters; update downstream references and resolve validation errors.

Availability

Only outputs from completed upstream actions are available. A parallel sibling cannot consume an output unless the graph introduces a dependency that guarantees ordering.

Pipeline validation reports references whose action does not exist, whose output is not declared by the action type, or whose producer is not upstream from the consumer. These semantic diagnostics do not change the ICE expression.