From e0eb6f9130b4654d6d3f516d32568381e9cdd19b Mon Sep 17 00:00:00 2001 From: Clark Boylan Date: Thu, 17 Apr 2014 16:17:09 -0700 Subject: [PATCH] Set config prior to git review -s. Requirements proposal jobs need to set git configs for each git repo it is proposing to. This is necessary because it shouldn't set the git config globally for the Jenkins user on the slaves. Change-Id: Id69ba218065022f69d2dd9d140825699d78604e3 --- .../files/slave_scripts/propose_requirements_update.sh | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/modules/jenkins/files/slave_scripts/propose_requirements_update.sh b/modules/jenkins/files/slave_scripts/propose_requirements_update.sh index d93e22e3e2..d710ac63a0 100755 --- a/modules/jenkins/files/slave_scripts/propose_requirements_update.sh +++ b/modules/jenkins/files/slave_scripts/propose_requirements_update.sh @@ -62,6 +62,11 @@ EOF # make sure the project even has this branch if git branch -a | grep -q "^ remotes/origin/$BRANCH$" ; then git checkout -B ${BRANCH} -t origin/${BRANCH} + # Need to set the git config in each repo as we shouldn't + # set it globally for the Jenkins user on the slaves. + git config user.name "OpenStack Proposal Bot" + git config user.email "openstack-infra@lists.openstack.org" + git config gitreview.username "proposal-bot" git review -s popd