Declarative Jenkins Pipeline for Spring Boot

Intermediate·2 min read·

Fast recall

Quick revision

Core answer

A declarative Jenkins pipeline uses a Jenkinsfile with a structured pipeline {} block containing stages for build, test, and deploy. You define agent, environment variables, and sequential stages that run Maven or Gradle commands, run tests, build a Docker image, and push to a registry.

Interview Answer2 min

A Jenkins declarative pipeline is a Jenkinsfile written in the declarative syntax — a structured DSL that defines stages, steps, agents, and post-conditions with explicit, readable structure. For a Spring Boot project, the pipeline typically covers checkout, build, test, analysis, Docker image creation, and deployment.

Pipeline structure

The pipeline {} block is the top-level wrapper; agent { docker { image 'eclipse-temurin:21' } } runs every stage inside a JDK container — no Java installation required on the Jenkins agent itself, and different pipelines can use different JDK versions simultaneously
stages contains an ordered list of stage blocks; each stage groups related steps and is visible as a named column in Jenkins' Stage View — failed stages are immediately visible without reading the full log
environment at the pipeline level defines variables available in every stage — DOCKER_REGISTRY = 'my-registry.io' used in build and push stages without repetition

Testing and quality gates

The test stage runs mvn verify rather than mvn test — verify triggers Surefire for unit tests and Failsafe for integration tests and JaCoCo coverage; mvn test skips integration tests
junit 'target/surefire-reports/*.xml' in the post { always {} } block publishes test results to Jenkins even when the build fails — test reports should be collected regardless of outcome so failures are visible without reading log output
Add jacoco(execPattern: 'target/jacoco.exec', minimumLineCoverage: '80') to fail the build when coverage drops below the threshold; this requires the JaCoCo Jenkins plugin

Deployment and credentials

Use withCredentials([usernamePassword(credentialsId: 'docker-registry', usernameVariable: 'DOCKER_USER', passwordVariable: 'DOCKER_PASS')]) to inject registry credentials into the Docker push step — credentials never appear in the Jenkinsfile or the build log
withKubeConfig([credentialsId: 'kubeconfig']) injects a kubeconfig for kubectl apply in the deploy stage — the kubeconfig lives in Jenkins Credentials, not committed to the repository

Interview-ready guide

Interview answer

Pipeline structure

The pipeline {} block is the top-level wrapper; agent { docker { image 'eclipse-temurin:21' } } runs every stage inside a JDK container — no Java installation required on the Jenkins agent itself, and different pipelines can use different JDK versions simultaneously
stages contains an ordered list of stage blocks; each stage groups related steps and is visible as a named column in Jenkins' Stage View — failed stages are immediately visible without reading the full log
environment at the pipeline level defines variables available in every stage — DOCKER_REGISTRY = 'my-registry.io' used in build and push stages without repetition

Testing and quality gates

The test stage runs mvn verify rather than mvn test — verify triggers Surefire for unit tests and Failsafe for integration tests and JaCoCo coverage; mvn test skips integration tests
junit 'target/surefire-reports/*.xml' in the post { always {} } block publishes test results to Jenkins even when the build fails — test reports should be collected regardless of outcome so failures are visible without reading log output
Add jacoco(execPattern: 'target/jacoco.exec', minimumLineCoverage: '80') to fail the build when coverage drops below the threshold; this requires the JaCoCo Jenkins plugin

Deployment and credentials

Use withCredentials([usernamePassword(credentialsId: 'docker-registry', usernameVariable: 'DOCKER_USER', passwordVariable: 'DOCKER_PASS')]) to inject registry credentials into the Docker push step — credentials never appear in the Jenkinsfile or the build log
withKubeConfig([credentialsId: 'kubeconfig']) injects a kubeconfig for kubectl apply in the deploy stage — the kubeconfig lives in Jenkins Credentials, not committed to the repository

03 · Deep dive