Archiving artifacts in mso builds

in order to understand why an arquillian test would fail

Change-Id: I586167f0805fc58094bbb676a70c76bdc1dc150d
Signed-off-by: JulienBe <jb379x@att.com>

diff --git a/jjb/mso/mso.yaml b/jjb/mso/mso.yaml
index d787ca9..7384283 100644 (file)
--- a/jjb/mso/mso.yaml
+++ b/jjb/mso/mso.yaml
@@ -7,9 +7,11 @@
       - '{project-name}-{stream}-verify-profile-java':
           mvn-profile: 'with-integration-tests'
           build-node: 'ubuntu1604-docker-8c-8g'
+          archive-artifacts: 'packages/arquillian-unit-tests/target/mso-automated-tests/**/*,packages/arquillian-unit-tests/target/surefire-reports/**/*'
       - '{project-name}-{stream}-merge-profile-java':
           mvn-profile: 'with-integration-tests'
           build-node: 'ubuntu1604-docker-8c-8g'
+          archive-artifacts: 'packages/arquillian-unit-tests/target/mso-automated-tests/**/*,packages/arquillian-unit-tests/target/surefire-reports/**/*'
       - '{project-name}-{stream}-release-version-java-daily'
       - '{project-name}-{stream}-docker-version-java-daily':
           docker-pom: 'pom.xml'
@@ -29,4 +31,4 @@
     mvn-settings: 'mso-settings'
     files: '**'
     archive-artifacts: ''
-    build-node: ubuntu1604-basebuild-4c-4g
+    build-node: ubuntu1604-basebuild-4c-4g
\ No newline at end of file