Fixing the Maven deploy publisher

Moving the Maven deploy above the ship logs and removing from the
integration until I receive confirmation from the team that it's
required

Change-Id: Ib7692b8572e3b0d55a79f5180dfa2764d406ca75
Signed-off-by: Vanessa Rene Valderrama <vvalderrama@linuxfoundation.org>

diff --git a/jjb/hc2vpp/hc2vpp.yaml b/jjb/hc2vpp/hc2vpp.yaml
index 504459c..55a3721 100644 (file)
--- a/jjb/hc2vpp/hc2vpp.yaml
+++ b/jjb/hc2vpp/hc2vpp.yaml
@@ -209,12 +209,12 @@
             branch: '{stream}'
         - email-notification:
             email-prefix: '[hc2vpp]'
-        - fdio-infra-shiplogs:
-            maven-version: 'mvn33-new'
         - maven-deploy:
             id: ''
             unique-version: true
             deploy-unstable: false
+        - fdio-infra-shiplogs:
+            maven-version: 'mvn33-new'
 
 - job-template:
     name: 'hc2vpp-integration-{stream}-{os}'
@@ -294,13 +294,5 @@
     publishers:
         - email-notification:
             email-prefix: '[hc2vpp]'
-        - maven-deploy:
-            id: ''
-            unique-version: true
-            deploy-unstable: false
         - fdio-infra-shiplogs:
             maven-version: 'mvn33-new'
-        - maven-deploy:
-            id: ''
-            unique-version: true
-            deploy-unstable: false