[
https://ovirt-jira.atlassian.net/browse/OVIRT-1173?page=com.atlassian.jir...
]
Barak Korren commented on OVIRT-1173:
-------------------------------------
Since we're typically cloning into a workspace that already contains a clone from a
previous builds, I don't think the real-life benefit of using a shallow clone will be
that grate. Worth checking though.
Also, wouldn't this prevent us from doing interesting things with {{git log}}, {{git
show}} or {{git describe}} from inside the automation scripts?
Please use git shallow clone as jobs default
--------------------------------------------
Key: OVIRT-1173
URL:
https://ovirt-jira.atlassian.net/browse/OVIRT-1173
Project: oVirt - virtualization made easy
Issue Type: By-EMAIL
Reporter: rgolan
Assignee: infra
Labels: standard-ci
Most if not all the git clone of the jobs don't need history at all.
For ovirt-engine I see it downloading *11Mb* using --depth 1 vs. *157Mb*
for regular clone.
R
--
This message was sent by Atlassian JIRA
(v1000.773.2#100032)