Browse documentation

Execution context

An execution has a context shared by its action graph.

Files

Actions operate in the execution workspace. A clone action can create source files that a later build action reads. Parallel actions must avoid incompatible writes to the same path.

Values

The context contains configured variables, attached secrets, and outputs exported by completed actions. Variables and secrets share a flat name namespace; outputs are addressed by action reference and output name:

${clone.commit_sha}

This namespace prevents two actions of the same type from overwriting one another.

Logs and diagnostics

Every action reports its state and log output. Exported outputs are included in those execution logs to show what became available to downstream actions.

Exact occurrences of attached secret values are redacted before log persistence. Avoid commands that print credentials or transformed secret values.

Failure propagation

Without continue-on-error, a failed action does not satisfy its outgoing dependencies. With continue-on-error, Codinamo may let the graph proceed and records that the terminal result contains tolerated failures.