From 80ed7cd16c55a0856d64d987234ba1497102031d Mon Sep 17 00:00:00 2001 From: Robert Collins Date: Sun, 16 Feb 2014 20:47:16 +1300 Subject: [PATCH] Add -tripleo pipelines. The experimental-tripleo pipeline is to enable building out tripleo tests against other projects in advance of the second region coming online. The check-tripleo pipeline ensures that in the event of a tripleo cloud failure the main check queue won't appear to backlog, making analysis of devstack-gate check health easier. Change-Id: I93045879c508defd4f1f86979fb42da79bd29fad --- .../openstack_project/files/zuul/layout.yaml | 44 +++++++++++++++++++ 1 file changed, 44 insertions(+) diff --git a/modules/openstack_project/files/zuul/layout.yaml b/modules/openstack_project/files/zuul/layout.yaml index 9f101acad2..324180c1db 100644 --- a/modules/openstack_project/files/zuul/layout.yaml +++ b/modules/openstack_project/files/zuul/layout.yaml @@ -169,6 +169,50 @@ pipelines: to: openstack-qa@lists.openstack.org subject: 'Periodic jobs for {change.project} failed' + - name: check-tripleo + description: > + Newly uploaded patchsets enter this pipeline to receive an initial +/-1 + Verified vote from Jenkins. This is used for TripleO patchsets only so + that if the TripleO cloud suffers a failure, folk looking can tell that + there isn't a system infra problem. only a TripleO specific problem. + Once the TripleO test cloud is multi region and has some months of + proven stability this will be folded back into the normal check pipeline. + failure-message: > + Build failed. For information on how to proceed, see + https://wiki.openstack.org/wiki/GerritJenkinsGit#Test_Failures + manager: IndependentPipelineManager + precedence: low + trigger: + gerrit: + - event: patchset-created + - event: change-restored + - event: comment-added + comment_filter: (?i)^\s*recheck(( (?:bug|lp)[\s#:]*(\d+))|( no bug))\s*$ + success: + gerrit: + force-message: true + failure: + gerrit: + force-message: true + + - name: experimental-tripleo + description: > + On-demand pipeline for requesting a run against a tripleo experimental + jobs - slower and running without redundancy - so not yet gating. Leave + review comment of "check experimental" to run jobs in this pipeline. + manager: IndependentPipelineManager + precedence: low + trigger: + gerrit: + - event: comment-added + comment_filter: (?i)^\s*check experimental\s*$ + success: + gerrit: + force-message: true + failure: + gerrit: + force-message: true + project-templates: - name: python-jobs