From 43a874fc58e7f5da9fa780ba118ffaca0079d847 Mon Sep 17 00:00:00 2001
From: Victor Stinner <vstinner@redhat.com>
Date: Thu, 11 Feb 2016 15:44:13 +0100
Subject: [PATCH] Add non-voting gate-trove-python34-db check

Add a non-voting python34 check job to Trove. The check is not voting
because it doesn't work yet, see the change
Ie08b45db885639541804c3bcc486e4e451833347.

The check job is only added to the development branch (master for
Newton): explicitly exclude existing stable branches.

Later the python34 gate job will be make voting to avoid Python 3
regressions. See the blueprint for the overall plan.

Partially implements: blueprint trove-python3
Change-Id: Ia41c990b6ce1eee6c21ca1821b27ec96061765d3
---
 zuul/layout.yaml | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/zuul/layout.yaml b/zuul/layout.yaml
index f21fe2c6d1..29320b78e9 100755
--- a/zuul/layout.yaml
+++ b/zuul/layout.yaml
@@ -2175,6 +2175,10 @@ jobs:
   - name: gate-trove-scenario-functional-dsvm-redis
     voting: false
 
+  - name: gate-trove-python34-db
+    branch: ^(?!stable/(?:juno|kilo|liberty|mitaka)).*$
+    voting: false
+
   - name: gate-anchor-tox-bandit
     branch: master
     voting: false
@@ -11322,6 +11326,7 @@ projects:
       - name: translation-jobs
       - name: release-notes-jobs
     check:
+      - gate-trove-python34-db
       - gate-trove-tox-checklinks
       - gate-trove-tox-doc-publish-checkbuild
       - gate-trove-functional-dsvm-mysql