YAML for Jev

Ask Jev, the TypeSafe model, a question about the run and export the answer as pipeline variables.

YAML parameters for Jev

PARAMETERS

integrationrequiredstring

TypeSafe integration identifier for authentication. It refers to an integration in the workspace by its identifier, not by its display name.

questionrequiredstring

The question to answer.

question_typerequiredstring enum

The type of the answer. One of SCORE, CHOICE, BOOLEAN.

Allowed enum:

SCORE,

CHOICE,

BOOLEAN

staterequired(string | object)[]

The context Jev answers about. Each entry is inline text or file: <path> read from the pipeline filesystem or the repository.

typerequiredstring

Value: JEV

actionrequiredstring

Unique identifier for the action within the pipeline.

modelstring

The Jev model to use. Defaults to jev-latest.

criteriaobject

The possible answers, by key. For SCORE the order defines the scale and 2 to 10 entries are allowed, for CHOICE 2 to 255. Used with SCORE and CHOICE.

true_whenstring

When the answer is true. Used with BOOLEAN.

false_whenstring

When the answer is false. Used with BOOLEAN.

trigger_timestring enum

Specifies when the action should be executed.

Allowed enum:

ON_EVERY_EXECUTION,

ON_FAILURE,

ON_BACK_TO_SUCCESS,

ON_WARNING,

ON_WAIT_FOR_APPROVE,

ON_TERMINATE

loopstring[]

The list of variables for dynamic action execution. The action runs once for each value.

run_only_on_first_failureboolean

When true, the action runs only on the first failure instead of on each failure. Used only when trigger_time is ON_FAILURE.

disabledboolean

When set to true the action is disabled. By default it is set to false.

timeoutinteger

The timeout in seconds. It cannot exceed the action time limit of the workspace plan; a higher value is rejected.

ignore_errorsboolean

If set to true the execution will proceed, mark action as a warning and jump to the next action. Doesn't apply to deployment actions.

retry_intervalinteger

Delay time between auto retries in seconds.

retry_countinteger

Number of retries if the action fails.

Constraints: ≤ 10

run_nextstring enum

Defines whether the action should run in parallel with the next one.

Allowed enum:

WAIT_ON_SUCCESS,

IN_SOFT_PARALLEL,

IN_HARD_PARALLEL

trigger_conditionsTriggerConditionYaml[]

The list of trigger conditions to meet so that the action can be triggered.

variablesVariableYaml[]

The list of variables you can use in the action.

Last modified on Nov 2, 2026

Import files Jira Build

YAML examples for Jev

Score the risk of a change with Jev

yaml

- action: "Assess deployment risk"
  type: "JEV"
  trigger_time: "ON_EVERY_EXECUTION"
  integration: "our-typesafe"
  state:
    - "Commit: $BUDDY_RUN_COMMIT_MESSAGE"
    - file: "CHANGELOG.md"
  question: "How risky is this change to deploy?"
  question_type: "SCORE"
  model: "jev-1.13.0"
  criteria:
    none: "Touches only documentation or comments"
    low: "Touches application code covered by tests"
    high: "Touches database migrations or public API contracts"

Classify a change with Jev

yaml

- action: "Classify the change"
  type: "JEV"
  trigger_time: "ON_EVERY_EXECUTION"
  integration: "our-typesafe"
  state:
    - "Commit: $BUDDY_RUN_COMMIT_MESSAGE"
  question: "What kind of change is this?"
  question_type: "CHOICE"
  criteria:
    feature: "Adds behaviour visible to the user"
    bugfix: "Restores behaviour that was already promised"
    other: "Anything that does not fit the options above"

Ask Jev a yes or no question with explicit true and false conditions

yaml

- action: "Check schema impact"
  type: "JEV"
  trigger_time: "ON_EVERY_EXECUTION"
  integration: "our-typesafe"
  state:
    - "Commit: $BUDDY_RUN_COMMIT_MESSAGE"
    - file: "CHANGELOG.md"
  question: "Does this change touch database migrations?"
  question_type: "BOOLEAN"
  true_when: "The changelog mentions a Liquibase changeset or any SQL schema file"
  false_when: "The changelog leaves the schema untouched"

Ask Jev a yes or no question

yaml

- action: "Check the release notes"
  type: "JEV"
  trigger_time: "ON_EVERY_EXECUTION"
  integration: "our-typesafe"
  state:
    - "Commit: $BUDDY_RUN_COMMIT_MESSAGE"
  question: "Do the release notes describe every change in this run?"
  question_type: "BOOLEAN"