RedHatTraining/rht-labs-docs.git

			@@ -540,11 +540,15 @@
			* set the Name to `BUILD_TAG`. This will be available to the job as an Enviroment Variable.
			* You can set `dev-todolist-fe-build.` as the default value for ease when triggering manually.
			* The description is not required but a handy one for reference would be `${JOB_NAME}.${BUILD_NUMBER} of previous build eg dev-todolist-fe-build.1232`
			<p class="tip">
			NOTE - Don't forget to include the `.` after `dev-todolist-fe-build` in the Default Value box.
			</p>

			![param-trigger-bake](../images/exercise2/param-trigger-bake.png)

			5. This time set the `Restrict where this project can be run` label to `master`.
			<p class="tip">
			`Master` is the default node that jobs run on. We don't want jenkins to execute the bake on any other nodes if the `master` is busy so it is always safer to specify it here.
			NOTE - `Master` is the default node that jobs run on. We don't want jenkins to execute the bake on any other nodes if the `master` is busy so it is always safer to specify it here.
			</p>

			5. There is no Git or SCM needed for this job so move down to the Build Environment and tick `Delete workspace before build starts`

			@@ -119,7 +119,7 @@
			Click on `dev-todolist-fe-build` and then click the `configure` button on the left-hand side.
			![jenkins-configure-job](../images/exercise3/jenkins-configure-job.png)

			2. Scroll to the `Build` part of the configuration page and add `npm run test` below `npm install`. Click `save` or `apply` at the bottom to save the changes.
			2. Scroll to the `Build` part of the configuration page and add `npm run test` below `npm install`.
			![jenkins-build-step](../images/exercise3/jenkins-build-step.png)

			2. Scroll to the `Post-build Actions` section and click `Add post-build action`. Select `Publish xUnit test result report` (Jenkins might place this at the top of the `Post-build Actions` list).

			@@ -91,13 +91,13 @@
			2. On the job's configure page; set the Branch Sources to `git`
			![multibranch-select-git](../images/exercise4/multibranch-select-git.png)

			2. Fill in the Git settings with your `todolist-api` GitLab url and set the credentials as you've done before.
			2. Fill in the Git settings with your `todolist-api` GitLab url and set the credentials as you've done before. `https://gitlab.apps.<SOMEDOMAIN>.com/<YOUR_NAME>/todolist-api.git`
			![multibranch-git](../images/exercise4/multibranch-git.png)

			2. Set the `Scan Multibranch Pipeline Triggers` to be periodical and the internal to 1 minute. This will poll the gitlab instance for new branches or change sets to build.
			2. Set the `Scan Multibranch Pipeline Triggers` to be periodic and the interval to 1 minute. This will poll the gitlab instance for new branches or change sets to build.
			![multibranch-scan-time](../images/exercise4/multibranch-scan-time.png)

			2. Save the Job configuration to run the intial scan. The log will show scans for `master` and `develop` branch which have no `Jenkinsfile` so are skipped. The resulting view will show the `feature/jenkisifle` job corresponding the only branch that currently has one. The build should run automatically.
			2. Save the Job configuration to run the intial scan. The log will show scans for `master` and `develop` branch which have no `Jenkinsfile` so are skipped. The resulting view will show the `feature/jenkinsfile` job corresponding the only branch that currently has one. The build should run automatically.
			![todolist-api-multi](../images/exercise4/todolist-api-multi.png)

			2. The pipeline file is setup to only run `bake` & `deploy` stages when on `master` or `develop` branch. This is to provide us with very fast feedback for team members working on feature or bug fix branches. Each time someone commits or creates a new branch a basic build with testing occurs to give very rapid feedback to the team. Let's now update our `master` and `develop` branches to include the Jenkinsfile and delete the feature branch.
			@@ -291,7 +291,7 @@
			- arachni
			```

			3. Update the params files `SOURCE_REPOSITORY_URL` to point to your gitlab's hosted version of the `enablement-ci-cd` repo.
			3. Update the `jenkins-slave-arachni` files `SOURCE_REPOSITORY_URL` to point to your gitlab's hosted version of the `enablement-ci-cd` repo.
			```
			SOURCE_REPOSITORY_URL=https://gitlab.apps.lader.rht-labs.com/<GIT_USERNAME>/enablement-ci-cd.git
			SOURCE_CONTEXT_DIR=docker/jenkins-slave-arachni

	exercises/2-attack-of-the-pipelines/README.md	6 ●●●●● patch \| view \| raw \| blame \| history
	exercises/3-revenge-of-the-automated-testing/README.md	2 ●●●●● patch \| view \| raw \| blame \| history
	exercises/4-an-enslaved-hope/README.md	8 ●●●●● patch \| view \| raw \| blame \| history