[JIRA] (OVIRT-620) Optimize how Jenkins fetchs ovirt-engine from gerrit
[
https://ovirt-jira.atlassian.net/browse/OVIRT-620?page=com.atlassian.jira...
]
Nadav Goldin commented on OVIRT-620:
------------------------------------
from man git gc:
{quote}
--aggressive
Usually git gc runs very quickly while providing good disk space utilization
and performance. This option will cause git gc to more aggressively optimize the
repository at the expense of taking much more time. The effects of this optimization are
persistent, so this option only needs to be used occasionally; every few hundred
changesets or so.
{quote}
I am not sure if we have 100s of patchsets/daily, but maybe weekly/monthly. Other than
that I never used it, so not sure if it could be a source of other problems.
Optimize how Jenkins fetchs ovirt-engine from gerrit
----------------------------------------------------
Key: OVIRT-620
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-620
Project: oVirt - virtualization made easy
Issue Type: Sub-task
Reporter: Nadav Goldin
Assignee: infra
ovirt-engine git repository is at the time of writing is of size 244MB, where
ovirt-engine/.git alone takes 160MB.
There are two things which might be done:
1. Find a way to optimize ovirt-engine.git/.git size, this needs to be explored deeply.
2. Check if it is possible to configure git plugin to not download the entire history,
although Jenkins attempts to optimize that, it still looks like the git plugin is
downloading the entire history(this is what a random check on the slaves using du
../jenkins/workspace/...../.git -h -s showed)
for instance the following command takes only 91Mb:
{quote}git clone --depth 1 --branch master {quote}
Although this will not solve real network/storage issues, it could help reduce those
problems and in the overall decrease jobs runtime. As Gerrit is still on AWS, this is a
considerable amount of traffic for each job we might be able to reduce.
--
This message was sent by Atlassian JIRA
(v1000.126.1#100004)