Pipeline Steps

Each named pipeline declares a collection of named step blocks the pipeline will execute.

The basic format of each step declaration is:

Tag	Description
`name`	A friendly name for the step that may be referenced in other steps. Step names must be unique within the same pipeline.
`type`	A predefined string that specifies the type of step. For more information, see Pipelines Steps.
`configuration`	Begins the section of settings required by the step `type`. This may include: Environment variables local to the step Any runtime configuration for the step Any triggering input steps or resources Any resources output by the step Any integrations used by the step All settings required by the step type
`execution`	Specifies the actions to perform for each execution phase of the step.

For example, here is a simple sequence of two steps. Each uses the generic Bash step to output text to the console:

    steps:
    - name: step_1
      type: Bash
      configuration:
        inputResources:
          - name: my_Git_Repository     # Trigger execution on code commit
      execution:
        onExecute:
          - echo "Hello World!"
 
    - name: step_2
      type: Bash
      configuration:
        inputSteps:
          - name: step_1               # Execute this step after the prior step
      execution:
        onExecute:
          - echo "Goodbye World!"