Copy main content to README

README.md

@@ -1,34 +1,27 @@
-# Learning Jenkins
-This is the repository for the LinkedIn Learning course `Learning Jenkins`. The full course is available from [LinkedIn Learning][lil-course-url].
+# Learning Jenkins, 03-05: String Parameters
+Create a freestyle job with one build step.
 
-_See the readme file in the main branch for updated instructions and information._
-## Instructions
-This repository has branches for each of the videos in the course. You can use the branch pop up menu in github to switch to a specific branch and take a look at the course at that stage, or you can add `/tree/BRANCH_NAME` to the URL to go to the branch you want to access.
+# WINDOWS SYSTEMS
+If you are running Jenkins on a Windows system:
 
-## Branches
-The branches are structured to correspond to the videos in the course. The naming convention is `CHAPTER#_MOVIE#`. As an example, the branch named `02_03` corresponds to the second chapter and the third video in that chapter. 
-Some branches will have a beginning and an end state. These are marked with the letters `b` for "beginning" and `e` for "end". The `b` branch contains the code as it is at the beginning of the movie. The `e` branch contains the code as it is at the end of the movie. The `main` branch holds the final state of the code when in the course.
+1. Select the `Execute Windows batch command` build step
+2. Enter the following for the command:
+```
+@echo off
+@echo VERSION_NUMBER = %VERSION_NUMBER%
+```
 
-When switching from one exercise files branch to the next after making changes to the files, you may get a message like this:
+[Follow this link for more details on Windows](WINDOWS.md)
 
-    error: Your local changes to the following files would be overwritten by checkout:        [files]
-    Please commit your changes or stash them before you switch branches.
-    Aborting
+# MacOS, Linux, and Docker
+If you are running Jenkins on MacOS, Linux, or Docker:
 
-To resolve this issue:
-	
-    Add changes to git using this command: git add .
-	Commit changes using this command: git commit -m "some message"
+1. Select the `Execute shell` build step.
+2. Enter the following for the command:
+```
+#!/bin/bash
+echo "VERSION_NUMBER = $VERSION_NUMBER"
+```
 
-## Installing
-1. To use these exercise files, you must have the following installed:
-	- [list of requirements for course]
-2. Clone this repository into your local machine using the terminal (Mac), CMD (Windows), or a GUI tool like SourceTree.
-3. [Course-specific instructions]
-
-
-[0]: # (Replace these placeholder URLs with actual course URLs)
-
-[lil-course-url]: https://www.linkedin.com/learning/
-[lil-thumbnail-url]: http://
+[Follow this link for more details on MacOS, Linux, and Docker](MAC_LINUX_DOCKER.md)