From 85ecf2df38725b1cb19a1131f91622a2649df4aa Mon Sep 17 00:00:00 2001 From: donal <donalspring@gmail.com> Date: Tue, 03 Jul 2018 15:45:13 +0200 Subject: [PATCH] Merge branch 'master' of github.com:rht-labs/enablement-docs --- 6-return-of-the-app-monitoring/README.md | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/6-return-of-the-app-monitoring/README.md b/6-return-of-the-app-monitoring/README.md index 3dc3dd4..5e034bb 100644 --- a/6-return-of-the-app-monitoring/README.md +++ b/6-return-of-the-app-monitoring/README.md @@ -37,7 +37,7 @@ _____ ## 10,000 Ft View -> The goal of this exercise is to introduce Build Monitors to radiate teams progress on Dashboards. +> The goal of this exercise is to introduce Build Monitors to radiate team's progress on Dashboards. 2. Create a new Dashboard for our Builds using the plugin above. Use Regex to add jobs to it. Use the BuildFail Analyser to add meaningful data to the reason for failures. @@ -60,7 +60,7 @@ 2. Check the box to use Regular Expression and set the value to be something that should scrape our apps such as `.*todolist.*`  -2. Finally; select `Display committers` and set the Failure Analyser to `Description`. This allows us to write regex for when fails occur in Jenkins and have the reasons plotted on the graph. For example; number of test scores or common compilation errors. +2. Finally; select `Display committers` and set the Failure Analyser to `Description`. This allows us to write regexes for when failures occur in Jenkins and have the reasons plotted on the graph. For example; number of test scores or common compilation errors.  2. Save your configuration to see your Build Monitor! @@ -121,7 +121,7 @@ ```  -2. We can save up these regex and inject them into the `jenkins-s2i` so the configuration is there the next time we launch and we don't have to code them up again. In `enablement-ci-cd` repo; the `jenkins-s2i/configuration/build-failure-analyzer.xml` already contains ones we've collected on previous residencies. +2. We can save up these regexes and inject them into the `jenkins-s2i` so the configuration is there the next time we launch and we don't have to code them up again. In `enablement-ci-cd` repo; the `jenkins-s2i/configuration/build-failure-analyzer.xml` already contains ones we've collected on previous residencies. ### Part 3 - Seed Jenkins Dashboards > _TODO - Add instructions for creating dashboards as part of s2i in Jenkins setup using DSL_ -- Gitblit v1.9.3