Day26:Jenkins Declarative Pipeline

Day26:Jenkins Declarative Pipeline

One of the most important parts of your DevOps and CICD journey is a Declarative Pipeline Syntax of Jenkins

Some terms for your Knowledge

What is Pipeline: A pipeline is a collection of steps or jobs interlinked in a sequence.

Declarative: Declarative is a more recent and advanced implementation of a pipeline as a code.

Scripted: Scripted was the first and most traditional implementation of the pipeline as a code in Jenkins. It was designed as a general-purpose DSL (Domain Specific Language) built with Groovy.

Why you should have a Pipeline

The definition of a Jenkins Pipeline is written into a text file (called a Jenkinsfile) which in turn can be committed to a project’s source control repository.

This is the foundation of "Pipeline-as-code"; treating the CD pipeline as a part of the application to be versioned and reviewed like any other code.

Creating a Jenkinsfile and committing it to source control provides a number of immediate benefits:

  • Automatically creates a Pipeline build process for all branches and pull requests.

  • Code review/iteration on the Pipeline (along with the remaining source code).

Pipeline syntax

pipeline {
    agent any 
    stages {
        stage('Build') { 
            steps {
                // 
            }
        }
        stage('Test') { 
            steps {
                // 
            }
        }
        stage('Deploy') { 
            steps {
                // 
            }
        }
    }
}

Task-01

1. Create a New Job, this time select Pipeline instead of Freestyle Project.

1)To create a Declarative pipeline in Jenkins, go to Jenkins UI and click on New item.

2)Enter the pipeline name and select Pipeline, and then click on ok

3)Go to project configuration page

4)In the “Pipeline” section, In definition select Pipeline script

5)Write a pipeline script

Pipeline: is Declarative Pipeline-specific syntax that defines a "block" containing all content and instructions for executing the entire Pipeline.

Agent: Agent signifies where the Jenkins build job should run. In this case, we have selected agent as any.

Stages: stages block consists of different executable stage blocks. At least one stage block is mandatory inside the stages block. Here we have names stage as “Hello”

Steps: Steps blocks consist of the actual operation which needs to be performed inside Jenkins. In the above example, we are printing “Hello World“.

6)Build the project. You can manually build the project by clicking on the "Build Now" link in the project's main page

7)After a build is completed, you can view the console output by clicking on the "Console Output" link in the build page.

As you can see from the above output, the Pipeline run successfully and printed Hello World.

8)You can see the each stage view by clicking on the "Full Stage View" in the project main page.

Thank you for reading!! I hope you find this article helpful!!

Happy Learning!!

Sayali✨

Did you find this article valuable?

Support Sayali Jadhav by becoming a sponsor. Any amount is appreciated!