Integration test stages in Jenkins - Mini Project: Build & Apply

Integration Test Stages in Jenkins Pipeline

📖 Scenario: You are working on a Jenkins pipeline to automate testing for a software project. The project requires running integration tests in separate stages to ensure the system components work together correctly.

🎯 Goal: Build a Jenkins pipeline script with multiple integration test stages. Each stage will run a specific integration test command. You will create the pipeline structure, add configuration variables, implement the test stages, and finally print the test results.

📋 What You'll Learn

Create a Jenkins pipeline with a pipeline block

Define an environment variable TEST_COMMAND with the value echo Running integration test

Add two stages named Integration Test 1 and Integration Test 2

Each stage should run the TEST_COMMAND using a sh step

Print a message All integration tests completed at the end

💡 Why This Matters

🌍 Real World

Jenkins pipelines automate software testing to catch bugs early and ensure code quality before deployment.

💼 Career

Understanding Jenkins pipelines and test stages is essential for DevOps engineers and automation specialists to maintain reliable CI/CD workflows.

1

Create the Jenkins pipeline skeleton

Write a Jenkins pipeline script starting with a pipeline block and a stages section. Do not add any stages yet.

Jenkins

pipeline {
    // Define stages here
    stages {
        // Your code here
    }
}

Need a hint?

Start with pipeline { and inside it add stages {}.

2

Add environment variable for test command

Inside the pipeline block, add an environment section. Define a variable called TEST_COMMAND with the value echo Running integration test.

Jenkins

pipeline {
    environment {
        // Your code here
    }
    stages {
    }
}

Need a hint?

Use environment { TEST_COMMAND = 'echo Running integration test' } inside pipeline.

3

Add two integration test stages

Inside the stages section, add two stages named Integration Test 1 and Integration Test 2. Each stage should run the shell command stored in TEST_COMMAND using sh.

Jenkins

pipeline {
    environment {
        TEST_COMMAND = 'echo Running integration test'
    }
    stages {
        // Your code here
    }
}

Need a hint?

Use stage('Name') { steps { sh TEST_COMMAND } } for each test stage.

4

Print completion message after tests

Add a final stage named Summary after the test stages. In this stage, use a sh step to print All integration tests completed.

Jenkins

pipeline {
    environment {
        TEST_COMMAND = 'echo Running integration test'
    }
    stages {
        stage('Integration Test 1') {
            steps {
                sh TEST_COMMAND
            }
        }
        stage('Integration Test 2') {
            steps {
                sh TEST_COMMAND
            }
        }
        // Your code here
    }
}

Need a hint?

Add a new stage with stage('Summary') { steps { sh 'echo All integration tests completed' } }.