Jenkins CI/CD Pipeline Tutorial — Build, Test and Deploy Like a Pro

Every software team eventually hits the same wall: the codebase grows, the team grows, and suddenly merging code feels like defusing a bomb. Someone pushes a change on Friday afternoon, nobody runs the tests manually, and by Monday morning production is on fire. This isn't a people problem — it's a process problem. Continuous Integration and Continuous Delivery (CI/CD) exists specifically to remove the human bottleneck from repetitive, error-prone steps like building artifacts, running test suites, and shipping to servers.

Jenkins is the open-source automation server that has been solving this problem since 2011. It sits between your version control system and your production environment, watching for every code commit and executing a defined pipeline of steps automatically. It has over 1,800 plugins, runs on any major OS, integrates with GitHub, Docker, Kubernetes, AWS, and virtually every tool in the DevOps ecosystem. It's not the newest tool on the block, but it's the most battle-tested — and understanding Jenkins deeply makes every other CI/CD tool (GitLab CI, GitHub Actions, CircleCI) easier to reason about because they all share the same mental model.

By the end of this article you'll understand why Declarative Pipelines beat Freestyle jobs for real teams, how to write a Jenkinsfile that builds a Node.js app, runs tests, builds a Docker image, and deploys to a staging server — and you'll know the three mistakes that silently break pipelines for months before anyone notices.

Declarative Pipelines: The Industry Standard

In the early days of Jenkins, we used 'Freestyle' jobs—clicking buttons in a web UI to configure builds. This was a disaster for version control. Today, we use Pipeline as Code. By defining your build logic in a Jenkinsfile stored alongside your source code, your CI/CD process becomes versionable, testable, and reproducible. A Declarative Pipeline provides a structured, 'human-readable' syntax that handles complex workflows, environment variables, and post-build actions with ease.

pipeline {
    agent any
    
    environment {
        PROJECT_NAME = 'forge-api'
        DOCKER_REGISTRY = 'io.thecodeforge'
    }

    stages {
        stage('Checkout') {
            steps {
                checkout scm
            }
        }

        stage('Build') {
            steps {
                echo 'Compiling Java Source...'
                sh './mvnw clean compile'
            }
        }

        stage('Unit Test') {
            steps {
                echo 'Running JUnit Tests...'
                sh './mvnw test'
            }
            post {
                always {
                    junit '**/target/surefire-reports/*.xml'
                }
            }
        }

        stage('Docker Build & Push') {
            when {
                branch 'main'
            }
            steps {
                script {
                    docker.withRegistry('', 'docker-hub-credentials') {
                        def customImage = docker.build("${DOCKER_REGISTRY}/${PROJECT_NAME}:${env.BUILD_ID}")
                        customImage.push()
                    }
                }
            }
        }
    }

    post {
        failure {
            echo 'Build Failed! Sending alert to Slack...'
        }
        success {
            echo 'Pipeline completed successfully.'
        }
    }
}

Containerizing the Build Environment

One of the biggest 'it works on my machine' headaches is having the wrong version of Java or Node installed on the Jenkins agent. Instead of installing tools globally on your servers, we use Docker Agents. This ensures that every build runs in a clean, isolated container with exactly the dependencies it needs. This approach makes your Jenkins infrastructure significantly easier to maintain and scale.

# io.thecodeforge: Standardized Build Agent
FROM jenkins/agent:latest-jdk17

USER root

# Install Maven and Docker CLI for 'Docker-out-of-Docker' builds
RUN apt-get update && apt-get install -y maven docker.io \
    && apt-get clean \
    && rm -rf /var/lib/apt/lists/*

# Ensure the jenkins user can run docker commands
RUN usermod -aG docker jenkins

USER jenkins

Frequently Asked Questions