[
https://issues.jenkins-ci.org/browse/JENKINS-12128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159236#comment-159236
]
SCM/JIRA link daemon commented on JENKINS-12128:
------------------------------------------------
Code changed in jenkins
User: imod
Path:
src/main/java/org/jvnet/hudson/plugins/m2release/M2ReleaseAction.java
src/main/java/org/jvnet/hudson/plugins/m2release/M2ReleaseBuildWrapper.java
http://jenkins-ci.org/commit/m2release-plugin/c78a508bcb9634c01b582ea7c3791fae86eeded0
Log:
[FIXED JENKINS-12128] expose dryRun flag, release and dev version as env
variables
Compare: https://github.com/jenkinsci/m2release-plugin/compare/d302d15...c78a508
> Expose releaseVersion and developmentVersion as environment variables
> ---------------------------------------------------------------------
>
> Key: JENKINS-12128
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12128
> Project: Jenkins
> Issue Type: Improvement
> Components: m2release
> Affects Versions: current
> Environment: Not applicable
> Reporter: Jason Spotswood
> Assignee: teilo
> Labels: envinronment-variables
>
> When building a Maven release, the parameters Release Version and Development
> Version are passed to the Maven release command via -DreleaseVersion and
> -DdevelopmentVersion respectively.
> It would be extremely handy to expose these as environment variables so that
> they can be accessed throughout the job configuration; for example just like
> the variable WORKSPACE.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
