Top-level properties - Amazon CodeCatalyst
NameSchemaVersionRunModeComputeTriggersActions

Top-level properties

The following is the reference documentation for the top-level properties in the workflow definition file.

# Name
Name: workflow-name
        
# Schema version
SchemaVersion: 1.0
        
# Run mode
RunMode: QUEUED|SUPERSEDED|PARALLEL

# Compute
Compute:  
...
            
# Triggers
Triggers:
...

# Actions
Actions:
...

Name

(Required)

The name of the workflow. The workflow name is shown in the workflows list and mentioned in notifications and logs. The workflow name and workflow definition file name can match, or you can name them differently. Workflow names do not need to be unique. Workflow names are limited to alphanumeric characters (a-z, A-Z, 0-9), hyphens (-), and underscores (_). Spaces are not allowed. You cannot use quotation marks to enable special characters and spaces in workflow names.

Corresponding UI: visual editor/Workflow properties/Workflow name

SchemaVersion

(Required)

The schema version of the workflow definition. Currently, the only valid value is 1.0.

Corresponding UI: none

RunMode

(Optional)

How CodeCatalyst handles multiple runs. You can use one of the following values:

  • QUEUED – Multiple runs are queued and run one after the other. You can have up to 50 runs in a queue.

  • SUPERSEDED – Multiple runs are queued and run one after the other. A queue can only have one run, so if two runs end up together in the same queue, the later run supersedes (takes over from) the earlier run, and the earlier run is canceled.

  • PARALLEL – Multiple runs occur simultaneously.

If this property is omitted, the default is QUEUED.

For more information, see Configuring queued, superseded, and parallel runs.

Corresponding UI: visual editor/Workflow properties/Advanced/Run mode

Compute

(Optional)

The computing engine used to run your workflow actions. You can specify compute either at the workflow level or at the action level, but not both. When specified at the workflow level, the compute configuration applies to all actions defined in the workflow. At the workflow level, you can also run multiple actions on the same instance. For more information, see Sharing compute across actions.

For more information about compute, see Working with compute and runtime environment Docker images.

Corresponding UI: none

Name: MyWorkflow
SchemaVersion: 1.0
...
Compute:  
  Type: EC2 | Lambda
  Fleet: fleet-name
  SharedInstance: true | false

Type

(Compute/Type)

(Required if Compute is set)

The type of compute engine. You can use one of the following values:

  • EC2 (visual editor) or EC2 (YAML editor)

    Optimized for flexibility during action runs.

  • Lambda (visual editor) or Lambda (YAML editor)

    Optimized action start-up speeds.

For more information about compute types, see About compute types.

Corresponding UI: visual editor/Workflow properties/Advanced/Compute type

Fleet

(Compute/Fleet)

(Optional)

Specify the machine or fleet that will run your workflow or workflow actions. With on-demand fleets, when an action starts, the workflow provisions the resources it needs, and the machines are destroyed when the action finishes. Examples of on-demand fleets: Linux.x86-64.Large, Linux.x86-64.XLarge. For more information about on-demand fleets, see On-demand fleet properties.

With provisioned fleets, you configure a set of dedicated machines to run your workflow actions. These machines remain idle, ready to process actions immediately. For more information about provisioned fleets, see Provisioned fleet properties.

If Fleet is omitted, the default is Linux.x86-64.Large.

For more information about compute fleets, see About compute fleets.

Corresponding UI: visual editor/Workflow properties/Advanced/Compute fleet

SharedInstance

(Compute/SharedInstance)

(Optional)

Specify the compute sharing capability for your actions. With compute sharing, actions in a workflow run on the same instance (runtime environment image). You can use one of the following values:

  • TRUE means that the runtime environment image is shared between workflow actions.

  • FALSE means that a separate runtime environment image is started and used for each action in a workflow, so you can't share resources such as artifacts and variables without extra configuration.

For more information about compute sharing, see Sharing compute across actions.

Corresponding UI: none

Triggers

(Optional)

A sequence of one or more triggers for this workflow. If a trigger is not specified, then you must manually start your workflow.

For more information about triggers, see Working with triggers.

Corresponding UI: visual editor/workflow diagram/Triggers

Name: MyWorkflow
SchemaVersion: 1.0
...
Triggers:
  - Type: PUSH
    Branches:
      - branch-name
    FilesChanged:
      - folder1/file
      - folder2/
 
  - Type: PULLREQUEST
    Events:
      - OPEN
      - CLOSED
      - REVISION
    Branches:
      - branch-name
    FilesChanged:
      - file1.txt
      
  - Type: SCHEDULE
    # Run the workflow at 10:15 am (UTC+0) every Saturday
    Expression: "15 10 ? * 7 *"
    Branches:
      - branch-name

Type

(Triggers/Type)

(Required if Triggers is set)

Specify the type of trigger. You can use one of the following values:

  • Push (visual editor) or PUSH (YAML editor)

    A push trigger starts a workflow run when a change is pushed to your source repository. The workflow run will use the files in the branch that you're pushing to (that is, the destination branch).

  • Pull request (visual editor) or PULLREQUEST (YAML editor)

    A pull request trigger starts a workflow run when a pull request is opened, updated, or closed in your source repository. The workflow run will use the files in the branch that you're pulling from (that is, the source branch).

  • Schedule (visual editor) or SCHEDULE (YAML editor)

    A schedule trigger starts workflow runs on a schedule defined by a cron expression that you specify. A separate workflow run will start for each branch in your source repository using the branch's files. (To limit the branches that the trigger activates on, use the Branches field (visual editor) or Branches property (YAML editor).)

    When configuring a schedule trigger, follow these guidelines:

    • Only use one schedule trigger per workflow.

    • If you've defined multiple workflows in your CodeCatalyst space, we recommend that you schedule no more than 10 of them to start concurrently.

    • Make sure you configure the trigger's cron expression with adequate time between runs. For more information, see Expression.

For examples, see Examples of triggers.

Corresponding UI: visual editor/workflow diagram/Triggers/Trigger type

Events

(Triggers/Events)

(Required if the trigger Type is set to PULLREQUEST)

Specify the type of pull request events that will start a workflow run. The following are the valid values:

  • Pull request is created (visual editor) or OPEN (YAML editor)

    The workflow run is started when a pull request is created.

  • Pull request is closed (visual editor) or CLOSED (YAML editor)

    The workflow run is started when a pull request is closed. The CLOSED event's behavior is tricky, and is best understood through an example. See Example: A trigger with a pull, branches, and a 'CLOSED' event for more information.

  • New revision is made to pull request (visual editor) or REVISION (YAML editor)

    The workflow run is started when a revision to a pull request is created. The first revision is created when the pull request is created. After that, a new revision is created every time someone pushes a new commit to the source branch specified in the pull request. If you include the REVISION event in your pull request trigger, you can omit the OPEN event, since REVISION is a superset of OPEN.

You can specify multiple events in the same pull request trigger.

For examples, see Examples of triggers.

Corresponding UI: visual editor/workflow diagram/Triggers/Events for pull request

Branches

(Triggers/Branches)

(Optional)

Specify the branches in your source repository that the trigger monitors in order to know when to start a workflow run. You can use regex patterns to define your branch names. For example, use main.* to match all branches beginning with main.

The branches to specify are different depending on the trigger type:

  • For a push trigger, specify the branches you're pushing to, that is, the destination branches. One workflow run will start per matched branch, using the files in the matched branch.

    Examples: main.*, mainline

  • For a pull request trigger, specify the branches you're pushing to, that is, the destination branches. One workflow run will start per matched branch, using the workflow definition file and source files in the source branch (not the matched branch).

    Examples: main.*, mainline, v1\-.* (matches branches that start with v1-)

  • For a schedule trigger, specify the branches that contain the files that you want your scheduled run to use. One workflow run will start per matched branch, using the the workflow definition file and source files in the matched branch.

    Examples: main.*, version\-1\.0

Note

If you don't specify branches, the trigger monitors all branches in your source repository, and will start a workflow run using the workflow definition file and source files in:

For more information about branches and triggers, see Trigger considerations when branching.

For more examples, see Examples of triggers.

Corresponding UI: visual editor/workflow diagram/Triggers/Branches

FilesChanged

(Triggers/FilesChanged)

(Optional if the trigger Type is set to PUSH, or PULLREQUEST. Not supported if the trigger Type is set to SCHEDULE.)

Specify the files or folders in your source repository that the trigger monitors in order to know when to start a workflow run. You can use regular expressions to match file names or paths.

For examples, see Examples of triggers.

Corresponding UI: visual editor/workflow diagram/Triggers/Files changed

Expression

(Triggers/Expression)

(Required if the trigger Type is set to SCHEDULE)

Specify the cron expression that describes when you want your scheduled workflow runs to occur.

Cron expressions in CodeCatalyst use the following six-field syntax, where each field is separated by a space:

minutes hours days-of-month month days-of-week year

Examples of cron expressions

Minutes Hours Days of month Month Days of week Year Meaning

0

0

?

*

MON-FRI

*

Runs a workflow at midnight (UTC+0) every Monday through Friday.

0

2

*

*

?

*

Runs a workflow at 2:00 am (UTC+0) every day.

15

22

*

*

?

*

Runs a workflow at 10:15 pm (UTC+0) every day.

0/30

22-2

?

*

SAT-SUN

*

Runs a workflow every 30 minutes Saturday through Sunday between 10:00 pm on the starting day and 2:00 am on the following day (UTC+0).

45

13

L

*

?

2023-2027

Runs a workflow at 1:45 pm (UTC+0) on the last day of the month between the years 2023 and 2027 inclusive.

When specifying cron expressions in CodeCatalyst, make sure you follow these guidelines:

  • Specify a single cron expression per SCHEDULE trigger.

  • Enclose the cron expression in double-quotes (") in the YAML editor.

  • Specify the time in Coordinated Universal Time (UTC). Other time zones are not supported.

  • Configure at least 30 minutes between runs. A faster cadence is not supported.

  • Specify the days-of-month or days-of-week field, but not both. If you specify a value or an asterisk (*) in one of the fields, you must use a question mark (?) in the other. The asterisk means 'all' and the question mark means 'any'.

For more examples of cron expressions and information about wildcards like ?, *, and L, see the Cron expressions reference in the Amazon EventBridge User Guide. Cron expressions in EventBridge and CodeCatalyst work exactly the same way.

For examples of schedule triggers, see Examples of triggers.

Corresponding UI: visual editor/workflow diagram/Triggers/Schedule

Actions

A sequence of one or more actions for this workflow. CodeCatalyst supports several action types, such as build and test actions, which offer different types of functionality. Each action type has:

  • an Identifier property that indicates the action's unique, hard-coded ID. For example, aws/build@v1 identifies the build action.

  • a Configuration section that contains properties that are specific to the action.

For more information about each action type, see its reference documentation, available in the Workflow definition reference.

The following is the YAML reference for actions and action groups in the workflow definition file.

For more information about actions, see Working with actions.

Name: MyWorkflow
SchemaVersion: 1.0
...
Actions:
  action-name:
    Identifier: action-identifier
    Configuration:
    ...
  #Action groups
  action-group-name:
    Actions:
      ...

action-name

(Actions/action-name)

(Required)

Replace action-name with a name you want to give the action. Action names must be unique within the workflow, and must only include alphanumeric characters, hyphens, and underscores. For more information about syntax rules, see YAML syntax guidelines.

For more information about naming practices for actions, including restrictions, see the action-name.

Corresponding UI: visual editor/action-name/Configuration tab/Action name or Action display name

action-group-name

(Actions/action-group-name)

(Optional)

An action group contains one or more actions. Grouping actions into action groups helps you keep your workflow organized, and also allows you to configure dependencies between different groups of actions.

Replace action-group-name with a name you want to give the action group. Action group names must be unique within the workflow, and must only include alphanumeric characters, hyphens, and underscores. For more information about syntax rules, see YAML syntax guidelines.

For more information about action groups, see Grouping actions into action groups.

Corresponding UI: none