From c70e7f7817bba97fc5d5661f63ab2b5587855417 Mon Sep 17 00:00:00 2001
From: Elizabeth Liner <eliner@us.ibm.com>
Date: Wed, 8 Mar 2017 15:23:25 -0600
Subject: [PATCH] Adding hardware to fspCI command for the release tool (Take
 2)

Change-Id: Ib7edebae62238e4673092d98a6c9c3ff8cc2d940
RTC:170870
Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/37692
Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com>
Reviewed-by: Elizabeth K. Liner <eliner@us.ibm.com>
Tested-by: Jenkins OP Build CI <op-jenkins+hostboot@us.ibm.com>
Tested-by: FSP CI Jenkins <fsp-CI-jenkins+hostboot@us.ibm.com>
Reviewed-by: Andrew J. Geissler <andrewg@us.ibm.com>
Reviewed-by: Stephen M. Cprek <smcprek@us.ibm.com>
Reviewed-by: William G. Hoffa <wghoffa@us.ibm.com>
---
 src/build/citest/auto-release | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/build/citest/auto-release b/src/build/citest/auto-release
index 13f1031cbc3..f4666c34b0c 100755
--- a/src/build/citest/auto-release
+++ b/src/build/citest/auto-release
@@ -150,7 +150,7 @@ function run_fsp_ci {
     while true;
     do
         ((retries--))
-        OUTPUT="$(fsp-CI-jenkins -r $FIPS_RELEASE -t $FEATURE --force)";
+        OUTPUT="$(fsp-CI-jenkins -r $FIPS_RELEASE -t $FEATURE --test_on_hardware=1 --force)";
 
         # Check if fsp-CI-jenkins failed to start
         if [ $? -eq 0 ]; then