From 20d6cbf400ca2a5bdff78919628a4755711c4da8 Mon Sep 17 00:00:00 2001 From: donal <donalspring@gmail.com> Date: Mon, 23 Apr 2018 14:23:32 +0200 Subject: [PATCH] WIP - adding scaffold for the Lab --- exercises/6-return-of-the-app-monitoring/README.md | 35 +++++++++++++++++------------------ 1 files changed, 17 insertions(+), 18 deletions(-) diff --git a/exercises/6-return-of-the-app-monitoring/README.md b/exercises/6-return-of-the-app-monitoring/README.md index eeebe9e..ff5c03d 100644 --- a/exercises/6-return-of-the-app-monitoring/README.md +++ b/exercises/6-return-of-the-app-monitoring/README.md @@ -1,19 +1,18 @@ -# Exercise Title +# Return of the Application Monitoring -> Short description of the exercise and it's outcomes +> In this exercise we will create a build monitor to radiate vital build information and statistics _____ ## Learning Outcomes As a learner you will be able to -- Do thing 1 -- Do thing 2 -- Do thing 3 +- Create dashboards in Jenkins to display build status +- ## Tools and Frameworks > Name of tool - short description and link to docs or website -1. [Jenkins](https://jenkins.io/) - OpenSource build automation server; highly customisable through plugins -1. [Ansible]() - blah blah ... +1. [Build Monitor plugin](https://wiki.jenkins.io/display/JENKINS/Build+Monitor+Plugin) - Build Monitor Plugin provides a highly visible view of the status of selected Jenkins jobs. It easily accommodates different computer screen sizes and is ideal as an Extreme Feedback Device to be displayed on a screen on your office wall. (Inspired by the no longer maintained RadiatorView plugin). +1. [Build Fail Analyser](https://wiki.jenkins.io/display/JENKINS/Build+Failure+Analyzer) - This plugin analyzes the causes of failed builds and presents the causes on the build page. It does this by using a knowledge base of build failure causes that is built up from scratch. Saving statistics about failure causes is also possible. ## Big Picture This exercise begins cluster containing blah blah @@ -21,37 +20,37 @@ _____ ## 10,000 Ft View -> This should contain the goal of the exercise; with enough information that advanced learners could use this to build the exercise without much guidance. The information here +> The goal of this exercise is to introduce Build Monitors to radiate teams progress on Dashboards. -2. Highlevel instruction 1 +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. -2. Highlevel instruction with ref to `file-a` to keep learners in supportable mode +2. Use the pipeline views in OpenShift and Jenkins to produce dashboards that teams can use. ## Step by Step Instructions > This is a fairly structured guide with references to exact filenames and sections of text to be added. Include pictures and code snippets where appropriate. Rule of thumb is learners are dumb.... so over describe _why_ we're doing things -### Part 1 - do some things +### Part 1 - Create a build monitor > _prefix of exercise and why we're doing it_ 2. Do thing using tool X. + 2. Insert blah into `file1.txt` ``` export SOME_THING=biscuits ``` + 2. Open console and navigate to `New Item` and click it  - -### Part 2 - do some other things -> _prefix of exercise and why we're doing it_ - -3. Do other things _____ ## Extension Tasks > _Ideas for go-getters. Advanced topic for doers to get on with if they finish early. These will usually not have a solution and are provided for additional scope._ - - Add Auth to your application - - Do some other stuff +Additional Alerting + - Add `Slack` integration to the Pipeline by setting up a WebHook to call the slack endpoint with Build Stats + - Add `Twillio` text integration to send you text messages when the build fails. +Additional Monitoring + - Explore the Application's FEK stack inside OpenShift ## Additional Reading > List of links or other reading that might be of use / reference for the exercise -- Gitblit v1.9.3