Jobs

Introduction

A job is a sequence of steps to be executed in the pipeline. It is mandatory to define at least one job in the pipeline. You can define the required jobs for the pipeline as key-value pairs using the jobs key.

Apart from the regular jobs defined in the pipeline, you can configure the following jobs as well :

• Approval Job
• Parallel Job

You can retrieve the status of a job by using << status.{stage_name}.{job_name} >>.

Properties of a Job

YAML Code Snippet for Job

Here’s an example code snippet for jobs that can be defined in a pipeline:

    

        
copy
        

            

        
    
    

         jobs:
  testJob1:
    steps:
      - echo "Enter your scripts here"
  testJob2:
    variables:
      BRANCH: main
    artifacts:
      upload:
        - name: artifactTest
          type: zip
          location: stratus://mybucket/home/artifacts
          files:
            - '**/*'
      download:
        - name: artifactTest
		    type: zip
          location: stratus://mybucket/home/artifacts
   notify:
      on-start:
        - notify-type: email
          notify-variables:
            to: amelia.burrows@zylker.com
      on-end:
        - notify-type: email
          notify-variables:
            to: amelia.burrows@zylker.com
    runner: runner2
    image: testImage1
    cwd: cd ./src
    steps:
      - echo "Enter your scripts here"
    and:
      - equal:
          - << pipeline.event.branch >>
          - main
      - true
  testJob3:
    steps:
      - echo "Hello"

    

The above code illustrates the following workflow:

• There are three jobs defined in the pipeline - testJob1, testJob2, testJob3.
• The testJob2 is configured to be executed only if the current working branch in the repository is the main branch.
• The testJob2 handles the process to store and retrieve the generated build files to and from Catalyst Stratus. This is defined using the upload and download keys.
• It also sends a notification to the defined email address in order to keep them informed about the start of the job execution and the completion of the job as well. This is acheived using the notify on-start and on-end keys.