Introduction

Jenkins is used by Automatics for following activities. 

• To perform test execution.
• To deploy Automatics Core to maven artifact repository.

Jenkins Setup

Automatics jenkins setup documentation can be found in the page : Automatics Jenkins Setup

For automating the deployment and parser jobs for Automatics, a new Pipeline job is introduced. What this pipeline job will do is it will invoke the existing jenkins freestyle jobs which does the deployment and API scanning in the correct order. The overview of jenkins pipeline job as well as the steps to create the Automatics pipeline job below.

Automatics 3.0 Deployment and Parser Job creation

URL:<<Jenkins url>>

Go to the Dashboard of after logging in to Jenkins UI.

• Click on New Item in the Jenkins dashboard.

• Click on the New Item and Create a job name.

• Select Pipeline option from the List of options
• Navigate to the Pipeline section of the job setup page. The below is a sample groovy script for creating the pipeline job. What the below script does is invoke the existing jobs in sequential order. It should invoke the job deploy Automatics Core, RDB/RDKV Utils, and the jobs needs for Automatics 3.0 which are API Scan job for Automatics Core, Scriptless Automation, RDKB/ RDKV Utils projects. The documentation for creating these individual jobs can be found here 
  API Scan Jobs
  • 1. Automatics Core : Utility Parser Job
    2. Scriptless Automation : Utility Parser Job
    3. RDKB Utils : Utility Parser Job
    4. RDKV Utils : Utility Parser Job

node {
   
    stage('Deployment DEPLOY_AUTOMATICS_CORE') {
       echo "Calling CI-Automatics-Core Job"
       build job: 'CI-Automatics-Core', wait: true, propagate: true
    }
    
    stage('Deployment RDKM_DEPLOY_RDKB_TEST_UTILS') {
       echo "Calling CI-RDKB-Utils Job"
       build job: 'CI-RDKB-Utils', wait: true, propagate: true
    }
    
    stage('Deployment RDKM_DEPLOY_RDKV_TEST_UTILS') {
       echo "Calling CI-RDKV-Utils Job"
       build job: 'CI-RDKV-Utils', wait: true, propagate: true
    }
    
     stage('Run utility parser for Automatics Core') {
       echo "Calling RDKM_AUTOMATICS_API_SCAN_FOR_AUTOMATICS_CORE Job"
       build job: 'AUTOMATICS_API_SCAN_FOR_AUTOMATICS_CORE', wait: true, propagate: true
    }
    
    stage('Run utility parser for Scriptless Automation') {
       echo "Calling RDKM_AUTOMATICS_API_SCAN_FOR_SCRIPTLESS_AUTOMATION Job"
       build job: 'AUTOMATICS_API_SCAN_FOR_SCRIPTLESS_AUTOMATION', wait: true, propagate: true
    }
    
      stage('Run utility parser for RDKB Test Utils') {
       echo "Calling RDKM_AUTOMATICS_API_SCAN_FOR_RDKB_UTILS Job"
       build job: 'AUTOMATICS_API_SCAN_FOR_RDKB_UTILS', wait: true, propagate: true
    }
    
    stage('Run utility parser for RDKV Test Utils') {
       echo "Calling RDKM_AUTOMATICS_API_SCAN_FOR_RDKV_UTILS Job"
       build job: 'AUTOMATICS_API_SCAN_FOR_RDKV_UTILS', wait: true, propagate: true
    }
}

The point to keep in mind is the name given in the "build job: '<<NAME_OF_JOB>>'"  should be same as the existing job in the jenkins