Concepts

Jenkins Integration Automation for Jira helps you extends Jenkins Integration for Jira to automate Jira specific parts of the your CI/CD workflow.

Rules

Rules are how you can extend Jenkins Integration for Jira by automatically executing actions based on CI/CD events. Each rule is build out of three components, namely events, conditions and actions. Events determine when the rule is executed, conditions can be used to narrow the scope of the actions, and action define what the rule should do when an event is processed and conditions are met.

For example: When a build is synchronized (Event) and its result is worse than success (Condition) then create an issue (Action).

Events

The starting point of any rule is the event it is interested in. Selecting the event type will bind the rule to be executed when such an event is received.

Conditions

Conditions allow you to narrow the scope of the actions, e.g. only execute the actions if a specific job was build. Using conditions is not required but can be useful to limit the scope of the actions.

Actions

Actions define what is done if the conditions of the rule are met, e.g. create an issue if the build result is worse than success.

Expression Values

Expression values allow you to access data within the event that triggered the rule and use them in rule actions.

Logs

Every execution of a rule is traceable via its Rule Log. This log contains details on the event that triggered the rule execute, outcome of any conditions and actions.