From cbea39ccd47dd63c09c7f03019a5c6ebce4ac148 Mon Sep 17 00:00:00 2001 From: Ken Dreyer Date: Thu, 9 Jan 2014 17:24:04 -0700 Subject: [PATCH] jenkins: support autobuild key or release key We need Jenkins to build ceph-deploy more often so we can have more testing, but we don't want to sign these "unofficial" builds with the official release key. Conditionally select the release key or the autobuild key based upon the $RELEASE environment variable. Jenkins will set this variable using a parameter when it runs each ceph-deploy build. For formal releases, we will set the parameter to "true". Signed-off-by: Ken Dreyer --- scripts/jenkins-build | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/scripts/jenkins-build b/scripts/jenkins-build index e2643e2..9d7a681 100755 --- a/scripts/jenkins-build +++ b/scripts/jenkins-build @@ -5,8 +5,17 @@ set -x -export GNUPGHOME=/home/jenkins-build/build/gnupg.ceph-release/ -export KEYID=17ED316D +# Jenkins will set $RELEASE as a parameter in the job configuration. +if $RELEASE ; then + # This is a formal release. Sign it with the release key. + export GNUPGHOME=/home/jenkins-build/build/gnupg.ceph-release/ + export KEYID=17ED316D +else + # This is an automatic build. Sign it with the autobuild key. + export GNUPGHOME=/home/jenkins-build/build/gnupg.autobuild/ + export KEYID=03C3951A +fi + HOST=$(hostname --short) echo "Building on ${HOST}" echo " DIST=${DIST}" -- 2.47.3