maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SCM-739) Release Plugin: Use "git --depth 1" When Checking Out
Date Fri, 01 Dec 2017 23:20:00 GMT

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

Hudson commented on SCM-739:
----------------------------

Build unstable in Jenkins: Maven TLP (wip) » maven-scm » master #12

See https://builds.apache.org/job/maven-wip/job/maven-scm/job/master/12/

> 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
>            Assignee: Olivier Lamy (*$^¨%`£)
>             Fix For: 1.9.6
>
>
> *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)

Mime
View raw message