Page History

...

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

Jenkins pipeline concept

Table of Contents

• Generic Overview

• what is Jenkins File?
• why use Jenkins pipeline?
• Jenkins pipeline concept
• Automated Deployment from GitHub

What is Jenkins Pipeline?

...

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

In simple words, Jenkins Pipeline is a combination of plugins that supports the integration and implementation of continuous delivery pipelines using Jenkins. A pipeline has an extensible automation server for creating simple or complex delivery pipelines "as code," via pipeline DSL (Domain-specific Language).

What is Jenkins File?

Jenkins pipelines can be defined using a text file called Jenkins File. You can implement pipeline as code using Jenkins File, and this can be defined by using a domain specific language (DSL). With Jenkins File, you can write the steps needed for running a Jenkins pipeline.

The benefits of using Jenkins File are:

• You can create pipelines automatically for all branches and execute pull requests with just one JenkinsFile.
• You can review your code on the pipeline
• You can audit your Jenkins pipeline
• This is the singular source for your pipeline and can be modified by multiple users.

Jenkins File can be defined by either Web UI or with a Jenkins File.

Declarative versus Scripted pipeline syntax:

There are two types of syntax used for defining your Jenkins File.

1. Declarative
2. Scripted

Declarative:

Declarative pipeline syntax offers an easy way to create pipelines. It contains a predefined hierarchy to create Jenkins pipelines. It gives you the ability to control all aspects of a pipeline execution in a simple, straight-forward manner.

Scripted:

Scripted Jenkins pipeline runs on the Jenkins master with the help of a lightweight executor. It uses very few resources to translate the pipeline into atomic commands. Both declarative and scripted syntax are different from each other and are defined totally differently.

Why use Jenkins pipeline?

...

Automatics 3.0 Deployment and Parser Job creation

URL:<<Jenkins url>>

After created a jenkins job user will genereted a github link. 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.

Based on the jobs we need to select the type of projects. Once project created it will be listed in job list 

User can find all the results in stage view of all utils and parser for kind reference. 

Image Removed

Image Removed

Let's now create a pipeline job using the below Groovy script:

• Click on New Item in the Jenkins dashboard.

• Set the “Job Name” as parent Job

• Select the “Job Type” as Pipeline project.

• Add the Groovy script as explained above and save the job.

...

...

• 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') {
           echoecho "Calling RDKM_DEPLOY_AUTOMATICS_CORECI-Automatics-Core Job"
           buildbuild job: 'RDKM_DEPLOY_AUTOMATICS_CORECI-Automatics-Core', wait: true, propagate: true
      }
       
      stage('Deployment RDKM_DEPLOY_RDKB_TEST_UTILS') {
           echoecho "Calling RDKM_DEPLOY_RDKB_TEST_UTILSCI-RDKB-Utils Job"
           buildbuild job: 'RDKM_DEPLOY_RDKB_TEST_UTILSCI-RDKB-Utils', wait: true, propagate: true
      }
       
      stage('Deployment RDKM_DEPLOY_RDKV_TEST_UTILS') {
           echoecho "Calling RDKM_DEPLOY_RDKV_TEST_UTILSCI-RDKV-Utils Job"
           buildbuild job: 'RDKM_DEPLOY_RDKV_TEST_UTILSCI-RDKV-Utils', wait: true, propagate: true
      }
       
        stagestage('Run utility parser for Automatics Core') {
           echoecho "Calling RDKM_AUTOMATICS_API_SCAN_FOR_AUTOMATICS_CORE Job"
           buildbuild job: 'RDKM_AUTOMATICS_API_SCAN_FOR_AUTOMATICS_CORE', wait: true, propagate: true
      }
       
      stage('Run utility parser for Scriptless Automation') {
           echoecho "Calling RDKM_AUTOMATICS_API_SCAN_FOR_SCRIPTLESS_AUTOMATION Job"
           buildbuild job: 'RDKM_AUTOMATICS_API_SCAN_FOR_SCRIPTLESS_AUTOMATION', wait: true, propagate: true
      }
       
         stage('Run utility parser for RDKB Test Utils') {
           echoecho "Calling RDKM_AUTOMATICS_API_SCAN_FOR_RDKB_UTILS Job"
           buildbuild job: 'RDKM_AUTOMATICS_API_SCAN_FOR_RDKB_UTILS', wait: true, propagate: true
      }
       
      stage('Run utility parser for RDKV Test Utils') {
           echoecho "Calling RDKM_AUTOMATICS_API_SCAN_FOR_RDKV_UTILS Job"
           buildbuild job: 'RDKM_AUTOMATICS_API_SCAN_FOR_RDKV_UTILS', wait: true, propagate: true
      }
}

Steps to create a separate job.

Inside the Repository URL mention the gerrit link of the specific project.

Image Removed

In Branch specifier user needs to be mention the correct branch 

Image Removed

Root POM? should be pom.xml

Following command should be entered inside Goals and options field.

Image Removed

clean package -DskipTests exec:java -Dautomatics.properties.file="xxx"

Once user entered all the details successfully. Job creation done successfully.

Dummy job creation

Now, it’s time to give your job something to do. Click on the Build tab on the configure page.

Image Removed

This will take you to the build section. Click on the Add build step menu and select Execute shell.

Image Removed

We’re going to use a one-line shell step for this job.

Image Removed

Enter the single line of shell code and click Save.

Click Build Now. The job will run and complete almost immediately. Next, click the build number to see your results.

Image Removed

Next, click on Console Output, and you’ll see the shell message.

Image Removed

Your job is ready for scheduling!

Add a Schedule to a Jenkins Job

Head back to the job configuration and click the Build Triggers tab.

Image Removed

Now, check the Build periodically box in the Build Triggers section.

Image Removed

This will open the scheduling text area.

Image Removed

Next, let’s set the job to run every five minutes.

Enter H/5 * * * * into the box, click Save, and reopen the configuration. Jenkins will show you when the job will run.

Image Removed

Save the job again and wait a few minutes. Depending on the value Jenkins selects for H, the job will run after a few minutes.

Here is a screenshot of a couple of builds on our system. You can see that the first build corresponds to the time shown above on the configure page.

Image Removed

The timestamps show that you’ve scheduled a job to run every five minutes.

Wait for a bit longer and you will see that it continues to run every five minutes.

...

 }
}