Releases: jenkinsci/pipeline-maven-plugin
Releases · jenkinsci/pipeline-maven-plugin
pipeline-maven-3.0.7
- JENKINS-48539: Maven Event Spy should use Maven built-in logging framework (SLF4J) instead of System.out
pipeline-maven-3.1.0-beta-1
- JENKINS-46368: PipelineGraphPublisher should also declare artifacts' parents as dependency
pipeline-maven-3.0.6
Bug fixes:
- JENKINS-46577 JdbcSQLException: Table "MAVEN_ARTIFACT" not found
pipeline-maven-3.0.6-beta-1
Bug fixes:
- JENKINS-46577 JdbcSQLException: Table "MAVEN_ARTIFACT" not found
pipeline-maven-3.0.5
- JENKINS-48362: Regression: 3.0.3 no longer support whitespace in Maven installation path
pipeline-maven-3.0.4
- JENKINS-48264: regression: 3.0.3 no longer supports whitespaces in job name
pipeline-maven-3.0.3
- JENKINS-47823
withMaven
fails to inject Maven settings files with docker-pipeline 1.14. When usingwithMaven
indocker.image('my-image').inside{}
and docker-pipeline 1.14:- Either prepend the PATH environment varizbles when invoking "mvn"
sh 'export PATH=$MVN_CMD_DIR:$PATH && mvn clean deploy'
- Or use Takari's Maven Wrapper
sh './mvnw clean deploy'
- Introduce the
MVN_CMD_DIR
environment variable in addition to theMVN_CMD
variable introduced in 3.0.3-beta-1 because a file cannot be added to thePATH
, it must be the parent folder of this file that is added to thePATH
Pattern to use withMaven()
in a docker.image().inside{}
step of docker-pipeline 1.14
node("linux-agent-with-docker") {
docker.image('maven').inside {
withMaven(mavenSettingsConfig: 'my-maven-settings') {
git "https://github.com/cyrille-leclerc/my-jar.git"
// prepend the $MVN_CMD_DIR variable to the $PATH environment variable
// in each "sh" step that invokes mvn
sh 'export PATH=$MVN_CMD_DIR:$PATH && mvn help:effective-settings'
}
}
}
Troubleshooting
// prepend the $MVN_CMD_DIR variable to the $PATH environment variable
// in each "sh" step that invokes mvn
// for troubleshooting, we display `which mvn`
sh 'export PATH=$MVN_CMD_DIR:$PATH && which mvn && mvn help:effective-settings'
pipeline-maven-3.0.3-beta-2
- Introduce the
MVN_CMD_DIR
environment variable in addition to theMVN_CMD
variable introduced in 3.0.3-beta-1 because a file cannot be added to thePATH
, it must be the parent folder of this file that is added to thePATH
Pattern to use withMaven()
in a docker.image().inside{}
step of docker-pipeline 1.14
node("linux-agent-with-docker") {
docker.image('maven').inside {
withMaven(mavenSettingsConfig: 'my-maven-settings') {
git "https://github.com/cyrille-leclerc/my-jar.git"
// prepend the $MVN_CMD_DIR variable to the $PATH environment variable
// in each "sh" step that invokes mvn
sh 'export PATH=$MVN_CMD_DIR:$PATH && mvn help:effective-settings'
}
}
}
Troubleshooting
// prepend the $MVN_CMD_DIR variable to the $PATH environment variable
// in each "sh" step that invokes mvn
// for troubleshooting, we display `which mvn`
sh 'export PATH=$MVN_CMD_DIR:$PATH && which mvn && mvn help:effective-settings'
pipeline-maven-3.0.3-beta-1
node("linux-agent-with-docker") {
docker.image('maven').inside {
withMaven(mavenSettingsConfig: 'my-maven-settings') {
git "https://github.com/cyrille-leclerc/my-jar.git"
// prepend the $MVN_CMD variable to the $PATH environment variable in each "sh" step that invokes mvn
sh 'export PATH=$MVN_CMD:$PATH && mvn help:effective-settings'
}
}
}
pipeline-maven-3.0.2
- JENKINS-47589 Better details of the database status for better troubleshooting
- JENKINS-47508 Fix NPE when
executionId
is missing