From f69ba4f04fb92454311dba8fba2e8fec0b84bf12 Mon Sep 17 00:00:00 2001 From: Sean Dague Date: Mon, 16 Feb 2015 08:41:37 -0500 Subject: [PATCH] skip rerunning requirements changes in devstack Requirements changes to projects trigger tempest/grenade jobs. However, these are exactly the same tests as would have just been run in the requirements job before we propose requirements changes to projects. So the merge of a requirements change current creates a great thundering herd in all the projects. Skip if this is the proposal bot and the only content changed is requirements. The requirements check job will ensure that people can't sneak an invalid requirement range in. Change-Id: Ie0c7470eae497ec666f200d2119f5de415901d1b --- zuul/layout.yaml | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/zuul/layout.yaml b/zuul/layout.yaml index 5b4b31aea2..17f9d420ad 100755 --- a/zuul/layout.yaml +++ b/zuul/layout.yaml @@ -552,6 +552,15 @@ jobs: # -nv jobs are never voting. - name: ^.*-nv$ voting: false + # because of global requirements overrides, there is no reason to + # run tempest/grenade tests after a requirements sync, as they've + # already been run in the requirements job with the override. + - name: ^.*(tempest|grenade)-dsvm.*$ + skip-if: + - project: ^openstack/ + all-files-match-any: + - ^(test-|)requirements.txt$ + # dsvm-neutron jobs should be conditionally skipped so they don't # run in response to changes that do not influence their execution. - name: ^.*(devstack|tempest|grenade|rally)-dsvm.*$