Merge "[upstream] update/improve content - Project Status and Zuul"

doc/upstream-training/source/slides/workflow-project-status-and-zuul.rst

@@ -40,17 +40,29 @@ Zuul Pipelines
 - Check
 
   - Run against all newly updated patch sets
-  - Jenkins votes +1/-1 depending on test results
+  - Runs unit testing, Pep8, docs/releasenote build and
+    functional tempest testing
+  - Zuul votes +1/-1 depending on test results
 
 - Gate
 
   - Only run after a patch is approved by a core reviewer
   - More extensive testing than check pipeline
+  - Runs another unit test run along with additional tempest testing
   - 'Gates' code entering the stable or master branches
 
+Zuul Pipelines - cont.
+======================
+
 - Post
 
   - Jobs run against a patch after it merges
+  - Documentation build/publishing, tarball generation, image build
+
+.. note::
+
+  - The above jobs are examples of what is run in each pipeline.
+    What is actually run varies based upon the project being tested.
 
 Exercise
 ========
@@ -66,16 +78,38 @@ Exercise
 
 - Discuss your findings with your group
 
-Jenkins Failures
-================
+Patch Number
+============
 
-.. image:: ./_assets/workflow-project-status-and-zuul-jenkins-fail.png
+.. image:: ./_assets/workflow-project-status-and-zuul-patch-id.png
+  :class: image-pad-top
+
+.. note::
+
+  - The number next to 'Change' is the patch number.
+  - Can use the patch number to track status in Zuul status page.
+
+Filtering on Patch Number in Zuul
+=================================
+
+.. image:: ./_assets/workflow-project-status-and-zuul-zuul-job-status.png
+  :class: image-pad-top
+
+.. note::
+
+  - Shows the Zuul status page filtered down to just the patch of interest.
+
+
+Zuul Failures
+=============
+
+.. image:: ./_assets/workflow-project-status-and-zuul-zuul-fail.png
   :class: image-pad-top
 
 
 
-Analysing Jenkins Failures
-==========================
+Analysing Zuul Failures
+=======================
 - Logs may be accessed by clicking on the test's name
 
   - Directs the user to saved log output
@@ -83,14 +117,32 @@ Analysing Jenkins Failures
 
 - Voting and non-voting jobs
 
-  - Voting job failures cause a -1 vote from Jenkins on the patch
-  - Non-voting jobs do not cause a -1 vote from Jenkins upon failure
+  - Voting job failures cause a -1 vote from Zuul on the patch
+  - Non-voting jobs do not cause a -1 vote from Zuul upon failure
 
 - Non-voting jobs are new jobs that are being tested and may not yet be ready
   to vote
 
-Log Output
-==========
+Logs
+====
+
+.. image:: ./_assets/workflow-project-status-and-zuul-zuul-failure-log-list.png
+  :class: image-pad-top
+
+.. note::
+
+  - Example of what the logs for a run look like
+  - Actual log files will vary depending on the test you are examining
+
+Logs - Testr HTML Report
+========================
+
+.. image:: ./_assets/workflow-project-status-and-zuul-failure-testr-html.png
+  :class: image-pad-top
+
+
+Logs - Job Run Output
+=====================
 
 .. image:: ./_assets/workflow-project-status-and-zuul-failure-log.png
   :class: image-pad-top
@@ -103,6 +155,29 @@ Intermittent Failures
 - To trigger a re-run of check or gate add a comment to the patch
   in the form of 'recheck bug XXXXX'
 
+Recheck Example
+===============
+
+.. image:: ./_assets/workflow-project-status-and-zuul-recheck-example.png
+  :class: image-pad-top
+
+.. note::
+
+  - Note ability to see logstash and link to launchpad
+
+What Are Rechecks
+=================
+
+- Issues causing intermittent failures
+- Elastic search is used to look for logs indicating similar failures
+
+  - Users add new bugs to
+    `elastic-recheck <https://docs.openstack.org/infra/elastic-recheck/readme.html>`_
+
+- Goal is to capture all instances of a failure in the hopes of identifying
+  patterns causing the bug
+- Comments on patches that hit a known bug
+
 Exercise
 ========
 - Find how rechecks are categorized