GitLab CI comparison in Jenkins - Mini Project: Build & Apply

GitLab CI and Jenkins Basic Comparison

📖 Scenario: You are learning about two popular tools used to automate software building and testing: GitLab CI and Jenkins. Both help teams deliver software faster by running tasks automatically when code changes.In this project, you will create a simple Jenkins pipeline script that mimics a basic GitLab CI job. This will help you understand how similar tasks are written in Jenkins compared to GitLab CI.

🎯 Goal: Build a Jenkins pipeline script that defines a simple job to print a message, similar to a GitLab CI job. This will show how Jenkins pipelines are structured and how they compare to GitLab CI jobs.

📋 What You'll Learn

Create a Jenkins pipeline script with a pipeline block

Add an agent to specify where the job runs

Define a stage named Example

Inside the stage, add a steps block with a echo command

Print the message Hello from Jenkins Pipeline!

💡 Why This Matters

🌍 Real World

Teams use Jenkins and GitLab CI to automate building and testing software whenever code changes. This saves time and reduces errors.

💼 Career

Understanding Jenkins pipelines and GitLab CI jobs is important for DevOps roles that manage continuous integration and delivery.

1

Create the Jenkins pipeline block

Write the first line of the Jenkins pipeline script by creating a pipeline block.

Jenkins

pipeline {
    // Your code here
}

Need a hint?

The Jenkins pipeline script always starts with the pipeline keyword followed by curly braces.

2

Add an agent to specify the execution environment

Inside the pipeline block, add an agent any line to tell Jenkins to run the job on any available agent.

Jenkins

pipeline {
    // Add agent any here
}

Need a hint?

The agent any line means Jenkins can run the job on any available machine.

3

Define a stage named Example

Inside the pipeline block, add a stages block. Inside it, create a stage named Example.

Jenkins

pipeline {
    agent any
    // Add stages and stage Example here
}

Need a hint?

Stages group steps in Jenkins pipelines. Each stage has a name in single quotes.

4

Add steps to print a message

Inside the stage('Example') block, add a steps block. Inside it, write echo 'Hello from Jenkins Pipeline!' to print the message.

Jenkins

pipeline {
    agent any
    stages {
        stage('Example') {
            // Add steps and echo here
        }
    }
}

Need a hint?

The steps block contains commands to run. echo prints text to the console.