Return of the Application Monitoring

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
- Create dashboards in Jenkins to display build status
-

Tools and Frameworks

Name of tool - short description and link to docs or website

1. 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).
2. Build Fail Analyser - 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

10,000 Ft View

The goal of this exercise is to introduce Build Monitors to radiate teams progress on Dashboards.

1. 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. 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 - Create a build monitor

prefix of exercise and why we're doing it

1. Do thing using tool X.

2. Insert blah into file1.txt
export SOME_THING=biscuits

3. Open console and navigate to New Item and click it

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.

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

Slide links

link back to the deck for the supporting material