[
https://issues.apache.org/jira/browse/MRELEASE-978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MRELEASE-978.
-----------------------------------
Resolution: Cannot Reproduce
Assignee: Robert Scholte
We're using the maven-release-plugin for quite some projects at github. Take a
look at https://github.com/codehaus-plexus/ which contains a set of libraries
used by Maven or Maven Plugins.
> unable to perform Maven Release Build with GitHub
> -------------------------------------------------
>
> Key: MRELEASE-978
> URL: https://issues.apache.org/jira/browse/MRELEASE-978
> Project: Maven Release Plugin
> Issue Type: Bug
> Reporter: Mahendra
> Assignee: Robert Scholte
> Priority: Major
>
> I am integrating maven release build with git hub and configured the same in
> Jenkins 2.7.2 and it is authenticating using credential plugin which I have
> created using ssh key on an account to communicate with github. The snapshot
> build works well and result is success.
> When I am performing maven release build it thows the error saying that
> unable to perform
> git clone command or repository is not known
> I have given the scm connection and developer connection in the pom file.
> As said earlier, snapshot build works fine which means the authentication
> with git is fine. But during release build it is failing. Do I need to
> mentioned ssh keys (provate and public) somewhere also in order to have
> release build? or how maven release build picks up the credentials?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
