ci

Use a declarative Jenkinsfile with a Maven agent that runs mvn clean verify, publishes JUnit results, records JaCoCo coverage, and builds and pushes a Docker image only on the main branch or version tags.

Use a multi-stage build that extracts the layered jar with jarmode=layertools, then copies the layers into a runtime stage based on eclipse-temurin:21-jre-alpine running as a non-root user with the JarLauncher entry point.

Pick exactly one per repository, never both. This skill provides the Jenkins variant; a separate github-actions-ci skill covers the GitHub Actions alternative with equivalent behavior.

Spring Boot 3.2 moved the launcher class to org.springframework.boot.loader.launch.JarLauncher. Using the old org.springframework.boot.loader.JarLauncher path on Spring Boot 3.2+ causes this failure.

Configure the jacoco-maven-plugin check goal bound to the verify phase with line and branch minimums, such as 0.80 line and 0.70 branch coverage. Running mvn verify then fails the build when coverage drops below the thresholds.

The public pipeline is deliberately vanilla with no shared library imports. You can wrap the build and image stages in a private fork with a one-line shared library call while keeping the shared catalogue vendor-neutral.