[
https://issues.apache.org/jira/browse/MRELEASE-868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MRELEASE-868.
-----------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period
of time. If you think this issue still applies, retest your problem with the
most recent version of Maven and the affected component, reopen and post your
results.
> Allow passing in SSH key via parameter for Git releases
> -------------------------------------------------------
>
> Key: MRELEASE-868
> URL: https://issues.apache.org/jira/browse/MRELEASE-868
> Project: Maven Release Plugin
> Issue Type: Improvement
> Affects Versions: 2.4.2
> Reporter: Konrad Windszus
> Priority: Major
>
> When triggering a release from a shared server (e.g. a globally shared
> jenkins), it is useful to let the release manager use his own credentials for
> the release. The release plugin from
> https://wiki.jenkins-ci.org/display/JENKINS/M2+Release+Plugin supports that
> for username, password authentication. In case of SSH authentication I cannot
> inject anything, because the maven-release-plugin does not provide that
> option. It would be great if you could allow to pass in an arbitrary SSH key
> (together with a passphrase) to be used during the release.
> That should work with jGit and Native Git.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
