Jenkins Pipeline

Many service-company clients use Jenkins. A declarative pipeline in the repository (Jenkinsfile) checks out the code, runs Maven with parameters, publishes reports and emails the team.

pipeline {
    agent { label 'selenium-linux' }

    parameters {
        choice(name: 'ENV', choices: ['qa', 'staging'], description: 'Environment')
        choice(name: 'SUITE', choices: ['testng-smoke.xml', 'testng-regression.xml'], description: 'Suite')
        choice(name: 'BROWSER', choices: ['chrome', 'firefox', 'edge'], description: 'Browser')
    }

    tools { jdk 'jdk21'; maven 'maven3' }

    stages {
        stage('Checkout') {
            steps { checkout scm }
        }
        stage('Test') {
            steps {
                sh "mvn -B clean test -Denv=${params.ENV} -DsuiteXml=${params.SUITE} -Dbrowser=${params.BROWSER} -Dheadless=true"
            }
        }
    }

    post {
        always {
            junit 'target/surefire-reports/*.xml'
            publishHTML(target: [reportDir: 'target/extent', reportFiles: 'ShopEaseReport.html',
                                 reportName: 'Extent Report', keepAll: true, alwaysLinkToLastBuild: true])
            archiveArtifacts artifacts: 'target/screenshots/*.png', allowEmptyArchive: true
        }
        failure {
            mail to: '[email protected]',
                 subject: "FAILED: ${env.JOB_NAME} #${env.BUILD_NUMBER}",
                 body: "See ${env.BUILD_URL}"
        }
    }
}