From 4bffd7a2682a3ecde7d84e782d303f4c8823b559 Mon Sep 17 00:00:00 2001
From: Vladimir Khlyunev <vkhlyunev@mirantis.com>
Date: Thu, 8 Aug 2019 13:08:27 +0400
Subject: [PATCH] Add retry after failure to tempest job

Change-Id: I7e424bac0aed45b53f209a0924c3e1748b216707
---
 maintenance-ci/mos/templates/tempest.multijob.yaml | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/maintenance-ci/mos/templates/tempest.multijob.yaml b/maintenance-ci/mos/templates/tempest.multijob.yaml
index b17edd9..df4ff88 100644
--- a/maintenance-ci/mos/templates/tempest.multijob.yaml
+++ b/maintenance-ci/mos/templates/tempest.multijob.yaml
@@ -12,6 +12,10 @@
     - heavy-job:
         weight: 3
     parameters:
+    - bool:
+        name: RERUN_AFTER_FAILURE
+        default: false
+        description: "Reschedule job after failure?"
     - node:
         name: NODE_LABELS
         default-slaves:
@@ -114,3 +118,12 @@
             MILESTONE=9.2
             SPECIFICATION={specification}
             USE_TEMPLATE=true
+    publishers:
+    # retry if job failed
+    - conditional-publisher:
+      - condition-kind: boolean-expression
+        condition-expression: $RERUN_AFTER_FAILURE
+        action:
+        - naginator:
+            max-failed-builds: 2
+            fixed-delay: 600
-- 
2.45.2