f74501e781
This patch adds support for the Maven release build wrapper. The Maven release plugin makes use of the concept of jenkins Actions to trigger the actual release - https://wiki.jenkins-ci.org/display/JENKINS/Action+and+its+family+of+subtypes The actual code for the action - https://github.com/jenkinsci/m2release-plugin/blob/master/ src/main/java/org/jvnet/hudson/plugins/m2release/M2ReleaseAction.java, seems to put together all the required parameters and makes a call to scheduleBuild2 and passes an Action object with it. Afaik, JJB doesn't support the concept of Actions. If the M2ReleaseAction was an instance of Builder, instead of Action it would work with this. Currently, I don't see how the actual build (release) can be triggered from JJB config, and it seems like we can define the build wrapper alone as part of the job definition, and would still have to trigger the release from the UI for the job like - <jobname>/m2release Change-Id: Ifc979cdb8e40ad31debff04f745649f23f7ef91a
17 lines
775 B
XML
17 lines
775 B
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<project>
|
|
<buildWrappers>
|
|
<org.jvnet.hudson.plugins.m2release.M2ReleaseBuildWrapper>
|
|
<releaseGoals>-Dresume=false release:prepare release:perform</releaseGoals>
|
|
<dryRunGoals>-Dresume=false -DdryRun=true release:prepare</dryRunGoals>
|
|
<numberOfReleaseBuildsToKeep>2</numberOfReleaseBuildsToKeep>
|
|
<selectCustomScmCommentPrefix>true</selectCustomScmCommentPrefix>
|
|
<selectAppendHudsonUsername>false</selectAppendHudsonUsername>
|
|
<selectScmCredentials>true</selectScmCredentials>
|
|
<releaseEnvVar/>
|
|
<scmUserEnvVar>SCM_USER</scmUserEnvVar>
|
|
<scmPasswordEnvVar>SCM_PASSWORD</scmPasswordEnvVar>
|
|
</org.jvnet.hudson.plugins.m2release.M2ReleaseBuildWrapper>
|
|
</buildWrappers>
|
|
</project>
|