Contexts are a way to access information inside a workflow run. Data can be access like this inside a job
${{ <contextName>.data }}
Contexts available:
cds: contains all the information about the workflow rungit: contains the git informationvars: contains the project variableset used by the current jobenv: contains environment variablesjobs: contains all parent jobs results and outputsneeds: contains all direct parents ( job.needs ) results and outputsinputs: contains all job inputssteps: contains all previous step statusmatrix: contains the curent value for each matrix variableintegrations: contains data of integration linked to the current jobgate: contains all gate inputsIt contains all cds data related to the workflow execution
event_name: the event name that trigger the workflowevent: the event payload received by CDSproject_key: the project identifier of the workflowrun_id: The identifier of the workflow runrun_number: The current run numberrun_attempt: The current run attemptworkflow: The name of the workflowworkflow_ref: The git refs of the worklow definition used in the current workflow runworkflow_sha: The git commit of the workflow definition used in the current workflow runworkflow_vcs_server: The vcs server name of the workflow definitionworkflow_repository: The name of the workflow definition repositorytriggering_actor: Username that trigger the workflow runjob: The current jobstage: The current stageworkspace: Path of the current workspaceintegrations: a map containing integration data linked to the current job. The key of the map is the integration nameIt contains all git information related to the workflow execution
server: The vcs server name linked to the workflowrepository: The repository linked to the workflowrepositoryUrl: Url of the linked repositoryyref: Current git refssha: Current commitconnection: Type of connection used: https/sshssh_key: SSH Key name usedssh_private: Private SSH Key used for git authenticationusername: Username used to connect to the repositorytoken: User token used for git authenticationsemver_current: Current semantic version computed by CDSsemver_next: Next semantic version computed by CDSIt contains the status and outputs of all recursive parent jobs
jobs.<job_id>.result: status of the given parent job.jobs.<job_id>.outputs: map of all job run result of type variable
jobs.<job_id>.outputs.<run_result_name>It contains the status and outputs of all direct parent jobs
needs.<job_id>.result: status of the given parent job.needs.<job_id>.outputs: map of all job run results of type variable
needs.<job_id>.outputs.<run_result_name>It contains the status and outputs of all previous steps in the current jobs
steps.<step_id>.outcome: result of the given state before ‘continue-on-error’steps.<step_id>.conclusion: result of the given state after ‘continue-on-error’steps.<step_id>.outputs: map of all job run results of type variable by step
steps.<step_id>.outputs.<run_result_name>vars.<varset_name>.<item_name>: value of the given item. If the value is a JSON item, you can select any element like this vars.<varset_name>.<item_name>.<key>.<subkey>