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

Automatics Deployment and 3.0 API Parser Pipeline Job

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.

Why use Jenkins pipeline?

Jenkins is an open continuous integration server which has the ability to support the automation of software development processes. You can create multiple automation jobs with the help of use cases, and run them as a Jenkins pipeline.

Here are the reasons why you use should use Jenkins pipeline:

• Jenkins pipeline is implemented as a code which allows multiple users to edit and execute the pipeline process.
• Pipelines are robust. So if your server undergoes an unforeseen restart, the pipeline will be automatically resumed.
• You can pause the pipeline process and make it wait to resume until there is an input from the user.
• Jenkins Pipelines supports big projects. You can run multiple jobs, and even use pipelines in a loop.

Jenkins pipeline concept

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 : API Scan for Automatics 3.0
    2. Scriptless Automation : API Scan for Automatics 3.0
    3. RDKB Utils : API Scan for Automatics 3.0

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
    }
}