Remove tripleo pipelines from zuul
With the shutdown of tripleo-test-cloud-rh1 we no longer have any jobs
that use these pipelines. Jobs that did run, have been moved to 3rd
party CI. Hardware and cloud are also lacking maintenance and soon to
be removed.
Depends-On:
gerrit: {}
mysql:
-- pipeline:
- name: check-tripleo
- description: >
- Newly uploaded patchsets enter this pipeline to receive an initial +/-1
- Verified vote from the "zuul" user. 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.
- success-message: Build succeeded (check-tripleo pipeline).
- failure-message: >
- Build failed (check-tripleo pipeline). For information on how to
- proceed, see
- http://docs.openstack.org/infra/manual/developers.html#automated-testing
- manager: independent
- precedence: normal
- trigger:
- gerrit:
- - event: patchset-created
- - event: change-restored
- - event: comment-added
- comment: (?i)^(Patch Set [0-9]+:)?( [\w\\+-]*)*(\n\n)?\s*recheck
- require:
- gerrit:
- open: True
- current-patchset: True
- success:
- gerrit: {}
- mysql:
- failure:
- gerrit: {}
- mysql:
-
-- pipeline:
- 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.
- success-message: Build succeeded (experimental-tripleo).
- failure-message: Build failed (experimental-tripleo).
- manager: independent
- precedence: low
- trigger:
- gerrit:
- - event: comment-added
- comment: (?i)^(Patch Set [0-9]+:)?( [\w\\+-]*)*(\n\n)?\s*check experimental\s*$
- success:
- gerrit: {}
- mysql:
- failure:
- gerrit: {}
- mysql:
-
- pipeline:
name: merge-check
description: >
