[
https://issues.apache.org/jira/browse/SCM-739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17962808#comment-17962808
]
ASF GitHub Bot commented on SCM-739:
------------------------------------
jira-importer commented on issue #946:
URL: https://github.com/apache/maven-scm/issues/946#issuecomment-2964635409
**[Olivier
Lamy](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=olamy)**
commented
Thanks
[zn...@freebsd.org](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=zn...@freebsd.org)
for your contribution!!
> Release Plugin: Use "git --depth 1" When Checking Out
> -----------------------------------------------------
>
> Key: SCM-739
> URL: https://issues.apache.org/jira/browse/SCM-739
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Improvement
> Components: maven-scm-provider-gitexe
> Affects Versions: 1.8.1
> Reporter: Ernst de Haan
> Assignee: Olivier Lamy
> Priority: Major
> Fix For: 1.10.0
>
>
> *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
(v8.20.10#820010)
