CI/CD tools landscape in Jenkins - Mini Project: Build & Apply

CI/CD Tools Landscape with Jenkins

📖 Scenario: You are working as a DevOps engineer in a small software company. Your team wants to understand the basic setup of a Jenkins pipeline to automate building and testing their code.

🎯 Goal: Build a simple Jenkins pipeline script that defines stages for building and testing code. This will help your team see how Jenkins automates tasks step-by-step.

📋 What You'll Learn

Create a Jenkins pipeline script with a pipeline block

Add an agent to specify where the pipeline runs

Define two stages: Build and Test

In each stage, add a simple echo command to show the stage name

Print the pipeline completion message at the end

💡 Why This Matters

🌍 Real World

Jenkins pipelines automate software building, testing, and deployment, saving time and reducing errors.

💼 Career

Understanding Jenkins pipelines is essential for DevOps roles to implement continuous integration and continuous delivery.

1

Create the basic Jenkins pipeline structure

Write a Jenkins pipeline script starting with a pipeline block and add an agent any line inside it.

Jenkins

pipeline {
    agent any
    // Your code here
}

Need a hint?

The pipeline block is the main container. agent any means the pipeline can run on any available machine.

2

Add the Build stage

Inside the pipeline block, add a stages block. Then add a stage named Build with a steps block that contains echo 'Building the project...'.

Jenkins

pipeline {
    agent any
    stages {
        stage('Build') {
            steps {
                // Your code here
            }
        }
    }
}

Need a hint?

The stages block holds all the steps your pipeline will run. Each stage groups related steps.

3

Add the Test stage

Inside the existing stages block, add another stage named Test with a steps block that contains echo 'Running tests...'.

Jenkins

pipeline {
    agent any
    stages {
        stage('Build') {
            steps {
                echo 'Building the project...'
            }
        }
        // Your code here
    }
}

Need a hint?

Stages run one after another. Add the Test stage after Build to simulate testing.

4

Print pipeline completion message

Add a final stage named Complete inside the stages block with a steps block that contains echo 'Pipeline finished successfully.'. Then run the pipeline to see all messages.

Jenkins

pipeline {
    agent any
    stages {
        stage('Build') {
            steps {
                echo 'Building the project...'
            }
        }
        stage('Test') {
            steps {
                echo 'Running tests...'
            }
        }
        // Your code here
    }
}

Need a hint?

The final stage confirms the pipeline ran all steps. The output shows messages from all stages in order.