[
https://issues.apache.org/jira/browse/SCM-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17962121#comment-17962121
]
ASF GitHub Bot commented on SCM-571:
------------------------------------
jira-importer opened a new issue, #789:
URL: https://github.com/apache/maven-scm/issues/789
**[Gerald
Jerome](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jjflyboy)**
opened
**[SCM-571](https://issues.apache.org/jira/browse/SCM-571?redirect=false)** and
commented
In the log of a release:perform, I noticed that the git clone command is
being run. This will be a real killer for large repositories on the other side
of a slow network or disk drive. It can also eat up disk space. A checkout
would be preferred. Perhaps, the following would be better:
mkdir -p target/checkout; cd target/checkout; GIT_DIR=../../.git git
checkout *; cd ../..
or,
git checkout \<new tag> #do perform in the original workspace
Regards.
---
**Affects:** 1.4
1 votes, 1 watchers
> use checkout, not clone under release:perform
> ---------------------------------------------
>
> Key: SCM-571
> URL: https://issues.apache.org/jira/browse/SCM-571
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Improvement
> Components: maven-scm-provider-gitexe
> Affects Versions: 1.4
> Reporter: Gerald Jerome
> Assignee: Mark Struberg
> Priority: Major
>
> In the log of a release:perform, I noticed that the git clone command is
> being run. This will be a real killer for large repositories on the other
> side of a slow network or disk drive. It can also eat up disk space. A
> checkout would be preferred. Perhaps, the following would be better:
> mkdir -p target/checkout; cd target/checkout; GIT_DIR=../../.git git checkout
> *; cd ../..
> or,
> git checkout <new tag> #do perform in the original workspace
> Regards.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
