Do not abort ONAP pipeline if deployment fails or times out 25/2025/3
authorFatih Degirmenci <fdegir@gmail.com>
Fri, 23 Aug 2019 08:23:57 +0000 (08:23 +0000)
committerFatih Degirmenci <fdegir@gmail.com>
Fri, 23 Aug 2019 08:29:00 +0000 (08:29 +0000)
The work to activate deployment and testing ONAP from master
started, it is important to see the state of the deployment
by running k8s, oom, and onap healthchecks no matter the state
of the deployment. Running healthcheck is cheap anyways.

Change-Id: Ia6a5c0f2c7bc324449ac27c89a87ff009da1b387

jjb/cloud-infra/cloud-infra-periodic-onap.yaml

index 4c659a937682f806bbf714c41ac9ae76ed6cce09..89c6d994572bb2a87b35342a8f603a5a61a9f3e9 100644 (file)
           cp $OPENRC_FILE /tmp/openrc
       - multijob:
           name: Deploy ONAP using OOM
-          condition: SUCCESSFUL
+          condition: ALWAYS
           projects:
             - name: 'onap-deploy-periodic-{distro}-{installer-type}-{type}-{onap-branch}'
               current-parameters: false
                 CLEANUP=$CLEANUP
               git-revision: true
               node-parameters: true
-              kill-phase-on: FAILURE
-              abort-all-job: true
+              kill-phase-on: NEVER
+              abort-all-job: false
       - multijob:
           name: K8S and OOM Healthcheck using xtesting
           condition: ALWAYS