Enable debug tarball on BMC
Two aspects of this change are:
Code update:
- Install debug tarball post code update.
- TBD: add parameter in code update jenkins job to take user
input.
CT run:
- Install debug tarball part of the __init__ setup procedure.
- TBD: add parameter in CT jenkins job to take user input.
- For manual test, users need to specify the debug tarball as
an input.
Test automation code must handle respectively if it has dependencies on
debug tarball binary as part of the "Suite Setup" or "Test Setup".
Resolves openbmc/openbmc-test-automation#461
Change-Id: Idc6f976776ad57a797cff428c840c133fc41ad8a
Signed-off-by: George Keishing <gkeishin@in.ibm.com>
diff --git a/tools/generate_argumentfile.sh b/tools/generate_argumentfile.sh
index f662990..1a114a3 100755
--- a/tools/generate_argumentfile.sh
+++ b/tools/generate_argumentfile.sh
@@ -21,3 +21,4 @@
echo "--variable OS_HOST:$OS_HOST" >> $ARG_FILE
echo "--variable OS_USERNAME:$OS_USERNAME" >> $ARG_FILE
echo "--variable OS_PASSWORD:$OS_PASSWORD" >> $ARG_FILE
+echo "--variable DEBUG_TARBALL_PATH:$DEBUG_TARBALL_PATH" >> $ARG_FILE