gistfile1.txt

# git remote -v
hugh    [email protected]:hughsaunders/jenkins-rpc (fetch)
hugh    [email protected]:hughsaunders/jenkins-rpc (push)
origin  [email protected]:rcbops/jenkins-rpC (fetch)
origin  [email protected]:rcbops/jenkins-rpC (push)

# git fetch hugh "+refs/pull/*:refs/remotes/hugh/pr/*"
From github.com:hughsaunders/jenkins-rpc
 * [new ref]         refs/pull/1/head -> hugh/pr/1/head
 * [new ref]         refs/pull/1/merge -> hugh/pr/1/merge
 
# git show -p  hugh/pr/1/head
commit 703ff9e
Author: Jean-Philippe Evrard <[email protected]>
Date:   Tue Jul 12 11:56:18 2016 +0100

    Use the current commit for deploying horizon extensions

    This changes the way the gate works, and uses the reference of
    the current commit for the value of the
    horizon_extensions_git_install_branch

    This value is used in the repo_build process, to build a wheel
    for the horizon_extensions, now that horizon_extensions is in-tree.

diff --git a/scripts/aio_build_script.sh b/scripts/aio_build_script.sh
index 62e3664..4d3afaa 100755
--- a/scripts/aio_build_script.sh
+++ b/scripts/aio_build_script.sh
@@ -123,6 +123,8 @@ rackspace_cloud_tenant_id: ${rackspace_cloud_tenant_id}
 rackspace_cloud_username: ${rackspace_cloud_username}
 rackspace_cloud_password: ${rackspace_cloud_password}
 rackspace_cloud_api_key: ${rackspace_cloud_api_key}
+horizon_extensions_git_repo: ${RPC_REPO}
+horizon_extensions_git_install_branch: ${ghprbTargetBranch}
 EOVARS
 set -x