[ 
https://issues.apache.org/jira/browse/SCM-886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16473410#comment-16473410
 ] 

Matthieu Brouillard commented on SCM-886:
-----------------------------------------

{quote}I guess a static {{.git/config}} in the test repo shall be enough.
{quote}
No it is not because the clone command already created a config file. We could 
write/append to it but it is quite ugly ; the best is to issue a git config 
command on this cloned repository. But I have not seen any command allowing to 
call 'config', did I miss looked?

> Tests with checkin rely on global git config
> --------------------------------------------
>
>                 Key: SCM-886
>                 URL: https://issues.apache.org/jira/browse/SCM-886
>             Project: Maven SCM
>          Issue Type: Bug
>          Components: maven-scm-provider-gitexe
>    Affects Versions: 1.9.5
>            Reporter: Matthieu Brouillard
>            Priority: Major
>
> Inside maven-scm-provider-gitexe project, the two following tests 
> `GitCheckInCommandNoBranchTest.testCheckinNoBranch` and 
> `GitCheckInCommandTest.testCheckinAfterRename` expect a global user.name and 
> user.email to be set.
> On installations where .gitconfig contains the following:
> {{[user]}}
> {{useConfigOnly = true}}
> The tests will fail.
> It would be better after repository creation to configure a user name & email 
> at project level.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to