Jenkins

Core Concept

Jenkins is a self-contained, open-source automation server written in Java. Its primary purpose is to automate repetitive tasks involved in the software development lifecycle, such as compiling code, running tests, and deploying applications. This automation is central to the practices of Continuous Integration (CI) and Continuous Delivery/Deployment (CD).

Key Features

• Plugins: Jenkins's greatest strength is its massive ecosystem of over 1,800 community-contributed plugins. These plugins allow it to integrate with virtually any tool in the development toolchain, from version control systems (like Git, SVN) to build tools (like Maven, Gradle), testing frameworks, and cloud providers (like AWS, Azure).
• Pipelines: Modern Jenkins usage revolves around the concept of Pipeline as Code, where the entire build/test/deploy pipeline is defined in a text file called a Jenkinsfile. This file is version-controlled along with the application's source code. There are two syntaxes for writing a Jenkinsfile: Declarative Pipeline (simpler, more structured) and Scripted Pipeline (more flexible, based on Groovy).
• Distributed Builds: Jenkins can distribute build and test workloads across multiple machines (called 'agents' or 'nodes'), allowing for parallel execution and scaling to handle many projects. The central Jenkins server is known as the 'controller' (formerly 'master').

Example Jenkinsfile (Declarative Pipeline)

pipeline {
    agent any
    stages {
        stage('Build') {
            steps {
                echo 'Building the application...'
                // Example: sh './gradlew build'
            }
        }
        stage('Test') {
            steps {
                echo 'Running tests...'
                // Example: sh './gradlew test'
            }
        }
        stage('Deploy') {
            steps {
                echo 'Deploying the application...'
                // Example: sh './deploy.sh'
            }
        }
    }
}

Usage

Developers commit code to a shared repository. Jenkins detects the change, automatically checks out the code, builds it, runs automated tests, and if all steps pass, can deploy the application to a staging or production environment. This provides rapid feedback and ensures the codebase is always in a working state.