Deploy to Multiple Environments

In this tutorial, we will create a Jenkins declarative pipeline that builds a Java application using Maven and deploys it to three different Tomcat environments: Dev, QA, and Prod.

Jenkinsfile

Here is the complete Jenkinsfile. You can find the source code in the GitHub repository.

pipeline {
  agent any
  options {
    disableConcurrentBuilds()
    disableResume()
    buildDiscarder(logRotator(numToKeepStr: '10'))
    timeout(time: 1, unit: 'HOURS')
  }
  tools {
    maven 'maven-3.6.3' 
  }
  stages {
    stage ('Build') {
      steps {
        sh 'mvn clean package'
      }
    }
    stage ('Deploy to Dev') {
      steps {
        script {
          deploy adapters: [tomcat9(credentialsId: 'tomcat_credential', path: '', url: 'http://20.197.20.20:8080')], contextPath: '/helloworld', onFailure: false, war: 'webapp/target/*.war' 
        }
      }
    }
    stage ('Deploy to Qa') {
      steps {
        script {
          deploy adapters: [tomcat9(credentialsId: 'tomcat-credential', path: '', url: 'http://20.197.20.30:8080')], contextPath: '/helloworld', onFailure: false, war: 'target/hello-world-*.war'
        }
      }
    }
    stage ('Deploy to Prod') {
      steps {
        script {
          deploy adapters: [tomcat9(credentialsId: 'tomcat-credential', path: '', url: 'http://20.197.20.178:8080')], contextPath: '/helloworld', onFailure: false, war: 'target/hello-world-*.war'
        }
      }
    }
  }
  post {
    always {
      deleteDir()
    }
  }
}

Explanation

Options

The options block contains pipeline-specific configurations:

• disableConcurrentBuilds(): Prevents multiple builds of the same project from running simultaneously.
• disableResume(): Disables the ability to resume a build if the controller restarts.
• buildDiscarder(logRotator(numToKeepStr: '10')): Keeps only the last 10 build logs to save disk space.
• timeout(time: 1, unit: 'HOURS'): Aborts the build if it takes longer than 1 hour.

Stages

The pipeline is divided into sequential stages:

1. Build: Compiles the Java project using mvn clean package.
2. Deploy to Dev: Deploys the generated WAR file to the Development Tomcat server (20.197.20.20).
3. Deploy to Qa: Deploys to the QA Tomcat server (20.197.20.30).
4. Deploy to Prod: Deploys to the Production Tomcat server (20.197.20.178).

Each deploy stage uses the deploy step (from the "Deploy to container" plugin) with specific Tomcat credentials and URLs.

Post Actions

The post block with always ensures that deleteDir() is called after the pipeline finishes (whether successful or not), cleaning up the workspace.

Reference

• Jenkins Pipeline Options
• Deploy to container Plugin

🧠 Quick Quiz — Pipeline Stages

#

In a declarative pipeline, how are stages executed by default?

Sequentially

In parallel

Randomly

Reverse order

Unless parallel is explicitly used, stages in a declarative pipeline are executed one after another in the order they are defined.

📬 DevopsPilot Weekly — Learn DevOps, Cloud & Gen AI the simple way.
👉 Subscribe here