[
https://issues.jenkins-ci.org/browse/JENKINS-13527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Maxwell updated JENKINS-13527:
-----------------------------------
Labels: environment-variables (was: envinronment-variables)
Description:
When building a Maven release it would be very helpful if "custom SCM tag" and
"SCM login Username" were exposed as environment variables
was:
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.
> Expose custom SCM tag and SCM login Username as environment variables
> ---------------------------------------------------------------------
>
> Key: JENKINS-13527
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13527
> Project: Jenkins
> Issue Type: Improvement
> Components: m2release
> Affects Versions: current
> Environment: Not applicable
> Reporter: Jeff Maxwell
> Assignee: teilo
> Labels: environment-variables
>
> When building a Maven release it would be very helpful if "custom SCM tag"
> and "SCM login Username" were exposed as environment variables
--
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