Plugin Information

Plugin ID	m2release
Latest Release	0.10.0-h-1
Latest Release Date	Aug 30, 2012
Sources	Github
Support	Eclipse Hudson Forum
Issue Tracking	Eclipse Bugzilla

This plugin allows you to perform a release build using the maven-release-plugin from within Hudson.

Project Configuration

On the job configuration page, enable the "Maven release build" under the Build Environment heading and add whatever release goals and options your require.

Performing a Release Build

Follow the "Perform Maven Release" link

and choose "Schedule Maven Release Build".

Using with Nexus Staging

Nexus staging will create a new Stage for each unique IP Address, deploy users and HTTP User agent.

For a particular Hudson slave the first two will be the same for all builds - so you need to configure Maven to use a unique HTTP User-Agent for the deploy.

To do this make sure your maven settings contains something like the following where the id matches the id for the release repository in the deployment section of your project:

  <server>
    <id>nexus</id>
    <username>my_login</username>
    <password>my_password</password>
    <configuration>
      <httpHeaders>
        <property>
          <name>User-Agent</name>
          <value>Maven m2Release (java:${java.vm.version} ${env.BUILD_TAG }</value>
        </property>
      </httpHeaders>
    </configuration>
  </server>

FAQ

If your build fails with the following:

[INFO] Executing: mvn clean verify --no-plugin-updates --batch-mode -P null,null
'mvn' is not recognized as an internal or external command,
operable program or batch file.

Then this is a maven bug not a hudson plug-in bug.
The solution is to upgrade to version 2.0-beta-8 or later of the maven-release-plugin in your project.

Some users with CVS (cvs+ssh) have reported that a release just hangs while accessing the ssh server (issue #4783). The solution is to use the native CVS client and append "-Dmaven.scm.provider.cvs.implementation=cvs_native" to the release arguments.

The use of this plugin requires that Maven can tag your code. You may need to use cvs/svn etc from the CI account on the server that is performing the release so the native tools used by maven have the required authentication information. (this is outside of Hudson SCM authentication)

Version History

0.7.0+ (Not yet released)

See the Jenkins WIKI for info.

Fix issue #7837 - release does not use the maven installation it was configured with but whatever is on the path.

0.6.1 (17th September 2010)

Fix issue #7492 - Fix internal error which occurs under tomcat but not winston due to a double redirect.

0.6.0 (16th September 2010)

Fix issue #3876 - Add an icon to release builds.
Fix issue #6791 - Scheduling a release will fail silently if a build is already in the queue.

0.5.3 (12th July 2010)

Fix NPE when trying to close nexus state.

0.5.2 (8th July 2010)

Re-Fix issue #6873 - After scheduling a release build a HTTP 404 error page can be displayed.

0.5.1 (30th June 2010)

Fix issue #6887 - NPE during release when version is decided by Maven.
Fix issue #6873 - After scheduling a release build a HTTP 404 error page can be displayed.

0.5.0 (25th June 2010)

Fix issue #6630 - plugin closes incorrect nexus stage

0.4.0 (26th May 2010)

Fix issue #5295 - plugin now allows you to pass SCM username/password to maven.
Fixed to work with Nexus 1.5.0 (authorization was not occuring correctly).
Added support for specifying an exact version to use across all modules (issue #3429).
Added support for specifying scmCommentPrefix (issue #4127 ).
Added support for appending the Hudson username to the scmCommentPrefix (optional).
Added config settings (per project) which option(s) should be enabled by default for the Release Action.

0.3.4 (29th December 2009)

Fix help pages not showing up when Hudson runs on a case sensitive file system.
Use POST instead of GET to avoid long form URLs.

0.3.3 (21th August 2009)

Fix issue #4172 that prevented hudson upgrades working correctly.

0.3.2 (24th July 2009)

(0.3.0 & 0.3.1 were not released)
Hudson doesn't set the MAVEN_OPTS variable so added a workaround in the plugin issue #3644
Added a sepcific security right to allow fine grained release permissions.
Added support for closing Nexus Pro staging repository after a release.
Added some synchronization to protect against a theoretical race condition.
Fix issue #4065 that caused the release plugin to blow up when releases where n-SNAPSHOT.

0.2.0 (23rd March 2009)

Added support for hudson Security (only users who can perform a manual build can trigger a release build).
Release goals now default to -Dresume=false release:prepare release:perform.
Added support for specifying exact versions to use.
Added support for appending hudson build number as maven build number qualifier.
Integrated with Hudson security. Users require "Build" rights in order to create a release
Requires Hudson >= 1.292.

0.1.0 (16th March 2009)

Initial version.
Can only use the auto versioning feature of the maven-release-plugin.
Tested with a simple single module project, in a master only hudson environment.
Requires Huson >= 1.288.

TODO

In no order:

~~Integrate with Hudson security model.~~
~~Add support for specifying exact versions to use.~~
~~Add support for auto-versioning with hudson build number as maven build number qualifier.~~
~~Add a sepcific security right to produce a release build.~~
Add support to clean workspace before a release build is performed for the case where hudson uses update (issue #3925).
work in progress: Add support to clean local maven repository before a release build is performed. Useful for guaranteeing the release is buildable from scratch.
Update wiki and add help for latest features.
~~Check compatability with Hudson master/slave.~~
~~Check compatability with multi-module projects.~~
~~Add some feedback onto the build history to show release builds (like the~~ ~~Release Plugin~~).
Get hudson to recognise the releases as build artifacts.
See if we can do something in the freestyle for maven builds.
Nexus support
- ~~rewrite support from ground up to avoid closing incorrect repository~~
- ~~Add support for closing~~ ~~nexus pro~~ ~~staging repos on succesful build completion.~~
- ~~Add support (if possible) for changing the User agent to support grouping into a~~ ~~nexus pro~~ ~~staging repo.~~
- Add support for removing a nexus pro staging repo on a failed build.

M2 Release Plugin

Plugin Information

Project Configuration

Performing a Release Build

Using with Nexus Staging

FAQ

Version History

0.7.0+ (Not yet released)

0.6.1 (17th September 2010)

0.6.0 (16th September 2010)

0.5.3 (12th July 2010)

0.5.2 (8th July 2010)

0.5.1 (30th June 2010)

0.5.0 (25th June 2010)

0.4.0 (26th May 2010)

0.3.4 (29th December 2009)

0.3.3 (21th August 2009)

0.3.2 (24th July 2009)

0.2.0 (23rd March 2009)

0.1.0 (16th March 2009)

TODO

Labels:

Comments (22)

Jason Zaugg says:

Gabriel Falkenberg says:

darren hartford says:

Giancarlo Rosso says:

pringles says:

Julien HENRY says:

Bertrand Gressier says:

Bertrand Gressier says:

Edgar Vonk says:

fabrice says:

Abhishek Chaturvedi says:

Baptiste MATHUS says:

Simon Buss says:

Daniel Triphaus says:

Matt Pierce says:

Bertrand Gressier says:

Shadow de Coutemeier says:

Jim Daniel says:

Lars Fischer says:

Mike Dalrymple says:

daniel nitzan says:

vijay says:

Status Code: 500