Jenkins Declarative Pipeline (06) : Day - 44
Table of contents
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 a 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 several 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
Copy
Copy
pipeline {
agent any
stages {
stage('Build') {
steps {
//
}
}
stage('Test') {
steps {
//
}
}
stage('Deploy') {
steps {
//
}
}
}
}
Task-01: Jenkins "Hello World" Declarative Pipeline
- Create a New Job, this time select Pipeline instead of Freestyle Project.
Click on "New Item" to create a new Jenkins job.
Enter Job Details:
Provide a name for the job (e.g., "Hello-World").
Choose "Pipeline" as the job type.
Add a description of this project
Configure Pipeline: In the pipeline configuration section: Write declarative pipeline code
Save pipeline configurations and run the pipeline job by clicking on "Build Now."
See the console output
"Thank you for reading my blog! Happy Learning!!!๐