From 590bd9d337023c102e34d74cda8e383bce5d0a1e Mon Sep 17 00:00:00 2001 From: acammies <a.cammies@gmail.com> Date: Mon, 07 May 2018 22:18:06 +0200 Subject: [PATCH] Merge pull request #215 from christophermay07/ex2 --- exercises/2-attack-of-the-pipelines/README.md | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/exercises/2-attack-of-the-pipelines/README.md b/exercises/2-attack-of-the-pipelines/README.md index 4a5ce91..cafb166 100644 --- a/exercises/2-attack-of-the-pipelines/README.md +++ b/exercises/2-attack-of-the-pipelines/README.md @@ -311,7 +311,7 @@ ### Part 2 - Create a NodeJS Build slave > _In this exercise; we will create a build configuration to generate a slave for Jenkins to use in it's builds_ -3. In order for Jenkins to be able to run `npm` builds and installs as we have done locally, we must configure a `jenkins-build-slave` for Jenkins to use. This slave will be dynamically provisioned when we run a build. It needs to have NodeJS and npm installed in it. In your `enablement-cd-cd` repository, checkout the template and configuration. This will bring in the template, the params & the `Dockerfile`. +3. In order for Jenkins to be able to run `npm` builds and installs as we have done locally, we must configure a `jenkins-build-slave` for Jenkins to use. This slave will be dynamically provisioned when we run a build. It needs to have NodeJS and npm installed in it. In your `enablement-ci-cd` repository, checkout the template and configuration. This will bring in the template, the params & the `Dockerfile`. ```bash $ git checkout exercise2/jenkins-slave docker/ templates/ params/jenkins-slave-npm ``` -- Gitblit v1.9.3