Using Jenkins Pipeline and Groovy to Simplify CI/CD for Multi‑Service Environments

In many microservice scenarios, making even trivial changes such as updating a URL requires editing each service’s Jenkins job, which becomes tedious and hard to track because Jenkins lacks built‑in change logs.

The proposed solution is to use the Jenkins Pipeline plugin and define jobs as Groovy code, allowing the pipeline definitions to be stored in a version‑control system.

By writing pipelines in Groovy and committing a Jenkinsfile, teams can maintain and evolve their CI/CD logic alongside application code; when connected to a multibranch pipeline, Jenkins automatically builds every branch according to the instructions in the Jenkinsfile.

Example Groovy pipeline code:

Coffee-Service, Food-Service: Jenkinsfile

def pipeline
stage('Load pipeline') {
    // Load the pipeline from the shared repository
    fileLoader.withGit(
        'https://url-to-pipeline-repo.git',
        'master',
        ' id-of-in-jenkins-stored-credentials') {
        // Every service is able to use pipeline.groovy
        pipeline = fileLoader.load('pipeline.groovy')
    }
}
pipeline.execute()
Pipeline Repo: pipeline.groovy

def execute() {
    stage('Checkout') {
        checkout scm
    }
    stage('Build service') {
        sh "mvn clean install"
    }
    // The variable env.BRANCH_NAME is automatically set to the current branch.
    // As a consequence of this feature the pipeline can deal with every new branch
    if ("develop".equals(env.BRANCH_NAME) {
        stage('Release') {
            sh "mvn release:prepare release:perform"
        }
    }
}

The article originates from https://www.jambit.com/en/latest-info/toilet-papers/groovy-jenkins-pipeline-baby/.