Releases: jenkinsci/pipeline-maven-plugin
Releases · jenkinsci/pipeline-maven-plugin
pipeline-maven-3.6.8-beta-1
- JENKINS-56044 Merge publishers (junit) with the same filename pattern
- JENKINS-55889 Support tycho-surefire-plugin tests
- JENKINS-56246 on MySQL, support up to 100chars on the maven_artifact.version column
pipeline-maven-3.6.7
JENKINS-55566 Only one downstream pipeline per parent pom dependency is triggered
pipeline-maven-3.6.6
- JENKINS-55378 Support MariaDB 10.2+
- JENKINS-55336 the optimisation "avoid excessive trigger" should not skip some pipeline triggers in case of failure of 'intermediate' builds
- JENKINS-55370 fix Pipeline Maven Plugin first initialisation exception when the plugin first initialisation takes place in an init.groovy script
- JENKINS-55325 Better error message when the
<server>
definition of Maven (global) settings can not be injected because the associated Jenkins credentials cannot be found.
[withMaven] Global Maven settings - Failure to resolve credentials: [mavenServerId: github, jenkinsCredentials: github-credentials]
pipeline-maven-3.6.6-beta-4
- JENKINS-55378 Support MariaDB 10.2+
- JENKINS-55370 fix Pipeline Maven Plugin first initialisation exception when the plugin first initialisation takes place in an init.groovy script
- JENKINS-55336 the optimisation "avoid excessive trigger" should not skip some pipeline triggers in case of failure of 'intermediate' builds
- JENKINS-55325 Better error message when the
<server>
definition of Maven (global) settings can not be injected because the associated Jenkins credentials cannot be found.
[withMaven] Global Maven settings - Failure to resolve credentials: [mavenServerId: github, jenkinsCredentials: github-credentials]
pipeline-maven-3.6.6-beta-3
- JENKINS-55370 fix Pipeline Maven Plugin first initialisation exception when the plugin first initialisation takes place in an init.groovy script
- JENKINS-55336 the optimisation "avoid excessive trigger" should not skip some pipeline triggers in case of failure of 'intermediate' builds
- JENKINS-55325 Better error message when the
<server>
definition of Maven (global) settings can not be injected because the associated Jenkins credentials cannot be found.
[withMaven] Global Maven settings - Failure to resolve credentials: [mavenServerId: github, jenkinsCredentials: github-credentials]
pipeline-maven-3.6.6-beta-2
- JENKINS-55336 the optimisation "avoid excessive trigger" should not skip some pipeline triggers in case of failure of 'intermediate' builds
- JENKINS-55325 Better error message when the
<server>
definition of Maven (global) settings can not be injected because the associated Jenkins credentials cannot be found.
[withMaven] Global Maven settings - Failure to resolve credentials: [mavenServerId: github, jenkinsCredentials: github-credentials]
pipeline-maven-3.6.6-beta-1
- JENKINS-55325 Better error message when the
<server>
definition of Maven (global) settings can not be injected because the associated Jenkins credentials cannot be found.
[withMaven] Global Maven settings - Failure to resolve credentials: [mavenServerId: github, jenkinsCredentials: github-credentials]
pipeline-maven-3.6.5
JENKINS-49337 fix InterruptedException when the processing of Maven outputs takes more than 300s
JENKINS-55090 Make MySQL the recommended database
JENKINS-55010 better detection of temporary file name of pom.xml when using "flatten-maven-plugin" and overwriting the default "flattenedPomFilename" setting
pipeline-maven-3.6.5-beta-1
JENKINS-49337 fix InterruptedException
JENKINS-55090 Make MySQL the recommended database
JENKINS-55010 better detection of temporary file name of pom.xml when using "flatten-maven-plugin" and overwriting the default "flattenedPomFilename" setting
pipeline-maven-3.6.4
- JENKINS-54515 don't trigger downstream pipelines that generate artifacts with the same groupId:artifactId as the dependency that made them eligible for a downstream pipeline trigger
- Add parameter in
withMaven()
to specify the temporary binary directory- use case: If the build system (cmake for example) relies on PATH environment variable for detecting source/environement changes, the build system will recompile all sources