From fc62f782bed6c292c3c4692065ad12a97ce8700c Mon Sep 17 00:00:00 2001 From: Sergey Lukjanov Date: Wed, 11 Dec 2013 00:43:29 +0400 Subject: [PATCH] Use full clone in propose requirements updates Shallow (--depth=1) clone raises some problems with git review tool. Here is the part of the failed propose-requirements-update job logs: + git clone --depth=1 ssh://jenkins@review.openstack.org:29418/openstack/cinder.git + pushd cinder + git review -s + git review -d I2d8f240009d2f847b321baa011880f753783be83 Downloading refs/changes/69/60969/1 from gerrit into review/jenkins/openstack/requirements fatal: unresolved deltas left after unpacking fatal: unpack-objects failed Change-Id: Ie69261fde73c18134906f3edd1263479830005c4 --- .../jenkins/files/slave_scripts/propose_requirements_update.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/jenkins/files/slave_scripts/propose_requirements_update.sh b/modules/jenkins/files/slave_scripts/propose_requirements_update.sh index ca5852d553..6433e49a53 100755 --- a/modules/jenkins/files/slave_scripts/propose_requirements_update.sh +++ b/modules/jenkins/files/slave_scripts/propose_requirements_update.sh @@ -55,7 +55,7 @@ EOF PROJECT_DIR=$(basename $PROJECT) rm -rf $PROJECT_DIR - git clone --depth=1 ssh://$USERNAME@review.openstack.org:29418/$PROJECT.git + git clone ssh://$USERNAME@review.openstack.org:29418/$PROJECT.git pushd $PROJECT_DIR git review -s