Revert "Update pipelines as per zuul docs"

This reverts commit e616914.

Author: mnasiadka

zuul.d/pipelines.yaml

@@ -2,8 +2,9 @@
     name: check
     description: |
       Newly uploaded patchsets enter this pipeline to receive an
-      initial check status.
+      initial +/-1 Verified vote.
     manager: independent
+    precedence: normal
     trigger:
       github:
         # Run this pipeline on new/changed pull requests
@@ -12,62 +13,41 @@
             - opened
             - changed
             - reopened
-        # Run in response to a pull request comment "recheck"
-        - event: pull_request
-          action: comment
-          comment: (?i)^\s*recheck\s*$
         # When using the checks API to report results, failed runs
         # will have a "re-run" button which emits this event.
         - event: check_run
           action: rerequested
-          check: .*/check:.*
+          check: '.*/check:.*'
     start:
       github:
         check: 'in_progress'
         comment: false
-        # It is recommended to use the checks API for consistency with
-        # other common CI tools that integrate with Github.  Results
-        # will appear on the "checks" tab of PR and changes.  There is
-        # generally no need to have Zuul leave comments when using the
-        # checks API.
-        #
-        # The older status API appears inline with the PR and can be
-        # enabled by uncommenting the "status:" in the various
-        # sections below.  You should choose one or the other
-        # depending on project preferences.
-        #
-        #status: 'pending'
-        #comment: false
     success:
       github:
         check: 'success'
         comment: false
-        #status: 'success'
     failure:
       github:
         check: 'failure'
         comment: false
-        #status: 'failure'
     dequeue:
       github:
-        check: cancelled
+        check: 'cancelled'
         comment: false
 
 - pipeline:
     name: gate
     description: |
-      Changes that have been approved by core developers are enqueued
-      in order in this pipeline, and if they pass tests, will be
-      merged.
+      Changes that have been approved are enqueued in order in this
+      pipeline, and if they pass tests, will be merged. For
+      documentation on how gating with Zuul works, please see
+      https://zuul-ci.org/docs/zuul/latest/gating.html
     manager: dependent
     precedence: high
     supercedes: check
+    post-review: True
     require:
       github:
-        review:
-          # Require an approval from user with write access (e.g. core-reviewer)
-          - permission: write
-            type: approved
         # Require label
         label: gate
         open: True
@@ -76,19 +56,13 @@
       github:
         - event: pull_request_review
           action: submitted
-          state: approved
-        - event: pull_request
-          action: comment
-          comment: (?i)^\s*regate\s*$
+          #state: approved
         - event: pull_request_review
           action: dismissed
-          state: request_changes
-        - event: pull_request
-          action: status
-          status: ".*:success"
+          #state: request_changes
         - event: check_run
           action: rerequested
-          check: .*/gate:.*
+          check: '.*/gate:.*'
         - event: pull_request
           action: labeled
           label:
@@ -97,17 +71,14 @@
       github:
         check: 'in_progress'
         comment: false
-        #status: 'pending'
     success:
       github:
         check: 'success'
         comment: false
-        #status: 'success'
         merge: true
     failure:
       github:
         check: 'failure'
-        #status: 'failure'
         comment: false
     dequeue:
       github:
@@ -127,6 +98,46 @@
         - event: push
           ref: ^refs/heads/.*$
 
+- pipeline:
+    name: promote
+    description: |
+      This pipeline runs jobs that operate after each change is merged
+      in order to promote artifacts generated in the gate
+      pipeline.
+    manager: supercedent
+    precedence: high
+    post-review: True
+    require:
+      github:
+        merged: True
+    trigger:
+      github:
+        - event: pull_request
+          action: closed
+
+- pipeline:
+    name: release
+    description: |
+      When a commit is tagged as a release, this pipeline runs jobs
+      that publish archives and documentation.
+    manager: independent
+    precedence: high
+    post-review: True
+    trigger:
+      github:
+        - event: push
+          ref: ^refs/tags/[0-9]+(\.[0-9]+)*$
+
+- pipeline:
+    name: daily
+    post-review: true
+    description: Jobs in this queue are triggered on a timer.
+    manager: independent
+    precedence: low
+    trigger:
+      timer:
+        - time: '0 6 * * *'
+
 - pipeline:
     name: tag
     description: This pipeline runs jobs in response to any tag event.