Apex: fixes test suite always running even when deploy fails 71/39371/1
authorTim Rozet <trozet@redhat.com>
Wed, 16 Aug 2017 01:52:01 +0000 (21:52 -0400)
committerTim Rozet <trozet@redhat.com>
Wed, 16 Aug 2017 01:52:01 +0000 (21:52 -0400)
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
jjb/apex/apex.yml.j2

index 3f6d4c0..07181fc 100644 (file)
             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
                   git-revision: false
         - multijob:
             name: 'OPNFV Test Suite'
-            condition: SUCCESSFUL
             projects:
                 - name: 'apex-testsuite-{scenario}-baremetal-{scenario_stream}'
                   node-parameters: true
index 5d7f150..2d760f8 100644 (file)
             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
                   git-revision: false
         - multijob:
             name: 'OPNFV Test Suite'
-            condition: SUCCESSFUL
             projects:
                 - name: 'apex-testsuite-{scenario}-baremetal-{scenario_stream}'
                   node-parameters: true