[PATCH 1/3] scripts: Make building verbose for better failure analysis

[Henning Schild <henning.schild@siemens.com>]

This will help understand what went wrong when looking at the CI logs
after a build failed. It can also help understanding builds that did not
fail.

Signed-off-by: Henning Schild <henning.schild@siemens.com>
---
 scripts/ci_build.sh   | 2 +-
 scripts/vm_smoke_test | 2 ++
 2 files changed, 3 insertions(+), 1 deletion(-)

diff --git a/scripts/ci_build.sh b/scripts/ci_build.sh
index f84fdcf..e941f8c 100755
--- a/scripts/ci_build.sh
+++ b/scripts/ci_build.sh
@@ -22,7 +22,7 @@ fi
 source isar-init-build-env /build/$WORKSPACE/$GIT_COMMIT
 
 # Start build for all possible configurations
-bitbake \
+bitbake -v \
         multiconfig:qemuarm-wheezy:isar-image-base \
         multiconfig:qemuarm-jessie:isar-image-base \
         multiconfig:qemuarm-stretch:isar-image-base \
diff --git a/scripts/vm_smoke_test b/scripts/vm_smoke_test
index 60c78da..fde0e05 100755
--- a/scripts/vm_smoke_test
+++ b/scripts/vm_smoke_test
@@ -60,6 +60,8 @@ run_test () {
     # Check kernel module
     check_example_module
 
+    dump_boot_log
+
     # Clean up test artifacts
     rm $CONSOLE_OUTPUT
     rm $PID_FILE
-- 
2.16.1