From 5d45630d38a5201c65e670342119f9eeadf30cef Mon Sep 17 00:00:00 2001 From: Rob Harris <roharris@redhat.com> Date: Mon, 23 Apr 2018 23:51:00 +0200 Subject: [PATCH] Merge branch 'master' of https://github.com/rht-labs/enablement-docs into slide-deck-links --- exercises/2-attack-of-the-pipelines/README.md | 17 ++++++++++++++++- 1 files changed, 16 insertions(+), 1 deletions(-) diff --git a/exercises/2-attack-of-the-pipelines/README.md b/exercises/2-attack-of-the-pipelines/README.md index 80e2d05..a391877 100644 --- a/exercises/2-attack-of-the-pipelines/README.md +++ b/exercises/2-attack-of-the-pipelines/README.md @@ -4,6 +4,21 @@  +## Exercise Intro +This lesson is focused on creating a pipeline for our application. What is a pipeline? A pipeline is a series of steps or stages that takes our code from source to a deployed application. There can be many stages to a pipeline but a simple flow is to run a `build > bake > deploy`. Usually the first stage is trigger by something like a git commit. There could be many steps in each of these stages; such as compiling code, running tests and linting. All of these are done to try and drive up code quality and give more assurance that what is deployed is behaving as expected. In the exercise we will create Jenkins pipeline by configuring it through the UI, this will create an un-gated pathway to production + +First we will explore the sample application and get it running locally. The sample app is a `todolist` app - the `Hello World` app of the modern day. + +#### Why create pipelines +* Assurance - drive up code quality and remove the need for dedicated deployment / release management teams +* Freedom - allow developers to take ownership of how and when code gets built and shipped +* Reliablility - pipelines are a bit boring; they execute the same way each and every time they're run! +* A pathway to production: + - Puts the product in the hands of the customer quicker + - Enables seamless and repeatable deploys + - More prod like infrastructure increases assurance + - ���We have already done it��� behavior de-risks go live + _____ ## Learning Outcomes @@ -694,4 +709,4 @@ - [Intro](https://docs.google.com/presentation/d/1t1CONuy-_IRPZYmU010Qgk2rshiDJTennvLyQR8GllE) - [Wrap-up](https://docs.google.com/presentation/d/1kZ8SV6iJnrKk_AqPpyPuNZifv7VzItHOB9HYdOnNJjI) -- [All Material](https://drive.google.com/drive/folders/1lf66ks2tT0eQ4A9RSU48u0ZhvBXzoHWJ) \ No newline at end of file +- [All Material](https://drive.google.com/drive/folders/1lf66ks2tT0eQ4A9RSU48u0ZhvBXzoHWJ) -- Gitblit v1.9.3