From c1ffe7b01ac0eb6e386c6eaa4ed497f8bdc8434a Mon Sep 17 00:00:00 2001
From: Tim Rozet <trozet@redhat.com>
Date: Tue, 15 Aug 2017 21:52:01 -0400
Subject: Apex: fixes test suite always running even when deploy fails
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

According to the multijob builder, condtion: "condition (str) – when to
trigger the other job".  Other job in this case means the next job I
believe.

Change-Id: I084fffc80584ad683345f6040ec0081c16513c8d
Signed-off-by: Tim Rozet <trozet@redhat.com>
---
 jjb/apex/apex.yml.j2 | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

(limited to 'jjb/apex/apex.yml.j2')

diff --git a/jjb/apex/apex.yml.j2 b/jjb/apex/apex.yml.j2
index 5d7f150cd..2d760f854 100644
--- a/jjb/apex/apex.yml.j2
+++ b/jjb/apex/apex.yml.j2
@@ -585,7 +585,7 @@
             description: "Deployed on $NODE_NAME - Scenario: $DEPLOY_SCENARIO"
         - multijob:
             name: 'Baremetal Deploy'
-            condition: ALWAYS
+            condition: SUCCESSFUL
             projects:
                 - name: 'apex-deploy-baremetal-{scenario_stream}'
                   node-parameters: true
@@ -600,7 +600,6 @@
                   git-revision: false
         - multijob:
             name: 'OPNFV Test Suite'
-            condition: SUCCESSFUL
             projects:
                 - name: 'apex-testsuite-{scenario}-baremetal-{scenario_stream}'
                   node-parameters: true
-- 
cgit 1.2.3-korg