The Pipeline Maven Plugin provides an advanced set of features for using Apache Maven in Jenkins Pipelines.

The withMaven step configures a maven environment to use within a pipeline job by calling sh "mvn …​ or bat "mvn …​. The selected maven installation is configured and prepended to the path.

It provides several Features to simplify the creation of your Pipeline scripts and ensure the Traceability of Maven builds.

It uses some Sensible default Maven parameters for a CI usage (batch-mode, …​) and automatically configures the Jenkins Report Publishers (Artifacts, JUnit, …​).

The Default Configuration can be defined globally or at the folder level to keep your pipeline code as short as possible while using the expected configuration (Maven settings.xml file…​) globally or locally.

This plugin allows transitioning smoothly from the legacy Maven Integration job type by allowing to reuse Maven Settings Support and by proposing the Trigger downstream pipeline when a snapshot is built.

• Installation
• Changelog
• Usage
• Features
  • Configurable as code
  • Sensible default Maven parameters
  • Maven Settings Support
  • Traceability of Maven builds
  • Report Publishers
  • Default Configuration
  • Trigger downstream pipeline when a snapshot is built
  • Support of Takari’s Maven Wrapper 'mvnw'
• Adding more Maven Reporters
• Database Setup
  • Using a MySQL Database
  • Using a PostgreSQL Database
• Known Limitations
  • Maven and JDK installation not supported in docker.image('xxx').inside{…​}
  • withMaven() not supported in docker.image('xxx').inside{…​} with old versions of the Docker engine
• Frequently Asked Questions

The plugin can be found under the name Pipeline Maven Integration Plugin in the Default Update Site.

For tests purposes only, pre-releases (beta) versions are available in the Experimental Plugin Site and development versions (incremental releases) are archived on every successful build on our CI environment.