Show the Robot Framework report in after_failure hook.

This reduces output of the check-build-and-verify.sh script and also looks more logical and a clean
approach.

Addressed to #631

Author: php-coder

.travis.yml

@@ -38,6 +38,15 @@ script:
       exit 1;
     fi
 
+after_failure:
+  # In order to be able debug robot framework test flakes we need to have a report.
+  # Just encode it to a gzipped binary form and dump to console.
+  - if fgrep -qs 'status="FAIL"' target/robotframework-reports/output.xml; then
+          echo "===== REPORT START ====="
+          cat target/robotframework-reports/output.xml | gzip -c | base64
+          echo "===== REPORT END ====="
+  fi
+
 after_success:
   - if [ "$SPRING_PROFILES_ACTIVE" = 'travis' ]; then
       ./src/main/scripts/ci/publish-code-coverage.sh;

src/main/scripts/ci/check-build-and-verify.sh

@@ -224,14 +224,6 @@ if [ "$RUN_ONLY_INTEGRATION_TESTS" = 'yes' ]; then
 	if [ "$DANGER_STATUS" != 'skip' ]; then
 		print_log danger.log 'Run danger'
 	fi
-	
-	# In order to be able debug robot framework test flakes we need to have a report.
-	# Just encode it to a gzipped binary form and dump to console.
-	if fgrep -qs 'status="FAIL"' target/robotframework-reports/output.xml; then
-		echo "===== REPORT START ====="
-		cat target/robotframework-reports/output.xml | gzip -c | base64
-		echo "===== REPORT END ====="
-	fi
 fi
 
 # We don't remove the logs to make them available to danger that may be executed later as a separate