[
https://jira.codehaus.org/browse/MRELEASE-868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=362052#comment-362052
]
Justin Georgeson commented on MRELEASE-868:
-------------------------------------------
Apparently at least for Shell command steps in Jenkins, using the SSH Agent
plugin for the build environment allows using Jenkins credentials to run the
maven release commands.
> Allow passing in SSH key via parameter for Git releases
> -------------------------------------------------------
>
> Key: MRELEASE-868
> URL: https://jira.codehaus.org/browse/MRELEASE-868
> Project: Maven Release Plugin
> Issue Type: Improvement
> Affects Versions: 2.4.2
> Reporter: Konrad Windszus
>
> 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
(v6.1.6#6162)
