GitHub Actions comparison in Jenkins - Mini Project: Build & Apply

GitHub Actions comparison

📖 Scenario: You work in a team that uses Jenkins for automation. Your manager wants to understand how GitHub Actions compares to Jenkins for running automated tasks.

🎯 Goal: You will create a simple Jenkins pipeline script that mimics a basic GitHub Actions workflow. This will help you see the similarities and differences between Jenkins and GitHub Actions.

📋 What You'll Learn

Create a Jenkins pipeline script with a simple job

Add a configuration variable for the branch to build

Use a stage to run a shell command simulating a build

Print the build status at the end

💡 Why This Matters

🌍 Real World

Teams use Jenkins pipelines to automate building, testing, and deploying software. Comparing Jenkins with GitHub Actions helps decide which tool fits best.

💼 Career

Understanding Jenkins pipelines and how they relate to GitHub Actions is valuable for DevOps roles that manage CI/CD workflows.

1

Create a Jenkins pipeline with a simple job

Create a Jenkins pipeline script with a pipeline block and a agent any directive.

Jenkins

pipeline {
    agent any
    // Your code here
}

Need a hint?

Start with the basic Jenkins pipeline syntax: pipeline { agent any }.

2

Add a configuration variable for the branch

Inside the pipeline block, add an environment section with a variable BRANCH_NAME set to main.

Jenkins

pipeline {
    agent any
    environment {
        // Your code here
    }
}

Need a hint?

Use the environment block to define variables like BRANCH_NAME.

3

Add a build stage to run a shell command

Add a stages block with a stage named Build. Inside it, add a steps block that runs the shell command echo Building branch $BRANCH_NAME using sh.

Jenkins

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

Need a hint?

Use sh 'echo Building branch $BRANCH_NAME' inside steps to run the shell command.

4

Print the build status

Add a post block inside the pipeline that prints Build finished successfully using echo when the build success condition is met.

Jenkins

pipeline {
    agent any
    environment {
        BRANCH_NAME = 'main'
    }
    stages {
        stage('Build') {
            steps {
                sh 'echo Building branch $BRANCH_NAME'
            }
        }
    }
    // Your code here
}

Need a hint?

Use the post block with success to run commands after a successful build.