| | |
|---|
| | | > In this exercise we will create a build monitor to radiate vital build information and statistics |
|---|
| | | |
|---|
| | |  |
|---|
| | | _____ |
|---|
| | | |
|---|
| | | ## Exercise Intro |
|---|
| | | Build monitors provide a tight feedback loop which is vital to high performing teams. Being in a highly visible location, build monitors radiate crucial build and test information, meaning the team doesn't have to go out of their way to find it. Build monitors also provide a degree of accountability whilst also keeping the team motivated to fix problems. With broken components visualised, seeing build monitors change from red to green can give the collective feeling that progress is being made. |
|---|
| | | |
|---|
| | | On residencies we display the build monitors on Raspberry Pi's hooked up to large TV screens that everyone can see at a glance. We've also used colour-changing lightbulbs in the labs that change from Green to Red depending on the success/fail status of jobs. There are many other ways to notify people of Build Failures such as Slack notices, text messages or just plain old email. This lab is about radiating the information to allow teams respond quickly to change. |
|---|
| | | |
|---|
| | | In this Exercise we will be creating a build monitor to display all of our jobs in one visual display as well as pipeline views. We will then add the cause of build failures for each job to the monitors. This will allow you to rapidly see why a particular build is failing and fix it faster. |
|---|
| | | |
|---|
| | | Finally, build monitors can promote team cohesion as they enable all team members to be on the same page regarding the current project status. They can also engage business users and clients on the stats of the system. __The most important thing here isn't the tool, but the visual feedback.__ |
|---|
| | | |
|---|
| | | ## Why do we use build monitors? |
|---|
| | | - Provides instant feedback to teams regarding the current status of the build. |
|---|
| | | - Tightens feedback loop by having vital information needed by teams, available upfront. |
|---|
| | | - Motivates teams to fix problems together. |
|---|
| | | |
|---|
| | | ____ |
|---|
| | | ## Learning Outcomes |
|---|
| | | As a learner you will be able to |
|---|
| | | - Create dashboards in Jenkins to display build status |
|---|
| | |
|---|
| | | |
|---|
| | | - [Intro](https://docs.google.com/presentation/d/1nfv1f04HkvN6ruOZ5JRMnHsSfDClyMNOhXxcC7WsSr4/) |
|---|
| | | - [Wrap-up](https://docs.google.com/presentation/d/1-HI9Wd5WWlzaMWmFpBEclqdyt9pFumaVbfOUrkfYKY0/) |
|---|
| | | - [All Material](https://drive.google.com/drive/folders/1Lx0OotWjisugCY11Ef0dF7EZXMIPoXOO) |
|---|
| | | - [All Material](https://drive.google.com/drive/folders/1Lx0OotWjisugCY11Ef0dF7EZXMIPoXOO) |
|---|
