[
https://issues.apache.org/jira/browse/SCM-739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16264729#comment-16264729
]
Robert Scholte commented on SCM-739:
------------------------------------
SCM is not only used by maven-release-plugin, so for this project it should be
configurable and current behavior should probably stay the default.
However,I think that in case of {{release:perform}} it makes sense to do a
shallow checkout. That's were we can activate it by default.
> Release Plugin: Use "git --depth 1" When Checking Out
> -----------------------------------------------------
>
> Key: SCM-739
> URL: https://issues.apache.org/jira/browse/SCM-739
> Project: Maven SCM
> Issue Type: Improvement
> Components: maven-scm-provider-gitexe
> Affects Versions: 1.8.1
> Reporter: Ernst de Haan
>
> *Executive summary: Please use {{--depth 1}} when checking out from a git
> repository.*
> Currently when doing {{mvn release:prepare release:perform}}, the git
> checkout step takes a significant amount of time.
> During the git checkout it appears to not only check out the correct version
> of the code, but also _all_ history, as would be done with a regular:
> {code:none}git clone URL{code}
> However, git supports checking out only the latest version of the code base,
> using this command: {code:none}git clone --depth 1 URL{code}
> For the purpose of the Maven Release Plugin, that should be sufficient, as
> far as I can see.
> Changing the plugin to use {{--depth 1}} will:
> - _significantly_ improve performance on larger repositories and/or with a
> lot of history
> - and reduce I/O on repositories with a lot of history.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
